From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Kleikamp <dave.kleikamp@oracle.com>,
Jeff Layton <jlayton@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Jan Kara <jack@suse.cz>, Matthew Wilcox <mawilcox@microsoft.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] JFS: do not ignore return code from write_one_page()
Date: Mon, 29 May 2017 09:23:01 +1000 [thread overview]
Message-ID: <20170529092301.5055288f@canb.auug.org.au> (raw)
In-Reply-To: <20170526233600.100aed6f6568e5f6119e9740@linux-foundation.org>
Hi Andrew,
On Fri, 26 May 2017 23:36:00 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Fri, 26 May 2017 15:48:51 -0500 Dave Kleikamp <dave.kleikamp@oracle.com> wrote:
>
> > Andrew,
> >
> > Do you want to pick this up into akpm-current? I could push it through
> > the jfs tree, but without the change to write_one_page(), my version of
> > the patch would need a manual merge. It'd be a simple one, so maybe
> > that's not a big deal.
>
> Yes, I'll add this to Jeff's series, thanks.
I have added this to linux-next today.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-05-28 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 2:43 linux-next: build warning after merge of the akpm-current tree Stephen Rothwell
2017-05-26 10:16 ` Jeff Layton
2017-05-26 11:28 ` Dave Kleikamp
2017-05-26 20:45 ` [PATCH] JFS: do not ignore return code from write_one_page() Dave Kleikamp
2017-05-26 20:48 ` Dave Kleikamp
2017-05-27 6:36 ` Andrew Morton
2017-05-28 23:23 ` 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=20170529092301.5055288f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=dave.kleikamp@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=ross.zwisler@linux.intel.com \
/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).