From: Jens Axboe <axboe@suse.de>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6] cciss typo fix
Date: Sat, 8 Jan 2005 09:41:17 +0100 [thread overview]
Message-ID: <20050108084113.GA21857@suse.de> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF107DC0185@cceexc23.americas.cpqcorp.net>
On Fri, Jan 07 2005, Miller, Mike (OS Dev) wrote:
> > -----Original Message-----
> > From: James Bottomley [mailto:James.Bottomley@SteelEye.com]
> >
> >
> > On Fri, 2005-01-07 at 17:01 -0600, mike.miller@hp.com wrote:
> > > - *total_size = be32_to_cpu(*((__be32 *)
> > &buf->total_size[0]))+1;
> > > - *block_size = be32_to_cpu(*((__be32 *)
> > &buf->block_size[0]));
> > > + *total_size = be32_to_cpu(*((__u32 *)
> > &buf->total_size[0]))+1;
> > > + *block_size = be32_to_cpu(*((__u32 *)
> > &buf->block_size[0]));
> >
> > I don't think that's a typo. It was introduced by this patch:
> >
> > ChangeSet 1.1988.24.79 2004/10/06 07:55:02 viro@www.linux.org.uk
> > [PATCH] cciss endianness and iomem annotations
> >
> > The idea being that BE and LE numbers should be annotated differently,
> > so the __be32 annotations look correct to me. I think sparse
> > will warn
> > if you make this change.
>
> Hmmm, SuSE complained that __be32 was not defined in the kernel. Any
> other thoughts, anyone?
Hmm odd, no one should have complained, it should just have been added
to the compat header.
--
Jens Axboe
next prev parent reply other threads:[~2005-01-08 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 23:24 [PATCH 2.6] cciss typo fix Miller, Mike (OS Dev)
2005-01-07 23:32 ` James Bottomley
2005-01-08 8:41 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-10 15:45 Miller, Mike (OS Dev)
2005-01-10 15:50 ` James Bottomley
2005-01-07 23:34 Miller, Mike (OS Dev)
2005-01-07 23:01 mike.miller
2005-01-07 23:19 ` James Bottomley
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=20050108084113.GA21857@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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 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.