From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: enricoss@tiscali.it, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: hsm violation
Date: Mon, 25 Jun 2007 11:15:06 +0900 [thread overview]
Message-ID: <467F252A.5070607@gmail.com> (raw)
In-Reply-To: <20070624123022.541f2f78.akpm@linux-foundation.org>
Andrew Morton wrote:
> That great spew of "set_level status: 0" is fairly annoying and useless.
I don't know where those are coming from. It's not from libata.
--
tejun
next prev parent reply other threads:[~2007-06-25 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <467E6456.4030503@tiscali.it>
2007-06-24 19:30 ` hsm violation Andrew Morton
2007-06-25 2:15 ` Tejun Heo [this message]
[not found] <fa.sspu6LOivd/touNtS2IsMKPqHa0@ifi.uio.no>
[not found] ` <fa.19XJG1Asdp1zwcWLxolIH6F+5lY@ifi.uio.no>
2007-06-24 19:42 ` Robert Hancock
2007-06-25 2:12 ` Tejun Heo
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=467F252A.5070607@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=enricoss@tiscali.it \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).