All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: brking@linux.vnet.ibm.com
Cc: Tejun Heo <htejun@gmail.com>,
	jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/3] libata: Initialize nbytes for internal sg commands
Date: Mon, 22 Jan 2007 15:00:17 -0600	[thread overview]
Message-ID: <45B525E1.8040502@linux.vnet.ibm.com> (raw)
In-Reply-To: <45AFD151.7050800@linux.vnet.ibm.com>

Brian King wrote:
> Tejun Heo wrote:
>> Brian King wrote:
>>> Some LLDDs, like ipr, use nbytes and pad_len to determine
>>> the total data transfer length of a command. Make sure
>>> nbytes gets initialized for internally generated commands.
>> I think it's better to apply the following patch instead of this one.
>>
>> http://article.gmane.org/gmane.linux.ide/14792
> 
> Works for me. I loaded that patch in place of this one and verified
> it solved my problem as well. I still need the other two patches in
> this series, however.

Jeff,

Do you plan to pull this patch series into upstream-fixes? Without these
three patches (or 1 & 3 plus Tejun's patch referenced above), ipr SATA
is broken in 2.6.20.

Thanks,

Brian

-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center

  reply	other threads:[~2007-01-22 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11690587311891-patch-mail.ibm.com>
2007-01-17 18:32 ` [PATCH 2/3] libata: Initialize nbytes for internal sg commands Brian King
2007-01-18  1:35   ` Tejun Heo
2007-01-18 19:58     ` Brian King
2007-01-22 21:00       ` Brian King [this message]
2007-01-17 18:32 ` [PATCH 3/3] libata: Initialize qc->pad_len Brian King

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=45B525E1.8040502@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=htejun@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.