From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: niteowl@intrinsity.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.59 kernel bugs
Date: Thu, 06 Feb 2003 14:33:11 -0800 [thread overview]
Message-ID: <276580000.1044570790@[10.10.2.4]> (raw)
In-Reply-To: <1044573413.12098.19.camel@irongate.swansea.linux.org.uk>
>> Some fairly sickening stuff ... I'll log the following sections in bugzilla
>> If any brave volunteers for the others want to go ahead with the other
>> sections, and split the effort, would be much appreciated. Please mail
>> back to lkml that you're doing it ... and watch very carefully on newly
>> logged bugs for collisions ;-)
>
> 2.4-ac fixes applied for : (No name in the entry as I've not figured
> out who to credit yet)
>
> o Fix i2c_ack cris extra ";"
> o Fix JSIOCSBTNMAP extra ";"
> o Fix VIDIOCGTUNER on w9966
> o Fix amd8111e_read_regs
> o Fix smctr_load_node_addr
> o Fix sym53c8xxx extra ";"
> o Fix sym53c8xxx_2 extra ";"
> o Fix cs46xx download area clear
> o Fix hysdn bootup error handling
> o Fix mtd mount error checks
> o Fix dpt_i2o reset error paths
> o Fix a jffs error path handler
> o Fix es1371 error path on register
> o Fix sscape operator precedence
> o Fix copy counting in vrc5477 audio
>
> Once the next -ac appears those should all drop into 2.5 if someone
> wants to do the legwork
I'm happy to do whatever legwork is needed ... if you already have a
seperate patch you could send my way for this stuff, would make it
easier, if not, I'll go digging through your next release ...
Thanks,
M.
next prev parent reply other threads:[~2003-02-06 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 20:43 niteowl
2003-02-06 21:08 ` Martin J. Bligh
2003-02-06 23:16 ` Alan Cox
2003-02-06 22:33 ` Martin J. Bligh [this message]
2003-02-06 21:16 ` Andrew Morton
2003-02-06 22:49 ` Dave Jones
2003-02-06 23:06 ` Randy.Dunlap
2003-02-28 9:14 ` Paul Laufer
2003-02-07 0:14 ` Russell King
2003-02-07 9:23 ` Oleg Drokin
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='276580000.1044570790@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=niteowl@intrinsity.com \
/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
all inboxes | Powered by JetHome®