From: Philipp Reisner <philipp.reisner@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars Ellenberg <lars.ellenberg@linbit.com>
Subject: Re: linux-next: build failure after merge of the final tree (block tree related)
Date: Thu, 17 Mar 2011 15:01:32 +0100 [thread overview]
Message-ID: <201103171501.32703.philipp.reisner@linbit.com> (raw)
In-Reply-To: <4D81DFA4.7000204@kernel.dk>
Am Donnerstag, 17. März 2011, um 11:17:08 schrieb Jens Axboe:
> On 2011-03-17 00:31, Stephen Rothwell wrote:
> > Hi Jens,
> >
> > On Fri, 11 Mar 2011 08:12:38 +0100 Jens Axboe <axboe@kernel.dk> wrote:
> >> On 2011-03-11 07:58, Stephen Rothwell wrote:
> >>> After merging the final tree, today's linux-next build (powerpc
> >>> allyesconfig) failed like this:
> >>>
> >>> drivers/char/tpm/tpm_tis.c:96: warning: 'is_itpm' defined but not used
> >>> drivers/block/drbd/drbd_bitmap.c: In function '__bm_change_bits_to':
> >>> drivers/block/drbd/drbd_bitmap.c:1287: error: implicit declaration of
> >>> function 'generic___test_and_set_le_bit'
> >>> drivers/block/drbd/drbd_bitmap.c:1289: error: implicit declaration of
> >>> function 'generic___test_and_clear_le_bit'
> >>> drivers/block/drbd/drbd_bitmap.c: In function 'drbd_bm_test_bit':
> >>> drivers/block/drbd/drbd_bitmap.c:1438: error: implicit declaration of
> >>> function 'generic_test_le_bit'
> >>>
> >>> Caused by commit 4b0715f09655 ("drbd: allow petabyte storage on 64bit
> >>> arch").
> >>
> >>> I have applied this patch for today (surely there is a better way):
> >> Thanks for not dropping it, I'll let the drbd guys send in a proper fix
> >> and get it committed.
> >
> > Ping?
>
> Lars, please send me a fix for this ASAP. It's holding up the block
> merge.
Hi Jens,
Please use Stephen's patch for the merge. It is perfectly valid.
Lars is in the progress of preparing a suggestion for a much
broader cleanup/fix for the little-endian bitops topic.
But that should not delay the the block merge, nor is it necessary
for the drbd updates. He plans to have that ready by tomorrow.
Best,
Phil
--
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2011-03-17 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 6:58 linux-next: build failure after merge of the final tree (block tree related) Stephen Rothwell
2011-03-11 7:12 ` Jens Axboe
2011-03-14 8:33 ` Lars Ellenberg
2011-03-16 23:31 ` Stephen Rothwell
2011-03-17 10:17 ` Jens Axboe
2011-03-17 14:01 ` Philipp Reisner [this message]
2011-03-18 8:56 ` [PATCH RFC] consolidate *_le_bit operations [was linux-next: build failure after merge of the final tree (block tree related)] Lars Ellenberg
-- strict thread matches above, loose matches on Subject: below --
2013-03-26 6:31 linux-next: build failure after merge of the final tree (block tree related) Stephen Rothwell
2013-04-01 23:22 ` Stephen Rothwell
2013-04-02 3:56 ` Stephen Rothwell
2010-07-09 4:39 Stephen Rothwell
2010-07-09 12:54 ` Arnd Bergmann
2010-07-09 12:56 ` Jens Axboe
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=201103171501.32703.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=axboe@kernel.dk \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).