From: Tejun Heo <htejun@gmail.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
James Steward <james.steward@dynamicratings.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ide: add dcache flushing after PIO
Date: Mon, 09 Jan 2006 18:16:25 +0900 [thread overview]
Message-ID: <43C229E9.6080705@gmail.com> (raw)
In-Reply-To: <20060109090842.GB9189@flint.arm.linux.org.uk>
Russell King wrote:
> On Sat, Jan 07, 2006 at 11:41:53PM +0100, Bartlomiej Zolnierkiewicz wrote:
>
>>Tejun posted RFC to lkml which got zero replies so I thought
>>that I will apply his patch if it *works*.
>
>
> Which appears to have been missed.
>
>
>>>>So far there was none and nobody seemed to care to test/comment
>>>>this patch ("works fine" is enough).
>>>
>>>Odd, as demonstrated by the linux-ide archives above I've already
>>>commented on it.
>>
>>OK, we have discussed the way to fix the problem.
>>
>>Still nothing was said whether this patch *actually* works or not.
>
>
> That's because I've already suggested that the patch is over-complex
> and I'm waiting for an updated patch. I'm not going to ask folk to
> test one patch which I know is doing far too much, only to have to
> ask them to test another patch later on.
>
> IOW, I'm not going to waste folk's time with a patch I know isn't
> suitable.
>
>
>>Test original Tejun's patch then.
>
>
> I can't - I'm not able to reproduce the problem due to the systems
> I have available to me.
>
> The way forward is an updated patch - Tejun's original patch updated
> with my comments. Once that's available, folk can test a patch which
> stands a chance of making it into mainline.
>
>
> Let me make my position clear: I don't care about this problem myself
> because I don't see it. That's why it's hung around since 2.4 times.
> My only involvement here is due to (a) other folk caring about it and
> (b) the lack of knowledge to get it fixed.
>
Hi, Russel & Bartlomiej.
As the message to the lkml didn't get any replies, I kind of forgot
about it. And after Russel's explanation, I don't think my first
approach is good. I will make another patch according to what I've
proposed in the message to lkml. I'm currently burried under libata EH
related stuff, but I think (or hope) it will be sorted out in a few days.
So, see you guys in a few days. Thanks.
--
tejun
next prev parent reply other threads:[~2006-01-09 9:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 0:47 Execute from CF causes segmentation faults James Steward
2005-12-20 12:52 ` Tejun Heo
2005-12-20 16:23 ` Bartlomiej Zolnierkiewicz
2005-12-21 9:48 ` Tejun Heo
2005-12-21 14:00 ` [PATCH] ide: add dcache flushing after PIO Tejun Heo
2005-12-21 14:03 ` Russell King
2005-12-21 14:43 ` Tejun Heo
2005-12-21 15:57 ` Bartlomiej Zolnierkiewicz
2005-12-21 16:00 ` Tejun Heo
2005-12-21 17:54 ` Russell King
2006-01-07 17:06 ` Russell King
2006-01-07 20:17 ` Bartlomiej Zolnierkiewicz
2006-01-07 21:22 ` Russell King
2006-01-07 22:41 ` Bartlomiej Zolnierkiewicz
2006-01-08 0:50 ` james
2006-01-09 9:08 ` Russell King
2006-01-09 9:16 ` Tejun Heo [this message]
2005-12-21 15:01 ` Execute from CF causes segmentation faults Russell 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=43C229E9.6080705@gmail.com \
--to=htejun@gmail.com \
--cc=bzolnier@gmail.com \
--cc=james.steward@dynamicratings.com \
--cc=linux-ide@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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).