From: Tejun Heo <htejun@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Tom Mortensen <tmmlkml@gmail.com>,
linux-kernel@vger.kernel.org, jeff@garzik.org
Subject: Re: 2.4.x libata resync
Date: Sat, 16 Sep 2006 15:27:12 +0900 [thread overview]
Message-ID: <450B9940.5030609@gmail.com> (raw)
In-Reply-To: <20060916053713.GJ541@1wt.eu>
Hello,
Willy Tarreau wrote:
> On Fri, Sep 15, 2006 at 10:14:07PM -0700, Tom Mortensen wrote:
>> To Jeff Garzik & others,
>> I was wondering if there are any plans for another resync of the latest
>> 2.6.x libata changes back into the 2.4.x kernel?
>
> When Jeff posted his last version (which got merged), he said that it
> would be his last work on this backport. I've been regularly checking
> what has changed in 2.6, because often some bugs are fixed, but I see
> that the code has considerably evolved since the last resync, and I'm
> not even sure that those bugfixes are needed for 2.4.
>
> A full resync of latest 2.6 would require a considerable effort it seems.
> Do you encounter any problems right now ? I get very few feedback from
> SATA users in general.
I don't think it's gonna happen. Later libata changes depend on a
number of SCSI updates, which in turn are deeply dependent upon new
driver model used in 2.6. So, apart from bug fixes, there won't be 2.4
resync.
--
tejun
next prev parent reply other threads:[~2006-09-16 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 5:14 2.4.x libata resync Tom Mortensen
2006-09-16 5:37 ` Willy Tarreau
2006-09-16 6:27 ` Tejun Heo [this message]
2006-09-16 6:38 ` Willy Tarreau
2006-09-16 15:49 ` Jeff Garzik
2006-09-16 15:51 ` Willy Tarreau
2006-09-16 16:07 ` Jeff Garzik
2006-09-16 16:05 ` Willy Tarreau
2006-09-16 16:27 ` Jeff Garzik
2006-09-16 16:22 ` Willy Tarreau
2006-09-16 6:47 ` Tom Mortensen
2006-09-16 6:18 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 14:52 Mikael Pettersson
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=450B9940.5030609@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmmlkml@gmail.com \
--cc=w@1wt.eu \
/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