From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Jesper Juhl <juhl-lkml@dif.dk>,
linux-kernel@vger.kernel.org,
Ryan Underwood <nemesis-lists@icequake.net>,
twaugh@redhat.com
Subject: Re: Request: Netmos support in parport_serial for 2.4.27
Date: Mon, 14 Jun 2004 06:10:59 +0200 [thread overview]
Message-ID: <20040614041059.GA11739@alpha.home.local> (raw)
In-Reply-To: <20040613220727.GB4771@logos.cnet>
Hi Marcelo,
On Sun, Jun 13, 2004 at 07:07:27PM -0300, Marcelo Tosatti wrote:
> And two, do we really need to move parport_serial.c to drivers/char in v2.4 ?
I believe that moving a file in the stable kernel is a bad thing when it
implies moving the module, especially for people in the embedded world,
because we can imagine some of them may have a particular update mechanism
or a pre-configured modules.dep or anything like that which will need to be
changed again for this update, while it seems there is no particular reason.
But if 2.6 has it in the same directory, this could be the occasion to move
it definitely.
Just my opinion anyway ;-)
Cheers,
Willy
next prev parent reply other threads:[~2004-06-14 4:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 11:19 Ryan Underwood
2004-06-13 12:39 ` Marcelo Tosatti
2004-06-13 20:30 ` Jesper Juhl
2004-06-13 21:04 ` Marcelo Tosatti
2004-06-13 22:07 ` Marcelo Tosatti
2004-06-14 4:10 ` Willy Tarreau [this message]
2004-06-14 4:51 ` Ryan Underwood
2004-06-14 14:59 ` Jesper Juhl
2004-06-21 1:49 ` Netmos 9835 in 2.6.x was " Marcelo Tosatti
2004-06-21 2:08 ` Andrew Morton
2004-06-14 8:20 ` Jesper Juhl
2004-06-13 13:05 ` Pavel Janík
2004-06-13 14:25 ` Willy Tarreau
2004-06-13 19:15 ` Jesper Juhl
2004-06-13 19:24 ` Jesper Juhl
[not found] <20040613171701.1750.70973.Mailman@linux.us.dell.com>
2004-06-14 4:44 ` Ryan Underwood
2004-06-15 14:06 ` Marcelo Tosatti
2004-06-16 11:50 ` Ryan Underwood
[not found] ` <20040616172421.GD8703@logos.cnet>
2004-06-17 2:33 ` Ryan Underwood
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=20040614041059.GA11739@alpha.home.local \
--to=willy@w.ods.org \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nemesis-lists@icequake.net \
--cc=twaugh@redhat.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®