From: Matthew Wilcox <matthew@wil.cx>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-scsi@vger.kernel.org,
Andi Kleen <ak@suse.de>,
Ingo Juergensmann <ij@2005.bluespice.org>,
Richard Hirst <rhirst@levanta.com>
Subject: Re: Removing BROKEN scsi drivers
Date: Tue, 22 Nov 2005 15:20:33 -0700 [thread overview]
Message-ID: <20051122222033.GQ1598@parisc-linux.org> (raw)
In-Reply-To: <1132695837.8928.11.camel@localhost.localdomain>
On Tue, Nov 22, 2005 at 10:43:56PM +0100, Kars de Jong wrote:
> I don't really understand the current mechanism. It seems to result in
> different behaviour for BE systems depending on the definition of
> CONFIG_53C700_LE_ON_BE.
I think you misunderstand the meaning of that symbol. It means "Support
little endian chips on a big endian processor". Without it set, the
driver supports only little endian chips on little endian processors and
big endian chips on big endian processors.
> Was this driver ever used on BE systems without CONFIG_53C700_LE_ON_BE
> being defined?
I doubt it.
next prev parent reply other threads:[~2005-11-22 22:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:14 Removing BROKEN scsi drivers Andi Kleen
2005-10-05 11:22 ` Arjan van de Ven
2005-10-05 11:31 ` Matthew Wilcox
2005-10-05 11:39 ` Christoph Hellwig
2005-10-05 12:32 ` Richard Hirst
2005-10-05 13:30 ` Kars de Jong
2005-10-05 14:00 ` Richard Hirst
2005-10-05 14:03 ` James Bottomley
2005-10-05 14:35 ` Rolf Eike Beer
2005-10-07 8:27 ` Geert Uytterhoeven
2005-10-07 13:42 ` Richard Hirst
2005-10-07 13:53 ` Kars de Jong
2005-11-15 9:51 ` Christoph Hellwig
2005-11-15 10:17 ` Ingo Juergensmann
2005-11-15 10:30 ` Christoph Hellwig
2005-11-15 11:32 ` Richard Hirst
2005-11-15 12:08 ` Roman Zippel
2005-11-15 12:11 ` Kars de Jong
2005-11-15 13:05 ` Matthew Wilcox
2005-11-22 8:36 ` Christoph Hellwig
2005-11-22 21:43 ` Kars de Jong
2005-11-22 22:20 ` Matthew Wilcox [this message]
2005-11-27 16:47 ` James Bottomley
2005-11-29 22:24 ` James Bottomley
2005-11-30 8:31 ` Kars de Jong
2005-11-30 8:45 ` Ingo Juergensmann
2005-12-01 20:43 ` Kars de Jong
2005-12-01 20:47 ` James Bottomley
2005-12-01 23:29 ` Richard Hirst
2005-12-02 15:03 ` Ingo Juergensmann
2005-12-07 21:25 ` Ingo Juergensmann
2006-07-07 12:44 ` Christoph Hellwig
2006-07-09 11:16 ` Richard Hirst
2006-07-09 11:25 ` Kars de Jong
2006-10-30 11:13 ` Christoph Hellwig
2006-10-30 12:34 ` Kars de Jong
2006-10-31 21:47 ` [RFC PATCH] m68k: switch to 53c700 driver Kars de Jong
2006-11-02 21:34 ` Geert Uytterhoeven
2006-12-17 22:28 ` James Bottomley
2006-12-18 9:34 ` Geert Uytterhoeven
2006-12-19 3:09 ` Al Viro
2006-12-22 21:21 ` Kars de Jong
2007-04-29 21:43 ` Christoph Hellwig
2005-10-05 11:43 ` Removing BROKEN scsi drivers Christoph Hellwig
2005-10-05 22:36 ` Douglas Gilbert
2005-10-06 10:23 ` Andi Kleen
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=20051122222033.GQ1598@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=ak@suse.de \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=ij@2005.bluespice.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rhirst@levanta.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;
as well as URLs for NNTP newsgroup(s).