From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: linux-next: manual merge of the vfs-miklos tree with the overlayfs tree and build failure
Date: Fri, 3 Feb 2017 20:03:46 +1100 [thread overview]
Message-ID: <20170203200346.7f80d372@canb.auug.org.au> (raw)
In-Reply-To: <CAJfpegtAZkenPkE0NHUfeSFcCJmBygVqCh8_yaVRqLj-5hjKEQ@mail.gmail.com>
Hi Miklos,
On Fri, 3 Feb 2017 09:35:09 +0100 Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> Sorry, I removed the conflicting content from that tree.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-02-03 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 0:16 linux-next: manual merge of the vfs-miklos tree with the overlayfs tree and build failure Stephen Rothwell
2017-01-31 6:47 ` Amir Goldstein
2017-01-31 10:38 ` Stephen Rothwell
2017-02-02 22:34 ` Stephen Rothwell
2017-02-03 8:35 ` Miklos Szeredi
2017-02-03 9:03 ` 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=20170203200346.7f80d372@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=amir73il@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).