linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (block tree related)
Date: Fri, 09 Jul 2010 14:56:24 +0200	[thread overview]
Message-ID: <4C371C78.1010701@kernel.dk> (raw)
In-Reply-To: <201007091454.09011.arnd@arndb.de>

On 2010-07-09 14:54, Arnd Bergmann wrote:
> On Friday 09 July 2010, Stephen Rothwell wrote:
> 
>> I applied the following patch for today:
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Fri, 9 Jul 2010 14:24:38 +1000
>> Subject: [PATCH] block: fix for block tracing build error
>>
>> block/compat_ioctl.c: In function 'compat_blkdev_ioctl':
>> block/compat_ioctl.c:754: error: 'BLKTRACESETUP32' undeclared (first use in this function)
> 
> Yes, the fix looks right, sorry about the breakage.
> I only tested with CONFIG_BLOCK_TRACE enabled, so I did not
> catch this.
> 
> Jens, please apply Stephen's patch.

Added, thanks Stephen.

-- 
Jens Axboe

  reply	other threads:[~2010-07-09 12:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09  4:39 linux-next: build failure after merge of the final tree (block tree related) Stephen Rothwell
2010-07-09 12:54 ` Arnd Bergmann
2010-07-09 12:56   ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-11  6:58 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
2013-03-26  6:31 Stephen Rothwell
2013-04-01 23:22 ` Stephen Rothwell
2013-04-02  3:56   ` Stephen Rothwell

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=4C371C78.1010701@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=arnd@arndb.de \
    --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).