Re: [PULL REQUEST] DMA-mapping framework redesign preparation patches
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Hi Marek, On Fri, 10 Feb 2012 19:32:17 +0100 Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote: > > Our patches with DMA-mapping framework redesign proposal have been > hanging for over a month with just a few comments. We would like to go > further in the development, but first I would like to ask You to give > them a try in the linux-next kernel. > > For everyone interested in this patch series, here is the relevant > thread: https://lkml.org/lkml/2011/12/23/97 > > If there are any problems with our git tree, please contact Marek > Szyprowski <m.szyprowski@xxxxxxxxxxx> or alternatively Kyungmin Park > <kyungmin.park@xxxxxxxxxxx>. > > The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab: > > Linux 3.3-rc2 (2012-01-31 13:31:54 -0800) > > are available in the git repository at: > git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next I have added this 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. -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx 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.
Description: PGP signature
[Linux MIPS Home] [LKML Archive] [Linux ARM] [Linux] [Git] [Photo] [Yosemite News] [Linux SCSI] [Linux Hams]