public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [GIT PULL] Core block IO changes for 3.14
Date: Wed, 29 Jan 2014 08:40:14 -0700	[thread overview]
Message-ID: <20140129154014.GP25989@kernel.dk> (raw)
In-Reply-To: <CAMuHMdWdvSUV6-nWQ5w5TAYhSQBm20ruhaDj9y08jd5EMo=yGA@mail.gmail.com>

On Wed, Jan 29 2014, Geert Uytterhoeven wrote:
> Hi Jens,
> 
> On Wed, Jan 29, 2014 at 4:17 PM, Jens Axboe <axboe@kernel.dk> wrote:
> > On Wed, Jan 29 2014, Geert Uytterhoeven wrote:
> >> On Tue, Jan 28, 2014 at 11:52 PM, Jens Axboe <axboe@kernel.dk> wrote:
> >> >> - Finally the immutable biovec changes from Kent Overstreet. This
> >> >>   enables some nice future work on making arbitrarily sized bios
> >> >>   possible, and splitting more efficient. Related fixes to immutable
> >> >>   bio_vecs:
> >> >>
> >> >>         - dm-cache immutable fixup from Mike Snitzer.
> >> >>         - btrfs immutable fixup from Muthu Kumar.
> >> >>
> >> >> - bio-integrity fix from Nic Bellinger, which is also going to stable.
> >> >>
> >> >>
> >> >> Please pull! There will be a bit of merge work for you, but it should be
> >> >> fairly straight forward. It's mostly related to changin:
> >> >>
> >> >> bio->bi_sector  -> bio->bi_iter.bi_sector
> >> >> bio->bi_size    -> bio->bi_iter.bi_size
> >> >>
> >> >>
> >> >> git://git.kernel.dk/linux-block.git for-3.14/core
> >> >
> >> > BTW, let me know if you want me to merge this. The above has been in
> >> > for-next since forever, and Stephen has carried a fix or two for new
> >> > merges.
> >>
> >> arch/xtensa/platforms/iss/simdisk.c:108:23: error: 'struct bio' has no
> >> member named 'bi_sector'
> >>
> >> http://kisskb.ellerman.id.au/kisskb/buildresult/10542666/
> >
> > Does the below fix it for you? There's an existing bug in there where it
> > kunmaps the wrong part (page instead of the address). Not sure that
> > matters on xtensa or whether the kmaps are a no-op, but cleaned up none
> > the less.
> 
> Yes, it does. Thanks!

Thanks for testing!

> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Added.

Linus, I queued up this patch, it's in for-3.14/core as well. This will
offset the inserted/deleted lines by 7/7.

-- 
Jens Axboe


      reply	other threads:[~2014-01-29 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 22:43 [GIT PULL] Core block IO changes for 3.14 Jens Axboe
2014-01-28 22:52 ` Jens Axboe
2014-01-29  0:05   ` Stephen Rothwell
2014-01-29  0:45     ` Jaegeuk Kim
2014-01-30 19:26       ` Linus Torvalds
2014-01-29  9:26   ` Geert Uytterhoeven
2014-01-29 15:17     ` Jens Axboe
2014-01-29 15:31       ` Geert Uytterhoeven
2014-01-29 15:40         ` Jens Axboe [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=20140129154014.GP25989@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chris@zankel.net \
    --cc=geert@linux-m68k.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.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