From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-next@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: request new tree for linux-next
Date: Thu, 18 Aug 2016 20:28:23 +1000 [thread overview]
Message-ID: <20160818202823.621fdebc@canb.auug.org.au> (raw)
In-Reply-To: <CAJfpegtBESANiPjGGbMetJ4h+X_QR2c35BnaCShmH4hfepMwjA@mail.gmail.com>
Hi Miklos,
On Thu, 18 Aug 2016 08:45:31 +0200 Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> Via Al.
OK.
> I plan to post these, but they are conflict prone so I think it's
> worth getting them into -next ASAP.
Posted, reviewed, unit tested ... *then* into linux-next, please.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-08-18 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 12:58 request new tree for linux-next Miklos Szeredi
2016-08-17 23:48 ` Stephen Rothwell
2016-08-18 6:45 ` Miklos Szeredi
2016-08-18 10:28 ` Stephen Rothwell [this message]
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=20160818202823.621fdebc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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