linux-kernel - Re: linux-next submission requirements (Was: [RFC PATCH] linker script: unify usage of discard definition)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 04 Jul 2009 12:18:02 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org
Subject: Re: linux-next submission requirements (Was: [RFC PATCH] linker script:
 unify usage of discard definition)

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@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/