From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Ravnborg <sam@ravnborg.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: modpost: Remove numeric suffix pattern matching
Date: Thu, 10 Jul 2014 10:44:11 +0930 [thread overview]
Message-ID: <8738ea582k.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140709204759.GA32335@ravnborg.org>
Sam Ravnborg <sam@ravnborg.org> writes:
> On Wed, Jul 09, 2014 at 11:41:48AM +0200, Rasmus Villemoes wrote:
>> For several years, the pattern "foo$" has effectively been treated as
>> equivalent to "foo" due to a bug in the (misnamed) helper
>> number_prefix(). This hasn't been observed to cause any problems, so
>> remove the broken $ functionality and change all foo$ patterns to foo.
>>
>> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
>> ---
>> Sam, was this what you meant? Otherwise, I'd be more than happy to
>> leave the issue to someone else.
> Exactly - thanks.
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
>
> Rusty - I assume you pick this up and channel it through the module tree.
>
> Sam
Done, thanks!
Applied,
Rusty.
prev parent reply other threads:[~2014-07-10 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 8:46 [PATCH] scripts/mod/modpost.c: Fix bug in number_prefix Rasmus Villemoes
2014-06-25 14:26 ` Paul Gortmaker
2014-06-25 22:57 ` Rasmus Villemoes
2014-07-08 23:58 ` Rusty Russell
2014-07-09 7:13 ` Sam Ravnborg
2014-07-09 9:41 ` [PATCH] scripts: modpost: Remove numeric suffix pattern matching Rasmus Villemoes
2014-07-09 20:47 ` Sam Ravnborg
2014-07-10 1:14 ` Rusty Russell [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=8738ea582k.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=paul.gortmaker@windriver.com \
--cc=sam@ravnborg.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