[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.999.0710301206390.30120@woody.linux-foundation.org>
Date: Tue, 30 Oct 2007 12:11:02 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Zach Brown <zach.brown@...cle.com>
cc: Karl Schendel <kschendel@...allegro.com>,
Benjamin LaHaise <bcrl@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nick Piggin <nickpiggin@...oo.com.au>,
Chris Mason <chris.mason@...cle.com>
Subject: Re: [PATCH] Fix bad data from non-direct-io read after direct-io
write
On Tue, 30 Oct 2007, Zach Brown wrote:
>
> OK, I tested and verified Karl's fix and wrote some commentary around it.
Thanks, will apply.
> (Would a aio-dio git repo on kernel.org for these kind of fixes be well
> received?)
If it's one of these "in a blue moon" things I don't think it matters.
Whatever is easier.
In general, patches have lots of advantages: (a) you can apply it
regardless of version, and (b) pushing the email containing them back and
forth with commentary etc is very powerful.
So I would generally see git as a "maintainer handling issue", not a
"these kinds of fixes" issue. Git doesn't obviate the need for having
people look at patches (and that implies sending them out). But git _is_ a
good way to push the finished product out, if it's a recurring thing.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists