From: Jeff Garzik <jgarzik@pobox.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sata_via: PATA support, resubmit
Date: Mon, 08 Jan 2007 10:51:42 -0500 [thread overview]
Message-ID: <45A2688E.3080503@pobox.com> (raw)
In-Reply-To: <20070108154249.6d8f5697@localhost.localdomain>
Alan wrote:
>> The problem you need to fix or work around is ata_probe_ent, which
>> doesn't properly fill in ata_port info for this situation. Tejun has
>> posted patches that kill ata_probe_ent, which you were pointed to.
>
> And which are not yet in the main tree leaving many users unable to
> install Linux.
The controllers affected by your patch have been around for well over a
year. I doubt a huge amount of suffering will be caused by pausing to
get it right... especially when you have been pointed at two working
code examples that already get it right.
> This isn't the way to get stuff done. When you've got the
> new patches in the driver can use them if its worth it (which, see below,
> I question).
In Linux, we work /with/ the subsystem, not around it.
Your current approach is fundamentally flawed. You can see this because
e.g. a call to vt6421_ops::scr_read() will immediately oops, after your
patch.
Just separate PATA and SATA operations. That way everything works as
expected, and you don't unintentionally add lovely oopses all over the
place.
Jeff
next prev parent reply other threads:[~2007-01-08 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 12:26 [PATCH] sata_via: PATA support, resubmit Alan
2007-01-08 13:04 ` Jeff Garzik
2007-01-08 15:42 ` Alan
2007-01-08 15:51 ` Jeff Garzik [this message]
2007-01-08 16:40 ` Alan
2007-01-08 16:34 ` Jeff Garzik
2007-01-08 17:11 ` Alan
2007-01-09 10:39 ` 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=45A2688E.3080503@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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