Stephen,
as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:
git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master
David, Stephen would like to see your explicit ack.
To make a long story short, currently the MTD subsystem maintenance is a
team work:
1. David is the maintainer who has the ultimate authority to merge or
reject patches, and who holds the biggest MTD experience/knowledge.
2. David is busy with other projects and has no time to routinely
review patches and merge them to the mtd-2.6.git tree. And I help him
with my "level 2" l2-mtd-2.6.git tree.
By including l2-mtd-2.6.git into linux-next we want to solve the
following problem: because of lack of time dwmw2 does not always merges
patches to the mtd-2.6.git tree, and often we are in a situation when
MTD patches are exposed to linux-next for a day or 2, during the merge
window, and then they are merged.
Thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
David,
On Mon, 2011-06-06 at 10:37 +0300, Artem Bityutskiy wrote:
> Stephen,
>
> as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:
>
> git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master
although you already asked about this, sfr wanted your deliberate ack.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
On Tue, 2011-06-07 at 07:40 +0300, Artem Bityutskiy wrote:
> David,
>
> On Mon, 2011-06-06 at 10:37 +0300, Artem Bityutskiy wrote:
> > Stephen,
> >
> > as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:
> >
> > git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master
>
> although you already asked about this, sfr wanted your deliberate ack.
Ack.
Thanks.
--
dwmw2
Hi Artem,
On Mon, 06 Jun 2011 10:37:30 +0300 Artem Bityutskiy <[email protected]> wrote:
>
> as we've discussed, please, include l2-mtd-2.6.git tree to linux-next:
>
> git://git.infradead.org/users/dedekind/l2-mtd-2.6.git master
I have added this 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
[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.