linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, hellan@acm.org,
	Carlos.Pardo@siliconimage.com, Raymond.Liu@siliconimage.com
Subject: Re: [PATCH 1/3] sata_sil: add board ID for 3512
Date: Sat, 25 Feb 2006 13:33:02 +0900	[thread overview]
Message-ID: <43FFDDFE.7020606@gmail.com> (raw)
In-Reply-To: <114084184662-git-send-email-htejun@gmail.com>

Tejun Heo wrote:
> 3512 is slightly different from 3112 errata-wise.  Differentiate it.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> 

Wow, script mix up. Sorry. Please ignore this series. Will resend.

-- 
tejun

       reply	other threads:[~2006-02-25  4:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <114084184662-git-send-email-htejun@gmail.com>
2006-02-25  4:33 ` Tejun Heo [this message]
2006-02-25  4:52 [PATCHSET, RESEND] sata_sil: R_ERR on DMA activate FIS errata workaround Tejun Heo
2006-02-25  4:52 ` [PATCH 1/3] sata_sil: add board ID for 3512 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=43FFDDFE.7020606@gmail.com \
    --to=htejun@gmail.com \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=Raymond.Liu@siliconimage.com \
    --cc=hellan@acm.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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).