Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: port and device of libata.force ID separated by point
Date: Fri, 23 Apr 2010 02:37:44 +0200	[thread overview]
Message-ID: <4BD0EBD8.9060308@kernel.org> (raw)
In-Reply-To: <201004211217.12697.roman.fietze@telemotive.de>

On 04/21/2010 12:17 PM, Roman Fietze wrote:
> Hello,
> 
> If I understand libata-core correctly, esp. arround line 6572:
> 
> 	/* parse id */
> 	p = strchr(id, '.');
> 	...
> 
> the optional device is separated from the port in the libata.force ID
> by a point or dot instead of by a colon.
> 
> If my assumption is correct, this patch will fix the documentation:
> 
> Signed-off-by: Roman Fietze <roman.fietze@telemotive.de>

Heh, nice catch.

Acked-by: Tejun Heo <tj@kernel.org>

Thanks.

-- 
tejun

  reply	other threads:[~2010-04-23  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 10:17 [PATCH] libata: port and device of libata.force ID separated by point Roman Fietze
2010-04-23  0:37 ` Tejun Heo [this message]
2010-04-23  1:52 ` 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=4BD0EBD8.9060308@kernel.org \
    --to=tj@kernel.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=roman.fietze@telemotive.de \
    /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