Mark Post wrote:

I guess that, after all, I'll have to figure out git !


You could just send the diff to the Linux Kernel Mailing List (LKML).


Learning git wasn't that hard ;).. I wanted to have a properly formatted
and possibly retrievable patch ready.. (ok.. The patch was a 1 liner..
but still) .. now..

Actually, I found out (still learning) that posting to LKML by itself is
usually not enough (although sending a copy to LKML for the record seems
to be the Right Thing(tm) to do).. It would have been better and faster
if I had also sent it to the maintainer (Martin Schwidefsky) and the
linux-s390 ML too.. Lesson : RTFM Ivan ! (for that matter
Documentation/SubmittingPatches.txt).. Hopefully, Frans Pop picked it
up, forwarded to the right people, the patch was reviewed, Stefan
Weinhuber found an even better solution and..

Voila !

A fix is in Linus' 2.6.27-rc4-git4[1] (so it should make into 2.6.27,
and possibly 2.6.26 and 2.6.25 (when the problem was introduced [1])
since it was CC'd to stable too)..

Thanks,

--Ivan

[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=49fd38bdaa96f093fcad3176a781a4d0de8f8602

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to