From: Andi Kleen <andi@firstfloor.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] test-hexdump.c: Fix initconst confusion
Date: Thu, 16 Apr 2015 23:21:00 +0200 [thread overview]
Message-ID: <20150416212059.GV2366@two.firstfloor.org> (raw)
In-Reply-To: <CAMuHMdWd9vPb9-MgJdHBNHFUKzXKOp1wY8+OOVxVJKs9cPc3CA@mail.gmail.com>
> > I tried it, but it would have needed a lot more changes to shut up
> > warnings later in the code. This was the least intrusive.
>
> "a lot more changes" is "one more change"? (patch sent)
Thanks Geert. You're right of course.
-Andi
prev parent reply other threads:[~2015-04-16 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:06 [PATCH 1/2] Don't let LATENCYTOP and LOCKDEP select KALLSYMS_ALL Andi Kleen
2015-04-08 13:06 ` [PATCH 2/2] test-hexdump.c: Fix initconst confusion Andi Kleen
2015-04-08 22:35 ` Andrew Morton
2015-04-08 23:52 ` Andi Kleen
2015-04-09 0:14 ` [PATCH] checkpatch: Add a test for const with __read_mostly uses Joe Perches
2015-04-09 0:28 ` Andi Kleen
2015-04-09 0:33 ` Joe Perches
2015-04-16 19:33 ` [PATCH 2/2] test-hexdump.c: Fix initconst confusion Geert Uytterhoeven
2015-04-16 21:21 ` Andi Kleen [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=20150416212059.GV2366@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.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