From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Prakash Surya <surya1@llnl.gov>,
"John L. Hammond" <john.hammond@intel.com>
Subject: Re: linux-next: manual merge of the staging tree with the vfs-miklos tree
Date: Wed, 28 Sep 2016 17:02:04 +1000 [thread overview]
Message-ID: <20160928170204.0d951d15@canb.auug.org.au> (raw)
In-Reply-To: <20160928062501.GA19141@kroah.com>
Hi Greg,
On Wed, 28 Sep 2016 08:25:01 +0200 Greg KH <greg@kroah.com> wrote:
>
> Looks good to me, one of these days we will get lustre out of staging to
> make this easier...
I look forward to it :-)
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-09-28 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 5:00 linux-next: manual merge of the staging tree with the vfs-miklos tree Stephen Rothwell
2016-09-28 6:25 ` Greg KH
2016-09-28 7:02 ` 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=20160928170204.0d951d15@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=john.hammond@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=surya1@llnl.gov \
--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;
as well as URLs for NNTP newsgroup(s).