linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Resch <jr@xor.at>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: Inclusion of patch for Promise SATAII 150 TX4 in mainline 2.6 kernel?
Date: Sun, 06 Feb 2005 14:39:26 +0100	[thread overview]
Message-ID: <42061E0E.2020302@xor.at> (raw)

Hi,

I noticed that 2.6.10 (referring to the changelog, 2.6.11-rc3 as well) 
has no builtin support for Promise SATAII 150 TX4 yet; a separate patch 
(http://marc.theaimsgroup.com/?l=linux-ide&m=110426005503319&q=raw) is 
needed to recognize this hardware.

Since the patch seems to work fine and is available for quite some time 
already, I'm interested if there are plans if and when it will be 
included in mainline 2.6?

[Please CC me on replies]


Best regards,
Johannes Resch


             reply	other threads:[~2005-02-06 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 13:39 Johannes Resch [this message]
2005-02-07 21:03 ` Inclusion of patch for Promise SATAII 150 TX4 in mainline 2.6 kernel? Mark Hahn
2005-02-07 21:39   ` Jeff Garzik
2005-02-08  4:19     ` Brad Campbell

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=42061E0E.2020302@xor.at \
    --to=jr@xor.at \
    --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).