From: "Tobin C. Harding" <me@tobin.cc>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tycho@tycho.ws, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Pull Request for linux-next
Date: Mon, 26 Feb 2018 09:13:39 +1100 [thread overview]
Message-ID: <20180225221339.GA2808@eros> (raw)
In-Reply-To: <20180226075422.6d55953d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2209 bytes --]
On Mon, Feb 26, 2018 at 07:54:22AM +1100, Stephen Rothwell wrote:
> Hi Tobin,
>
> On Sun, 25 Feb 2018 18:59:07 +1100 "Tobin C. Harding" <me@tobin.cc> wrote:
> >
> > Would it be possible to get the development tree for
> > scripts/leaking_addresses.pl included in Linux-next please.
> >
> > The tree is hosted on kernel.org
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tobin/leaks.git/
> >
> > I have created a branch called linux-next. This branch is not tagged or
> > signed. I'm super new to kernel maintainer branch management, ATM the
> > tree mirrors GregKH's staging tree setup i.e 3 branches
> >
> > master
> > leaks-testing
> > leaks-next
> >
> > Development done on leaks-testing. Once patches have been rinsed
> > through LKML move them to leaks-next. Any holes in that?
>
> That looks fine to me. I have added your leaks-next branch from
> today. It would be nice to see some Reviewed-by or Acked-by tags on
> your commits.
Yeah I know that would be awesome, there doesn't seem to be a lot of
interest in this script ATM. None of my recent patches have gotten any
comments what so ever. We have a second maintainer now though so
hopefully there will be at least two sets of eyes going over it.
> Thanks for adding your subsystem tree as a participant of linux-next. As
> you may know, this is not a judgement of your code.
lol, that line made my heart jump into mouth ready for the comment to
come :)
> 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,
Tobin.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-02-25 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 7:59 Pull Request for linux-next Tobin C. Harding
2018-02-25 20:54 ` Stephen Rothwell
2018-02-25 22:13 ` Tobin C. Harding [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-21 8:14 Greentime Hu
2018-02-22 0:29 ` Stephen Rothwell
2018-02-22 3:36 ` Greentime Hu
2018-02-22 4:28 ` Stephen Rothwell
2017-10-31 20:43 Palmer Dabbelt
2017-10-31 21:21 ` Stephen Rothwell
2009-11-15 16:35 PULL request " Tejun Heo
2009-11-15 22:52 ` 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=20180225221339.GA2808@eros \
--to=me@tobin.cc \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tycho@tycho.ws \
/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.