From: Jeff Garzik <jgarzik@pobox.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Oliver Weihe <o.weihe@deltacomputer.de>, linux-ide@vger.kernel.org
Subject: Re: additional PCI device ID for the sata_svw driver
Date: Tue, 17 Jan 2006 08:37:46 -0500 [thread overview]
Message-ID: <43CCF32A.9080508@pobox.com> (raw)
In-Reply-To: <1137224156.4854.59.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> On Wed, 2006-01-11 at 19:23 +0100, Oliver Weihe wrote:
>
>>Hello,
>>
>>please add the following device ID into the sata_svw driver:
>
>
> Jeff, you'll take care of it or do you want me to submit a patch ? I'm
> more than happy to leave you maintainership of this driver ;)
Just took care of it...
Jeff
next prev parent reply other threads:[~2006-01-17 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 18:23 additional PCI device ID for the sata_svw driver Oliver Weihe
2006-01-14 7:35 ` Benjamin Herrenschmidt
2006-01-17 13:37 ` Jeff Garzik [this message]
2006-01-17 12:58 ` 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=43CCF32A.9080508@pobox.com \
--to=jgarzik@pobox.com \
--cc=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=o.weihe@deltacomputer.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;
as well as URLs for NNTP newsgroup(s).