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: Wed, 16 Feb 2005 08:35:50 +0000 [thread overview]
Message-ID: <20050216083550.GO8859@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050215192618.GL8859@parcelfarce.linux.theplanet.co.uk>
On Tue, Feb 15, 2005 at 07:26:18PM +0000, Al Viro wrote:
> 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).
Gaack... My apologies - I've seriously underestimated the amount of RL
crap, so no, it won't be ready today. I'll try to do that ASAP, but I can't
make a good estimate of how much I'll be able to do during the next week.
Crap...
OK, let's do it that way - send the stuff my way, I'll port it if needed
and if there are duplicates, your patches win. FWIW, stuff in fs/* is
* a bunch of patches in fs/reiserfs/* (carved up, see R[0-4]-* on
ftp.linux.org.uk/pub/people/viro)
* nfs, nfsd, lockd and net/sunrpc along with them (not carved up
into sane form and that will be needed to even start talking about merge)
* compat_ioctl.c (part of i2c annotations)
* fs/hostfs/* (part of UML patches, so that'll a part of further split
once the things stabilize a bit)
* couple of trivial ones - procfs (duplicate of your patch) and
ncpfs (ncp_request_reply.sign made be32[6])
* include-ectomy in a lot of places, but that's not likely to clash
with your stuff.
Most of the mess is in drivers/*, arch/* and (for endianness patches) net/*...
next prev parent reply other threads:[~2005-02-16 8:35 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
2005-02-16 8:35 ` Al Viro [this message]
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=20050216083550.GO8859@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®