From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@fb.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS Dev Mailing List <linux-fsdevel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL] f2fs for 4.8
Date: Wed, 27 Jul 2016 14:02:36 -0700 [thread overview]
Message-ID: <20160727210236.GA73525@jaegeuk> (raw)
In-Reply-To: <CA+55aFx+v=iM2t+4OhF2AqbdszNYWt6677C2LvX-iYmDEnh_Rg@mail.gmail.com>
On Wed, Jul 27, 2016 at 11:46:11AM -0700, Linus Torvalds wrote:
> On Wed, Jul 27, 2016 at 11:29 AM, Jens Axboe <axboe@fb.com> wrote:
> >
> > Looks OK to me, though I think you could have dropped the ->bi_rw
> > assignment in f2fs_submit_page_bio():
> >
> > bio->bi_rw = fio->op_flags;
> > bio_set_op_attrs(bio, fio->op, fio->op_flags);
> >
> > __submit_bio(fio->sbi, bio, fio->type);
>
> Ahh, yes. I'll add a patch to drop that line, unless you just want to
> do it yourself (or Jaegeuk Kim wants to do it in the f2fs tree).
Actually, I was writing an email to point that out. :)
Thanks to Jens for the patch for this.
Anyway, the changes look good to me as well.
> Jaegeuk, I'd still really want confirmation that it all actually
> works. The extra line should be harmless, even if Jens is right that
> it is ugly and wrong. It might be worth testing with that line
> removed.
I've confirmed that there is no problem; I've checked a round of xfstests and
fsstress test.
Thank you for resolving the conflicts.
Thanks,
prev parent reply other threads:[~2016-07-27 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 4:08 [GIT PULL] f2fs for 4.8 Jaegeuk Kim
2016-07-27 8:41 ` Christoph Hellwig
2016-07-27 21:24 ` Jaegeuk Kim
2016-07-27 17:46 ` Linus Torvalds
2016-07-27 18:29 ` Jens Axboe
2016-07-27 18:46 ` Linus Torvalds
2016-07-27 18:47 ` Jens Axboe
2016-07-27 21:02 ` Jaegeuk Kim [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=20160727210236.GA73525@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=axboe@fb.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).