All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: J?rn Engel <joern@wohnheim.fh-wedel.de>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org, holzheu@de.ibm.com
Subject: Re: [S390] hypfs sparse warnings.
Date: Thu, 28 Sep 2006 16:21:39 +0200	[thread overview]
Message-ID: <20060928142139.GC6899@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20060928135406.GB18933@wohnheim.fh-wedel.de>

On Thu, Sep 28, 2006 at 03:54:06PM +0200, J?rn Engel wrote:
> On Thu, 28 September 2006 15:42:47 +0200, Heiko Carstens wrote:
> > On Thu, Sep 28, 2006 at 03:25:40PM +0200, J?rn Engel wrote:
> > > On Thu, 28 September 2006 15:07:37 +0200, Martin Schwidefsky wrote:
> > > > 
> > > > sparse complains, if we use bitwise operations on enums. Cast enum to
> > > > long in order to fix that problem!
> > > 
> > > At this point I start to wonder which part should be changed.  Is it
> > > better to
> > > a) cast some more, as you started to do,
> > > b) change enums to #defines or
> > > c) change '|' to '+'?
> > > 
> > > At any rate, you have the same problem in 5 seperate places by my
> > > count and only changed 1 of them.  Nak - in case anyone cares.
> > 
> > That would be where? My sparse run didn't reveal anything else.
> 
> Search for diag204.  All calls have the same format with bitwise or of
> two enums, so they are all equally (in-)correct.

You probably need to update your git tree. All of them have casts in the
meantime. Except for the one addressed with this patch.
See: 331c982d4a6b43cdc0d056956a1cae8a7d6237bf

  reply	other threads:[~2006-09-28 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 13:07 [S390] hypfs sparse warnings Martin Schwidefsky
2006-09-28 13:25 ` Jörn Engel
2006-09-28 13:31   ` Al Viro
2006-09-28 13:42   ` Heiko Carstens
2006-09-28 13:54     ` Jörn Engel
2006-09-28 14:21       ` Heiko Carstens [this message]
2006-09-28 14:41         ` Jörn Engel
2006-09-28 13:54   ` Michael Holzheu

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=20060928142139.GC6899@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=holzheu@de.ibm.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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.