From: Joe Perches <joe@perches.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, jfs-discussion@lists.sourceforge.net
Subject: Re: [Jfs-discussion] [PATCH 5/6] fs/jfs: Add printf format/argument verification
Date: Fri, 12 Nov 2010 00:53:47 -0800 [thread overview]
Message-ID: <1289552027.6519.60.camel@Joe-Laptop> (raw)
In-Reply-To: <1289489501.6848.13.camel@shaggy-w500>
On Thu, 2010-11-11 at 09:31 -0600, Dave Kleikamp wrote:
> On Wed, 2010-11-10 at 15:46 -0800, Joe Perches wrote:
> > Add __attribute__((format... to jfs_error.
> > All arguments matched formats, no other changes necessary.
> > Signed-off-by: Joe Perches <joe@perches.com>
> Acked-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> Would you like to push this patchset as a group, or would you like me to
> push this patch through the jfs tree?
I think each patch should go through the
appropriate fs maintainers separately.
cheers, Joe
next prev parent reply other threads:[~2010-11-12 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 23:46 [PATCH 0/6] fs: " Joe Perches
2010-11-10 23:46 ` [PATCH 1/6] fs/adfs: Add printf format/argument verification and fix fallout Joe Perches
2010-11-10 23:46 ` [PATCH 2/6] fs/affs: " Joe Perches
2010-11-11 9:20 ` Geert Uytterhoeven
2010-11-11 10:14 ` [PATCH] fs/affs/file.c: Use appropriate format types and casts Joe Perches
2010-11-10 23:46 ` [PATCH 3/6] fs/befs: Add printf format/argument verification and fix fallout Joe Perches
2010-11-10 23:46 ` [PATCH 4/6] fs/ecryptfs: " Joe Perches
2010-11-16 3:28 ` Tyler Hicks
2010-11-10 23:46 ` [PATCH 5/6] fs/jfs: Add printf format/argument verification Joe Perches
2010-11-11 15:31 ` [Jfs-discussion] " Dave Kleikamp
2010-11-12 8:53 ` Joe Perches [this message]
2010-11-10 23:46 ` [PATCH 6/6] fs/udf: " Joe Perches
2010-11-11 9:55 ` Jan Kara
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=1289552027.6519.60.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.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
Powered by JetHome