From: Marek Michalkiewicz <marekm@amelek.gda.pl>
To: Ed Vance <EdV@macrolink.com>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
"'Russell King'" <rmk@arm.linux.org.uk>
Subject: Re: 2.4.x parport_serial link order bug (only works as a module)
Date: Tue, 2 Dec 2003 14:48:51 +0100 [thread overview]
Message-ID: <20031202134851.GA6658@amelek.gda.pl> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A34047@EXCHANGE>
Hi,
On Thu, Nov 20, 2003 at 10:09:39AM -0800, Ed Vance wrote:
>
> I think it should go into 2.4. It fixes this particular ordering issue
> without mucking about with the ordering mechanism or even adding code. I'm
> sorry to say that I had forgotten about it. It's a good minimum-change
> brute-force umm... solution. No bloat or complexity issues.
>
> At your convenience, please move the parport_serial.c file and apply the
> corresponding Makefile changes.
Now that 2.4.23 is out, could you try to help me getting this (and
possibly NetMos changes) into 2.4.24? I've just read that 2.4.24
is the last release for which new drivers are accepted, and it's
not even a new driver... Tim Waugh has been silent about NetMos
problems, and the current version of my patch (made for 2.4.21,
but should apply cleanly to 2.4.23) makes NetMos support a config
option, conditional on CONFIG_EXPERIMENTAL.
Thanks,
Marek
next prev parent reply other threads:[~2003-12-02 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 18:09 Ed Vance
2003-12-02 13:48 ` Marek Michalkiewicz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 15:23 Marek Michalkiewicz
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=20031202134851.GA6658@amelek.gda.pl \
--to=marekm@amelek.gda.pl \
--cc=EdV@macrolink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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
all inboxes | Powered by JetHome®