From: Michael Holzheu <HOLZHEU@de.ibm.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-kernel@vger.kernel.org, mschwid2@de.ibm.com
Subject: Re: [S390] hypfs sparse warnings.
Date: Thu, 28 Sep 2006 15:54:54 +0200 [thread overview]
Message-ID: <OF23094A82.EDC81A74-ON422571F7.004C2D9B-422571F7.004C7025@de.ibm.com> (raw)
In-Reply-To: <20060928132540.GA18933@wohnheim.fh-wedel.de>
Hi Jörn,
Jörn Engel <joern@wohnheim.fh-wedel.de> wrote on 09/28/2006 03:25:40 PM:
> 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,
I have done that! Martin already has submitted this patch.
Michael
prev parent reply other threads:[~2006-09-28 13:54 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
2006-09-28 14:41 ` Jörn Engel
2006-09-28 13:54 ` Michael Holzheu [this message]
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=OF23094A82.EDC81A74-ON422571F7.004C2D9B-422571F7.004C7025@de.ibm.com \
--to=holzheu@de.ibm.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@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 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).