All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Mark Haverkamp <markh@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Mark Salyzyn <mark_salyzyn@adaptec.com>
Subject: Re: [PATCH] 2.6 aacraid: endian cleanup
Date: Mon, 28 Mar 2005 15:36:23 -0800	[thread overview]
Message-ID: <424894F7.5090103@osdl.org> (raw)
In-Reply-To: <1112052522.5560.34.camel@markh1.pdx.osdl.net>

Mark Haverkamp wrote:
> On Mon, 2005-03-28 at 22:59 +0100, Christoph Hellwig wrote:
> 
>>On Mon, Mar 21, 2005 at 10:41:23AM -0800, Mark Haverkamp wrote:
>>
>>>A patch from Adaptec with byte order changes:
>>> - drop byte swapping on all 0's and all 1's content
>>> - fix up missing swapping directives
>>> - ensure swapping on 16 bit values does not use 32 bit swap
>>> - reconcile the readl/writel auto-swapping in only most of the
>>>configurations.
>>
>>that last bit is bogus.  readl/writel are defined to swap bytes on
>>big endian systems.  Whatever broken Mvista/Windriver or whatever port
>>doesn't do that should be fixed.
>>
>>Also please remove unrelated changes like the new cardtypes from the patch,
>>follow normal kernel codingstyle (e.g. ||, && at the end of the line) and
>>switch to __le* types for harware structures and make sure it's passing
>>sparse -Wbitwise.
> 
> 
> Sorry if this is a dumb question, but I haven't used sparse before.  If
> I do a make C=1, will that run sparse with the appropriate options?

sparse doesn't do bitwise by default, so you need to do

make C=1 CHECK="sparse -Wbitwise" drivers/scsi/filename.o  (e.g.)

-- 
~Randy

  reply	other threads:[~2005-03-28 23:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 18:41 [PATCH] 2.6 aacraid: endian cleanup Mark Haverkamp
2005-03-28 21:58 ` James Bottomley
2005-03-28 22:04   ` Mark Haverkamp
2005-03-28 22:17     ` James Bottomley
2005-03-28 21:59 ` Christoph Hellwig
2005-03-28 22:05   ` Mark Haverkamp
2005-03-28 23:28   ` Mark Haverkamp
2005-03-28 23:36     ` Randy.Dunlap [this message]
2005-03-28 23:38     ` Mark Haverkamp
2005-03-29 16:49   ` Mark Haverkamp
2005-03-29 16:51     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2005-03-28 23:02 Salyzyn, Mark

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=424894F7.5090103@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@osdl.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.