Skip to contentSkip to conversation

Please add swiotlb.git tree to linux-next

DISCUSSION Konrad Rzeszutek Wilk 2 participants 2 messages Oct 31, 2012 Linux-next tree

lore
Share & tools
lore

Konrad Rzeszutek Wilk

author Acked-by H. Peter Anvin Acked-by Tony Luck
#0 lore raw

Hello,

Please add:

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git #linux-next

in the linux-next system. The branch is 'linux-next'. This would be the tree and branch used for maintaining the swiotlb and its different users.

The Ack's have already been given per this commit:

commit 6e28b761c5020c4bc943c7e38da86bea8af77d5c

Author: Konrad Rzeszutek Wilk <[email protected]>
Date:   Mon Oct 8 16:28:05 2012 -0700

MAINTAINERS: add Konrad as the SWIOTLB maintainer

Now that I've an IA64 box on top of the other boxes (IBM with Calgary-X, Intel VT-d, AMD Vi, and AMD GART - that can use SWIOTLB as fallback) I can reliably do regression testing.

#1 lore raw

Hi Konrad,

Quoted 20 lines · On Wed, 31 Oct 2012 08:59:29 -0400 Konrad Rzeszutek Wilk…

Please add:

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git #linux-next

in the linux-next system. The branch is 'linux-next'. This would be the tree and branch used for maintaining the swiotlb and its different users.

The Ack's have already been given per this commit:

commit 6e28b761c5020c4bc943c7e38da86bea8af77d5c

Author: Konrad Rzeszutek Wilk <[email protected]>
Date:   Mon Oct 8 16:28:05 2012 -0700

MAINTAINERS: add Konrad as the SWIOTLB maintainer

Now that I've an IA64 box on top of the other boxes (IBM with Calgary-X, Intel VT-d, AMD Vi, and AMD GART - that can use SWIOTLB as fallback) I can reliably do regression testing.

Quoted 8 lines

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Signature · 15 lines
Cheers,
Stephen Rothwell 
[email protected]

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.