From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: build failure after merge of the file-locks tree
Date: Wed, 17 May 2017 11:48:05 +1000 [thread overview]
Message-ID: <20170517114805.57714a7a@canb.auug.org.au> (raw)
In-Reply-To: <1494983403.21644.8.camel@poochiereds.net>
Hi Jeff,
On Tue, 16 May 2017 21:10:03 -0400 Jeff Layton <jlayton@poochiereds.net> wrote:
>
> I think this patch will probably fix it, but I don't have a 32-bit host
> set up to build on just now. I'll go ahead and merge this into the
> branch, and will plan to test it tomorrow (hopefully before the next
> fetch).
Thanks. If you don't get around to testing, I will let you know if it
still fails tomorrow :-)
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-05-17 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 0:27 linux-next: build failure after merge of the file-locks tree Stephen Rothwell
2017-05-17 1:10 ` Jeff Layton
2017-05-17 1:48 ` Stephen Rothwell [this message]
2017-05-17 12:32 ` Jeff Layton
2017-05-17 12:35 ` Stephen Rothwell
2017-05-17 23:45 ` 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=20170517114805.57714a7a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).