All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dedekind@infradead.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] ubi: kill homegrown endian macros
Date: Thu, 17 May 2007 21:42:34 +0100	[thread overview]
Message-ID: <20070517204234.GR4095@ftp.linux.org.uk> (raw)
In-Reply-To: <20070517102931.6bbbad1a.akpm@linux-foundation.org>

On Thu, May 17, 2007 at 10:29:31AM -0700, Andrew Morton wrote:
> On Thu, 17 May 2007 18:09:50 +0300 Artem Bityutskiy <dedekind@infradead.org> wrote:
> 
> > On Thu, 2007-05-17 at 16:56 +0200, Christoph Hellwig wrote:
> > > On Thu, May 17, 2007 at 05:50:43PM +0300, Artem Bityutskiy wrote:
> > > > Christoph,
> > > > 
> > > > On Thu, 2007-05-17 at 16:32 +0200, Christoph Hellwig wrote:
> > > > > Kill ubis homegrown endianess handling crap and replace it with
> > > > > the normal kernel endianess handling.
> > > > 
> > > > Err,__be32 and the company are just sparse things, while I have compiler
> > > > checks with my struct ubi32_t and friends. JFFS2 also uses the same
> > > > technique. Why do you force me to rely on sparse instead instead of
> > > > compiler?
> > > 
> > > Yes.  Like all other code in the kernel aswell.
> > 
> > Andrew, may I please have your ack that I absolutely have to use __be32
> > instead of my own types since Christoph tends to provide no explanation
> > to his requests.
> 
> umm..  I'd say what you've done in there is an improvement to the exiting
> stuff: getting gcc to check it is better than having to use sparse.

Ahem...  So what does
	x |= y;
turns into with that approach?

  parent reply	other threads:[~2007-05-17 20:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 14:32 [PATCH] ubi: kill homegrown endian macros Christoph Hellwig
2007-05-17 14:50 ` Artem Bityutskiy
2007-05-17 14:56   ` Christoph Hellwig
2007-05-17 15:09     ` Artem Bityutskiy
2007-05-17 17:29       ` Andrew Morton
2007-05-17 17:46         ` Artem Bityutskiy
2007-05-17 18:18           ` Andrew Morton
2007-05-17 20:32             ` Artem Bityutskiy
2007-05-17 20:30         ` Matthieu CASTET
2007-05-18  2:39           ` David Woodhouse
2007-05-18  2:57             ` John Anthony Kazos Jr.
2007-05-18  3:17               ` David Woodhouse
2007-05-18 11:52                 ` John Anthony Kazos Jr.
2007-05-18 14:52                   ` David Woodhouse
2007-05-18 22:00                     ` Segher Boessenkool
2007-05-19  2:07                       ` David Woodhouse
2007-05-19 12:24                         ` Segher Boessenkool
2007-05-20 11:29                           ` David Woodhouse
2007-05-18 19:55             ` matthieu castet
2007-05-19  1:29               ` David Woodhouse
2007-05-18 20:30             ` matthieu castet
2007-05-17 20:42         ` Al Viro [this message]
2007-05-17 20:53           ` Al Viro
2007-05-18  6:58             ` Artem Bityutskiy
2007-05-18  8:38               ` Al Viro
2007-05-17 21:14           ` Dmitry Torokhov
2007-05-17 21:29             ` Al Viro
2007-05-17 21:33             ` David Miller
2007-05-17 21:47               ` Al Viro
2007-05-17 21:26           ` Al Viro
2007-05-17 20:56   ` David Miller
2007-05-17 21:03     ` Al Viro
2007-05-17 15:50 ` David Woodhouse
2007-05-17 18:12   ` Christoph Hellwig
2007-05-17 18:23     ` Sam Ravnborg
2007-05-17 18:36       ` Christoph Hellwig
2007-05-17 20:18         ` Jeremy Fitzhardinge
2007-05-17 20:27 ` Matthieu CASTET

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=20070517204234.GR4095@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=dedekind@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.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.