From: Tejun Heo <tj@kernel.org>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: WARNING: at drivers/block/floppy.c:2929 do_fd_request+0xb7/0xb9()
Date: Thu, 15 Dec 2011 10:44:10 -0800 [thread overview]
Message-ID: <CAOS58YPj1Qc_dfMc83P3ifRAnKW7d828SBxTZK1dc=wMDb6iXQ@mail.gmail.com> (raw)
In-Reply-To: <4EEA0C39.4050900@canonical.com>
Hello,
On Thu, Dec 15, 2011 at 7:03 AM, Tim Gardner <tim.gardner@canonical.com> wrote:
> Tejun - is your patch from https://lkml.org/lkml/2011/12/5/421 in the
> pipeline ? We've got some test machines that are incurring many instances of
> this warning. I noticed that Wu Fengguang also complained about it in
> https://lkml.org/lkml/2011/11/2/208.
Ooh, I think I forgot to send proper patch for that. Sending it now.
Thanks for reminding me.
--
tejun
prev parent reply other threads:[~2011-12-15 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 15:03 WARNING: at drivers/block/floppy.c:2929 do_fd_request+0xb7/0xb9() Tim Gardner
2011-12-15 18:44 ` Tejun Heo [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='CAOS58YPj1Qc_dfMc83P3ifRAnKW7d828SBxTZK1dc=wMDb6iXQ@mail.gmail.com' \
--to=tj@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.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;
as well as URLs for NNTP newsgroup(s).