From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition)
Date: Sat, 04 Jul 2009 12:18:02 +0900 [thread overview]
Message-ID: <4A4EC9EA.9070005@kernel.org> (raw)
In-Reply-To: <20090704113448.49a722d2.sfr@canb.auug.org.au>
Hello,
Stephen Rothwell wrote:
> Hi Tejun,
>
> [This is not aimed just at you ... this patch just gave me an
> opportunity to point this out again.]
>
> On Sat, 04 Jul 2009 08:37:28 +0900 Tejun Heo <tj@kernel.org> wrote:
>> This patch is on top of the current percpu#for-next.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-next
>>
>> Thanks.
>>
>> NOT_SIGNED_OFF_YET
>
> Well, given no SOB and that this is a RFC patch, it should *not* be in a
> branch that is pulled into linux-next.
It's not _in_ the branch. It's on _top_ of the branch.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-07-04 3:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 23:37 [RFC PATCH] linker script: unify usage of discard definition Tejun Heo
2009-07-03 23:37 ` Tejun Heo
2009-07-04 1:34 ` linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition) Stephen Rothwell
2009-07-04 3:18 ` Tejun Heo [this message]
2009-07-04 4:03 ` Stephen Rothwell
2009-07-04 4:07 ` Tejun Heo
2009-07-04 5:51 ` [RFC PATCH] linker script: unify usage of discard definition Mike Frysinger
2009-07-04 5:51 ` Mike Frysinger
2009-07-04 15:37 ` Paul Mundt
2009-07-04 18:40 ` [microblaze-uclinux] " Michal Simek
2009-07-06 6:17 ` Michal Simek
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=4A4EC9EA.9070005@kernel.org \
--to=tj@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.