From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: Please add extable branch to linux-next
Date: Wed, 22 Feb 2017 13:19:36 -0500 [thread overview]
Message-ID: <20170222181936.GE8577@windriver.com> (raw)
In-Reply-To: <20170125095006.141e71c8@canb.auug.org.au>
[Re: Please add extable branch to linux-next] On 25/01/2017 (Wed 09:50) Stephen Rothwell wrote:
> Hi Paul,
>
> On Tue, 24 Jan 2017 16:42:08 -0500 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> > Would you please add the "extable" branch to linux-next for a once around
> > addition from this repo?
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux.git
>
> Added from today. If I forget to remove it once it is merged, please
> just remind me, thanks.
This has now been merged and can be removed.
Thanks,
Paul.
next prev parent reply other threads:[~2017-02-22 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 21:42 Please add extable branch to linux-next Paul Gortmaker
2017-01-24 22:50 ` Stephen Rothwell
2017-02-22 18:19 ` Paul Gortmaker [this message]
2017-02-22 20:53 ` 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=20170222181936.GE8577@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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