linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "\"Jörn Engel\"" <joern@logfs.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kent Overstreet <kmo@daterainc.com>, Jens Axboe <axboe@kernel.dk>,
	Takashi Iwai <tiwai@suse.de>
Subject: linux-next: build failure after merge of the bcon tree
Date: Tue, 5 Nov 2013 16:29:22 +1100	[thread overview]
Message-ID: <20131105162922.441f612bd17f6fa977c39e89@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

Hi Jörn,

After merging the bcon tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/block/blockconsole.c: In function 'sync_read':
drivers/block/blockconsole.c:184:5: error: 'struct bio' has no member named 'bi_idx'
  bio.bi_idx = 0;
     ^
drivers/block/blockconsole.c:185:5: error: 'struct bio' has no member named 'bi_size'
  bio.bi_size = SECTOR_SIZE;
     ^
drivers/block/blockconsole.c:187:5: error: 'struct bio' has no member named 'bi_sector'
  bio.bi_sector = ofs >> SECTOR_SHIFT;
     ^
drivers/block/blockconsole.c: In function 'bcon_erase_segment':
drivers/block/blockconsole.c:215:6: error: 'struct bio' has no member named 'bi_size'
   bio->bi_size = PAGE_SIZE;
      ^
drivers/block/blockconsole.c:218:6: error: 'struct bio' has no member named 'bi_idx'
   bio->bi_idx = 0;
      ^
drivers/block/blockconsole.c:219:6: error: 'struct bio' has no member named 'bi_sector'
   bio->bi_sector = (bc->write_bytes + i * PAGE_SIZE) >> 9;
      ^
drivers/block/blockconsole.c: In function 'bcon_writesector':
drivers/block/blockconsole.c:338:5: error: 'struct bio' has no member named 'bi_size'
  bio->bi_size = SECTOR_SIZE;
     ^
drivers/block/blockconsole.c:343:5: error: 'struct bio' has no member named 'bi_idx'
  bio->bi_idx = 0;
     ^
drivers/block/blockconsole.c:344:5: error: 'struct bio' has no member named 'bi_sector'
  bio->bi_sector = bc->write_bytes >> 9;
     ^

Caused by changes in the block tree.  Thierry Reding mentioned that you
didn't think that the bcon tree was linux-next material any more, so I
just dropped your tree.  If that is incorrect, please let me know and I
will reinstate it and fix this merge conflict.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2013-11-05  5:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131105162922.441f612bd17f6fa977c39e89@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=joern@logfs.org \
    --cc=kmo@daterainc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).