From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: James McKenzie <james@fishsoup.dhs.org>,
linux-kernel@vger.kernel.org, trivial@rustcorp.com.au
Subject: Re: [2.5 patch] allow only one Toshiba Type-O IR Port driver in the kernel
Date: Tue, 29 Oct 2002 09:29:32 -0800 [thread overview]
Message-ID: <20021029172932.GE32449@bougret.hpl.hp.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0210291619310.14144-100000@mimas.fachschaften.tu-muenchen.de>
On Tue, Oct 29, 2002 at 04:26:50PM +0100, Adrian Bunk wrote:
> On Mon, 21 Oct 2002, Jean Tourrilhes wrote:
>
> > Adrian,
>
> Hi Jean,
>
> > Thanks very much for the report. I personally uses modules,
> > and I would prefer the ability to compile both modules, so that people
> > can try both without having to recompile their kernel.
>
> notice that my patch doesn't disallow to build both drivers as modules.
>
> > I think a much better patch (and simpler in the long term)
> > would be to just rename 'toshoboe_init' to 'donauboe_init' (plus the
> > few other offending function). This is a case where the name doesn't
> > really matter.
> > What do you think ?
>
> That's an alternate solution that should also fix the compile problem.
>
> But as stated above my patch doesn't affect the case when both drivers are
> modular which is usually the desired setup when you want to switch between
> the two drivers.
I personally prefer to make the driver code cleaner rather
than making the config/Makefile rules more complex. I believe that in
the long run, it always pay to keep things simple.
But, I'm not religious about it.
> cu
> Adrian
How do we proceed ? Do you want to send patches yourself
directly, or do you want to wait until I send my next IrDA update ?
Regards,
Jean
next prev parent reply other threads:[~2002-10-29 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 14:44 Adrian Bunk
2002-10-21 17:32 ` Jean Tourrilhes
2002-10-29 15:26 ` Adrian Bunk
2002-10-29 17:29 ` Jean Tourrilhes [this message]
2002-10-30 12:14 ` Adrian Bunk
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=20021029172932.GE32449@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=bunk@fs.tum.de \
--cc=james@fishsoup.dhs.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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®