From: Jens Axboe <jens.axboe@oracle.com>
To: Alistair John Strachan <alistair@devzero.co.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
xfs@oss.sgi.com, neilb@suse.de
Subject: Re: XFS/md/blkdev warning (was Re: Linux 2.6.26-rc2)
Date: Mon, 12 May 2008 18:40:53 +0200 [thread overview]
Message-ID: <20080512164053.GD16217@kernel.dk> (raw)
In-Reply-To: <200805121726.15576.alistair@devzero.co.uk>
On Mon, May 12 2008, Alistair John Strachan wrote:
> I've been getting this since -rc1. It's still present in -rc2, so I thought
> I'd bug some people. Everything seems to be working fine.
>
> I'm not sure who's to blame here so I've added a few people to CC; if I've
> done so in error, sorry for the noise.
>
> The taint is from loading a custom (fixed) DSDT which I've been doing for
> ages, and which shouldn't affect this trace.
Neil should have a pending patch for this warning. Don't worry about it
:-)
--
Jens Axboe
next prev parent reply other threads:[~2008-05-12 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.1.10.0805120731480.3188@woody.linux-foundation.org>
2008-05-12 16:26 ` XFS/md/blkdev warning (was Re: Linux 2.6.26-rc2) Alistair John Strachan
2008-05-12 16:40 ` Jens Axboe [this message]
2008-05-12 16:47 ` Linus Torvalds
2008-05-12 16:49 ` Jens Axboe
2008-05-13 1:05 ` [PATCH] Remove blkdev warning triggered by using md Neil Brown
2008-05-17 18:22 ` XFS/md/blkdev warning (was Re: Linux 2.6.26-rc2) Alistair John Strachan
2008-05-17 18:37 ` Linus Torvalds
2008-05-17 18:41 ` Linus Torvalds
2008-05-17 20:09 ` Alistair John Strachan
2008-05-17 21:17 ` Linus Torvalds
2008-05-17 23:12 ` Alistair John Strachan
2008-05-17 23:39 ` Christoph Hellwig
2008-05-18 14:12 ` Alistair John Strachan
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=20080512164053.GD16217@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=alistair@devzero.co.uk \
--cc=neilb@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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