From: Behan Webster <behanw@converseincode.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"Michal Marek" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, "Jan-Simon Möller" <dl9pf@gmx.de>
Subject: Re: linux-next
Date: Wed, 19 Feb 2014 10:06:05 -0800 [thread overview]
Message-ID: <5304F28D.5070604@converseincode.com> (raw)
In-Reply-To: <20140219172223.9b107d24c1e5a708a1e3cece@canb.auug.org.au>
On 02/18/14 22:22, Stephen Rothwell wrote:
> Hi,
>
> On Tue, 18 Feb 2014 22:12:05 -0800 Behan Webster <behanw@converseincode.com> wrote:
>> Yes. The plan is to send them to the list. Just haven't got to it yet.
>> Sorry for the confusion.
>>
>> Like I said, at this point I was just asking about linux-next inclusion,
>> and how that all worked.
> OK, I should have said that linux-next is for patches that have passed
> review and unit testing and are essentially ready to go to Linus (or your
> upstream tree).
Then we're down to just the thinkpad ACPI nested functions patch which
fits those criteria.
I will remove the other patches (since they haven't been reviewed by the
appropriate kernel community yet), and we will only add patches to that
branch that satisfy those rules.
Thanks,
Behan
--
Behan Webster
behanw@converseincode.com
next prev parent reply other threads:[~2014-02-19 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5303C695.4030403@converseincode.com>
2014-02-19 0:17 ` linux-next Stephen Rothwell
2014-02-19 2:17 ` linux-next Behan Webster
2014-02-19 6:07 ` linux-next Sam Ravnborg
2014-02-19 6:12 ` linux-next Behan Webster
2014-02-19 6:22 ` linux-next Stephen Rothwell
2014-02-19 18:06 ` Behan Webster [this message]
2014-02-20 0:03 ` linux-next Stephen Rothwell
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=5304F28D.5070604@converseincode.com \
--to=behanw@converseincode.com \
--cc=dl9pf@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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