From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Jeff Layton <jlayton@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [PATCH] Handle SForced in storage_modifiers
Date: Thu, 5 Jan 2017 07:39:48 +0100 [thread overview]
Message-ID: <20170105063947.GA9300@macpro.local> (raw)
In-Reply-To: <CANeU7Qn_hebujogeF-HEaDsSWbEaPJTDpSUR5bXG1t1r7MihXA@mail.gmail.com>
On Thu, Nov 17, 2016 at 06:28:15AM +0800, Christopher Li wrote:
> On Tue, Nov 15, 2016 at 10:07 AM, Jeff Layton <jlayton@redhat.com> wrote:
> >
> > That looks fine to me. If you want to merge that one, then:
> >
> > Reviewed-by: Jeff Layton <jlayton@redhat.com>
>
> The patches is applied on "chrisl" repo and pushed out.
>
> Actually I want to merge the patch having you as the author.
>
> Chris
> --
I just noticed now, while doing some merging, that what have been commited
on the master tree is not the patch discussed here.
What have been commited is the same change but with 'CMax' (integer class)
while it was supposed to be 'SMax' (for the array of specifier).
The version on sparse-next is correct though.
Here is a patch fixing this:
From 04ffa624446bda7fbbc2c98fa012cb6e4bac1c53 Mon Sep 17 00:00:00 2001
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Date: Thu, 5 Jan 2017 07:31:46 +0100
Subject: [PATCH] fix mixup in "Handle SForced in storage_modifiers"
The patch used the wrong enum for the maximum size of the array.
Fixes: 1db3b627 ("Handle SForced in storage_modifiers")
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
parse.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/parse.c b/parse.c
index b52c6abe..385e40ce 100644
--- a/parse.c
+++ b/parse.c
@@ -105,11 +105,11 @@ enum {
};
enum {
- CInt = 0, CSInt, CUInt, CReal, CChar, CSChar, CUChar, CMax,
+ CInt = 0, CSInt, CUInt, CReal, CChar, CSChar, CUChar,
};
enum {
- SNone = 0, STypedef, SAuto, SRegister, SExtern, SStatic, SForced
+ SNone = 0, STypedef, SAuto, SRegister, SExtern, SStatic, SForced, SMax,
};
static struct symbol_op typedef_op = {
@@ -1281,7 +1281,7 @@ static const char *storage_class[] =
static unsigned long storage_modifiers(struct decl_state *ctx)
{
- static unsigned long mod[CMax] =
+ static unsigned long mod[SMax] =
{
[SAuto] = MOD_AUTO,
[SExtern] = MOD_EXTERN,
--
2.11.0
next prev parent reply other threads:[~2017-01-05 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 19:12 [PATCH] Handle SForced in storage_modifiers Jeff Layton
2016-11-14 20:04 ` Luc Van Oostenryck
2016-11-14 20:17 ` Linus Torvalds
2016-11-14 20:21 ` Luc Van Oostenryck
2016-11-15 1:00 ` Christopher Li
2016-11-15 2:07 ` Jeff Layton
2016-11-16 22:28 ` Christopher Li
2016-11-17 12:43 ` Jeff Layton
2017-01-05 6:39 ` Luc Van Oostenryck [this message]
2016-11-15 4:30 ` Josh Triplett
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=20170105063947.GA9300@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).