Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* please add for-next/seccomp
@ 2020-06-18 21:00 Kees Cook
  2020-06-21 21:27 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Kees Cook @ 2020-06-18 21:00 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Linux Next Mailing List

Hi Stephen,

Can you please add my "for-next/seccomp" tree to linux-next? I've been
including it in the already added "for-next/kspp" tree, but I'd rather
have it be its own tree for linux-next, as it is ultimately its own topic.

https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/seccomp

Thanks!

-Kees

-- 
Kees Cook

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: please add for-next/seccomp
  2020-06-18 21:00 please add for-next/seccomp Kees Cook
@ 2020-06-21 21:27 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2020-06-21 21:27 UTC (permalink / raw)
  To: Kees Cook; +Cc: Linux Next Mailing List


[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

Hi Kees,

On Thu, 18 Jun 2020 14:00:44 -0700 Kees Cook <keescook@chromium.org> wrote:
>
> Can you please add my "for-next/seccomp" tree to linux-next? I've been
> including it in the already added "for-next/kspp" tree, but I'd rather
> have it be its own tree for linux-next, as it is ultimately its own topic.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/seccomp

I have added

git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git branch for-next/seccomp

from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux 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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-18 21:00 please add for-next/seccomp Kees Cook
2020-06-21 21:27 ` Stephen Rothwell

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git