From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] um: Preinclude include/linux/kern_levels.h
Date: Sun, 09 Sep 2012 08:09:25 -0700 [thread overview]
Message-ID: <1347203365.2050.3.camel@joe2Laptop> (raw)
In-Reply-To: <CAMuHMdVyWRGyTPbA9pL267XWnvBnbN77353WjF8Ovmd062NSwg@mail.gmail.com>
On Sun, 2012-09-09 at 10:33 +0200, Geert Uytterhoeven wrote:
> Ping?
Richard? Are you going to pick up this patch?
It seems sensible.
Geert, I suggest sending it directly to Linus as a fix
if Richard doesn't respond in a few days.
> On Thu, Aug 16, 2012 at 8:15 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > The userspace part of UML uses the asm-offsets.h generator mechanism to
> > create definitions for UM_KERN_<LEVEL> that match the in-kernel
> > KERN_<LEVEL> constant definitions.
> >
> > As of commit 04d2c8c83d0e3ac5f78aeede51babb3236200112 ("printk: convert
> > the format for KERN_<LEVEL> to a 2 byte pattern"), KERN_<LEVEL> is no
> > longer expanded to the literal '"<LEVEL>"', but to '"\001" "LEVEL"', i.e.
> > it contains two parts.
> >
> > However, the combo of DEFINE_STR() in
> > arch/x86/um/shared/sysdep/kernel-offsets.h and sed-y in Kbuild doesn't
> > support string literals consisting of multiple parts. Hence for all
> > UM_KERN_<LEVEL> definitions, only the SOH character is retained in the actual
> > definition, while the remainder ends up in the comment. E.g. in
> > include/generated/asm-offsets.h we get
> >
> > #define UM_KERN_INFO "\001" /* "6" KERN_INFO */
> >
> > instead of
> >
> > #define UM_KERN_INFO "\001" "6" /* KERN_INFO */
> >
> > This causes spurious '^A' output in some kernel messages:
next prev parent reply other threads:[~2012-09-09 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:15 [PATCH/RFC] um: Preinclude include/linux/kern_levels.h Geert Uytterhoeven
2012-09-09 8:33 ` Geert Uytterhoeven
2012-09-09 15:09 ` Joe Perches [this message]
2012-09-09 16:06 ` [uml-devel] " Richard Weinberger
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=1347203365.2050.3.camel@joe2Laptop \
--to=joe@perches.com \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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