From: Linus Torvalds <torvalds@linux-foundation.org>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
David Woodhouse <dwmw2@infradead.org>,
Frank Haverkamp <haver@vnet.ibm.com>
Subject: Re: [GIT-PULL] please pull UBI tree
Date: Fri, 27 Apr 2007 09:00:25 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704270855300.9964@woody.linux-foundation.org> (raw)
In-Reply-To: <1177677925.7539.18.camel@sauron>
On Fri, 27 Apr 2007, Artem Bityutskiy wrote:
>
> Linus, please, pull UBI tree from
> git://git.infradead.org/ubi-2.6.git for-linus
>
> The UBI tree has been in -mm for several releases and we would like to
> see it in the mainline.
Quite frankly, I have absolutely _zero_ visibility into things like this,
so before I merge it I want ack's from various layers (preferably a
mixture of interests - are any vendors interested, is DavidW ok with this,
who is using it now and are the interfaces and designs correct etc etc?)
So I simply cannot make that decision. I don't have the expertise or the
knowledge. I'll have to trust somebody else for things like this, and it
should be somebody who isn't "personally involved".
In other words, I kind of want a sign-off from other parties, because I
can't pull things like this "blind".
Are there (embedded?) vendors that already integrate this into their
kernel, or wait for it? Is dwmw supportive of this? Questions, questions..
Linus
next prev parent reply other threads:[~2007-04-27 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 12:45 [GIT-PULL] please pull UBI tree Artem Bityutskiy
2007-04-27 16:00 ` Linus Torvalds [this message]
2007-04-27 17:30 ` Artem Bityutskiy
2007-04-27 17:57 ` Thomas Gleixner
2007-04-27 17:59 ` Linus Torvalds
2007-04-27 20:52 ` Andrew Morton
2007-04-27 21:22 ` Randy Dunlap
2007-04-27 22:42 ` Josh Boyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.98.0704270855300.9964@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=haver@vnet.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox