From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: "linux-arch@vger•kernel.org" <linux-arch@vger•kernel.org>,
Linux Kernel <linux-kernel@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition)
Date: Sat, 4 Jul 2009 11:34:48 +1000 [thread overview]
Message-ID: <20090704113448.49a722d2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A4E9638.20304@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
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.
This is what I send to any maintainer that submits a tree for linux-next
inclusion (and before anyone else points it out: this was not true early
on):
"all patches/commits in the tree/series must have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next 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@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2009-07-04 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A4E9638.20304@kernel.org>
2009-07-04 1:34 ` Stephen Rothwell [this message]
2009-07-04 3:18 ` linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition) Tejun Heo
2009-07-04 4:03 ` Stephen Rothwell
2009-07-04 4:07 ` Tejun Heo
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=20090704113448.49a722d2.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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