From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: David Howells <dhowells@redhat.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
"torvalds@osdl.org" <torvalds@osdl.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-afs@lists.infradead.org" <linux-afs@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] AFS: Fix compilation warning
Date: Tue, 14 Jul 2009 19:36:36 +0300 [thread overview]
Message-ID: <4A5CB414.5000001@nokia.com> (raw)
In-Reply-To: <5554.1247588246@redhat.com>
Hi,
David Howells wrote:
> Can you try Jaswinder's patch? I don't see the warning even without your
> patch, so I can't test it.
Linus has already applied my patch which you sent him:
commit dd0d9a46f573b086a67522f819566427dba9c4c7
Author: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Date: Thu Jul 9 10:44:30 2009 +0100
AFS: Fix compilation warning
But this patch applies to both current linux-2.6.git and to
pre-"AFS: Fix compilation warning" tree.
I've compile-tested the latter and yes, this patch fixes
the warning.
FWIW, if you want to apply this patch, then you probably
should first revert my patch, or make this patch undo my
"unitinialized_var" changes. And probably this stuff is
anyway not 2.6.31 material, because the warning is fixed
anyway :-) Anyway, not my area :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-07-14 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 9:44 [PATCH] AFS: Fix compilation warning David Howells
2009-07-14 8:47 ` Jaswinder Singh Rajput
2009-07-14 8:58 ` Jaswinder Singh Rajput
2009-07-14 13:10 ` David Howells
2009-07-14 13:49 ` Jaswinder Singh Rajput
2009-07-14 14:16 ` David Howells
2009-07-14 16:17 ` David Howells
2009-07-14 16:36 ` Artem Bityutskiy [this message]
2009-07-14 17:22 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 8:04 [PATCH] AFS: fix " Artem Bityutskiy
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=4A5CB414.5000001@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jaswinder@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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