From: Andrew Morton <akpm@osdl.org>
To: Latchesar Ionkov <lucho@advancedsolutions.com>
Cc: davej@redhat.com, linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH] v9fs: fix for access to unitialized variables or freed memory
Date: Tue, 7 Mar 2006 15:04:22 -0800 [thread overview]
Message-ID: <20060307150422.084f3863.akpm@osdl.org> (raw)
In-Reply-To: <20060307124304.GA15195@ionkov.net>
Latchesar Ionkov <lucho@advancedsolutions.com> wrote:
>
> Miscellaneous fixes related to accessing uninitialized variables or memory
> that was already freed.
That part of your patch is applicable to (and needed in) 2.6.16. (Please
confirm).
> Adds function declarations missed in
> v9fs-print-9p-messages.patch.
And that part is only applicable to a patch which is queued for 2.6.17.
Hence I split your patch into two patches. The latter one will be folded
into v9fs-print-9p-messages-fix before I send it off to Linus.
The general rule is "one concept per patch", please. This patch had two.
prev parent reply other threads:[~2006-03-07 23:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 7:04 9pfs double kfree Dave Jones
2006-03-06 7:07 ` David S. Miller
2006-03-06 7:23 ` Al Viro
2006-03-06 7:28 ` Dave Jones
2006-03-06 7:56 ` Pekka Enberg
2006-03-06 8:00 ` Dave Jones
2006-03-06 8:16 ` Al Viro
2006-03-06 8:23 ` Pekka Enberg
2006-03-06 8:27 ` Arjan van de Ven
2006-03-06 8:40 ` Kai Makisara
2006-03-06 9:34 ` Al Viro
2006-03-06 22:07 ` Pavel Machek
2006-03-09 14:48 ` Luke-Jr
2006-03-06 7:26 ` Balbir Singh
2006-03-06 7:31 ` Dave Jones
2006-03-06 7:39 ` Balbir Singh
2006-03-07 0:37 ` Andrew Morton
2006-03-07 1:04 ` Eric Van Hensbergen
2006-03-07 2:20 ` Latchesar Ionkov
2006-03-07 1:49 ` Latchesar Ionkov
2006-03-07 12:43 ` [PATCH] v9fs: fix for access to unitialized variables or freed memory Latchesar Ionkov
2006-03-07 23:04 ` Andrew Morton [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=20060307150422.084f3863.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@advancedsolutions.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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
Powered by JetHome