linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: 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: Pull Request for linux-next
Date: Sun, 25 Feb 2018 18:59:07 +1100	[thread overview]
Message-ID: <20180225075907.GB9456@eros> (raw)

Hi Stephen,

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?


thanks,
Tobin.

             reply	other threads:[~2018-02-25  7:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25  7:59 Tobin C. Harding [this message]
2018-02-25 20:54 ` Pull Request for linux-next Stephen Rothwell
2018-02-25 22:13   ` Tobin C. Harding
  -- 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=20180225075907.GB9456@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).