From: Jonathan Cameron <jic23@cam.ac.uk>
To: David Vrabel <david.vrabel@csr.com>
Cc: akpm@linux-foundation.org, roel.kluin@gmail.com,
linux-mmc@vger.kernel.org,
"libertas-dev@lists.infradead.org"
<libertas-dev@lists.infradead.org>
Subject: Re: [patch 077/232] sdio: fix read buffer overflow
Date: Thu, 01 Oct 2009 15:11:37 +0100 [thread overview]
Message-ID: <4AC4B899.9000701@cam.ac.uk> (raw)
In-Reply-To: <4AC48FA1.409@csr.com>
David Vrabel wrote:
> David Vrabel wrote:
>> It's harmless if the tuple contains fewer so I think we should just try
>> and parse as many strings as possible. Does this patch fix your regression?
>
> I spelt the field name wrong in the comment. Use this patch instead,
> please.
Works for me, so Tested-by: Jonathan Cameron <jic23@cam.ac.uk>
I guess it's just a question of posting it as a normal patch and seeing if
anyone screams.
Thanks,
Jonathan
next prev parent reply other threads:[~2009-10-01 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 23:45 [patch 077/232] sdio: fix read buffer overflow akpm
2009-10-01 10:08 ` Jonathan Cameron
2009-10-01 11:12 ` David Vrabel
2009-10-01 11:16 ` David Vrabel
2009-10-01 14:11 ` Jonathan Cameron [this message]
2009-10-06 21:49 ` Bing Zhao
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=4AC4B899.9000701@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@csr.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=roel.kluin@gmail.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