From: Sean MacLennan <smaclennan@pikatech.com>
To: <benh@kernel.crashing.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Karsten Keil" <kkeil@suse.de>,
"Andreas.Eversberg" <Andreas.Eversberg@versatel.de>,
<isdn4linux@listserv.isdn4linux.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] Fix remaining big endian issue of hfcmulti
Date: Tue, 5 Aug 2008 19:38:08 -0400 [thread overview]
Message-ID: <20080805193808.40650f30@lappy.seanm.ca> (raw)
In-Reply-To: <1217977459.24157.210.camel@pasglop>
On Wed, 06 Aug 2008 09:04:18 +1000
"Benjamin Herrenschmidt" <benh@kernel.crashing.org> wrote:
> If the size of the binary (or performances) involved in doing the two
> type of IOs in a single driver is such that having the ability to
> only use one is worth it (for embedded for example), then you can
> provide a config option that allows to select which method to build
> in the driver, but it's a good idea to allow building both with
> runtime detection.
Fair enough. I can agree to that.
Cheers,
Sean
next prev parent reply other threads:[~2008-08-05 23:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 14:35 [PATCH 3/4] Fix remaining big endian issue of hfcmulti Karsten Keil
2008-08-04 12:03 ` David Woodhouse
2008-08-04 14:29 ` Karsten Keil
2008-08-05 4:29 ` Benjamin Herrenschmidt
2008-08-05 11:31 ` Karsten Keil
2008-08-05 13:04 ` Benjamin Herrenschmidt
2008-08-05 17:25 ` Karsten Keil
2008-08-05 18:42 ` Linus Torvalds
2008-08-05 21:02 ` Karsten Keil
2008-08-05 21:23 ` Sean MacLennan
2008-08-05 21:37 ` Linus Torvalds
2008-08-05 21:59 ` Sean MacLennan
2008-08-05 23:04 ` Benjamin Herrenschmidt
2008-08-05 23:38 ` Sean MacLennan [this message]
2008-08-06 0:18 ` Karsten Keil
2008-08-06 0:33 ` Benjamin Herrenschmidt
2008-08-05 21:46 ` Benjamin Herrenschmidt
2008-08-05 21:45 ` Benjamin Herrenschmidt
2008-08-05 21:43 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 11:01 AW: " Andreas.Eversberg
2008-08-07 13:46 ` Karsten Keil
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=20080805193808.40650f30@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=Andreas.Eversberg@versatel.de \
--cc=benh@kernel.crashing.org \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.