linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes] libata: set device class to NONE if phys_offline
Date: Thu, 23 Oct 2008 12:01:38 +0900	[thread overview]
Message-ID: <48FFE912.9050508@kernel.org> (raw)
In-Reply-To: <48FEFF23.5090006@ru.mvista.com>

Sergei Shtylyov wrote:
>> As on/offliness semantics is strictly defined and used in multiple
>>   
> 
>   More grammar nitpicking: it's either on/offline or on/offlineness. :-)

Right.  I'll keep it in mind.  I'm so glad that you're reviewing
libata changes.  Thanks.  :-)

-- 
tejun

  reply	other threads:[~2008-10-23  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 15:31 [PATCH #upstream-fixes] libata: set device class to NONE if phys_offline Tejun Heo
2008-10-22 10:23 ` Sergei Shtylyov
2008-10-23  3:01   ` Tejun Heo [this message]
2008-10-23  0:42 ` Jeff Garzik

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=48FFE912.9050508@kernel.org \
    --to=tj@kernel.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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).