From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Alexey Dobriyan <adobriyan@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] procfs: Fix sparse warnings
Date: Tue, 15 Feb 2005 19:26:18 +0000 [thread overview]
Message-ID: <20050215192618.GL8859@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200502151512.37774.adobriyan@mail.ru>
On Tue, Feb 15, 2005 at 03:12:37PM +0200, Alexey Dobriyan wrote:
> On Tuesday 15 February 2005 13:59, Al Viro wrote:
> > On Tue, Feb 15, 2005 at 02:55:55PM +0200, Alexey Dobriyan wrote:
> >
> > Let's hold this kind of stuff until 2.6.11, OK?
> >
> > Al, sitting on more than a megabyte of such patches...
>
> Could you send diffstat or something? I did "make allyesconfig" with
> -Wbitwise and digging slowly from the beginning. Now at fs/qnx4.
Umm... Let's do it that way: I'll get carving the sucker up to relatively
sane point and post it again (-bird, that is). Give me until tomorrow
morning and then feel free to send stuff my way - I'll merge it and feed
upstream when 2.6.11 opens (credited, obviously).
Keep in mind that for endianness patches you *really* need to check on
at least some big-endian targets and both on 32 and 64bit ones. I've
got a decent cross-build environment (tracking 14 targets now); if you need
help with setting up something similar, I can help.
next prev parent reply other threads:[~2005-02-15 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 12:55 Alexey Dobriyan
2005-02-15 11:59 ` Al Viro
2005-02-15 13:12 ` Alexey Dobriyan
2005-02-15 19:26 ` Al Viro [this message]
2005-02-16 8:35 ` Al Viro
2005-02-16 10:28 ` "__be32 s_addr" ? (was Re: [PATCH] procfs: Fix sparse warnings) Alexey Dobriyan
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=20050215192618.GL8859@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=adobriyan@mail.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®