mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Cc: 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 12:29:38 -0600	[thread overview]
Message-ID: <86e4eb4c-3cb8-8e0f-ebb4-48cdf4dea8e8@fb.com> (raw)
In-Reply-To: <CA+55aFwnNLqsuL_LwAV4OYQf9v+pje5w=OwoE=oA-R8QpXB-Cg@mail.gmail.com>

On 07/27/2016 11:46 AM, Linus Torvalds wrote:
> On Tue, Jul 26, 2016 at 9:08 PM, Jaegeuk Kim <jaegeuk@kernel.org> wrote:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/for-f2fs-4.8
>
> This got some merge conflicts with the bio interface rework
> (bio_set_op_attrs() etc), and while I tried to fix it up, I don't have
> any sane way to test the end result, so I might have screwed up
> royally.
>
> My resolution looks sane to me, and compiles, but that's all I'm
> really going to guarantee. Can you please give it a good round of
> testing, and Jens, can you check it out too. In particular, the
> fs/f2fs/data.c changes is what I might have screwed up..

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);

-- 
Jens Axboe

  reply	other threads:[~2016-07-27 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  4:08 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 [this message]
2016-07-27 18:46     ` Linus Torvalds
2016-07-27 18:47       ` Jens Axboe
2016-07-27 21:02       ` Jaegeuk Kim

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=86e4eb4c-3cb8-8e0f-ebb4-48cdf4dea8e8@fb.com \
    --to=axboe@fb.com \
    --cc=jaegeuk@kernel.org \
    --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

Powered by JetHome