From: Dave Young <dyoung@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: Minfei Huang <mhuang@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Minfei Huang <mnfhuang@gmail.com>
Subject: Re: [PATCH] kexec: Add prefix "kexec" to output message
Date: Wed, 23 Sep 2015 15:01:21 +0800 [thread overview]
Message-ID: <20150923070121.GC4394@dhcp-129-160.nay.redhat.com> (raw)
In-Reply-To: <20150923024933.GB3166@dhcp-17-102.nay.redhat.com>
On 09/23/15 at 10:49am, Baoquan He wrote:
> On 09/23/15 at 09:37am, Dave Young wrote:
> > > > Hi, Dave.
> > > >
> > > > How about removing all of the prefix "crashkernel" in kexec_core. Thus
> > > > we can be consistent with the output message prefix "kexec".
> > >
> > > Ping, any comment is appreciate and helpful.
> >
> > Remove "crashkernel" sounds not a proper way, it indicates crashkernel parsing
> > messages. I have no idea what is the best way but below modification sounds better to me:
> >
> > kexec_core.c:
> >
> > #define pr_fmt(fmt) "[kexec_core] " fmt
> > Also remove below prefix "Kexec:"
> > pr_warn("Kexec: Memory allocation for saving cpu register states failed\n");
> >
> > kexec.c:
> > #define pr_fmt(fmt) "[kexec] " fmt
> >
> > kexec_file.c:
> > #define pr_fmt(fmt) "[kexec_file] " fmt
>
> This is weird, user really don't need to know each file. I saw you added
> a new file kexec_internal.h and all three files includes it. Why not doing
> it there to make it the same as before?
I personally do not like add these prefix to a header file. One prefix for
a c file is better to me.
But rethinking about the prefix, looks like there's a lot of other components
using ":" so KBUILD_MODNAME ": " should be fine.
Thanks
Dave
prev parent reply other threads:[~2015-09-23 7:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 7:15 Minfei Huang
2015-09-13 16:52 ` Eric W. Biederman
2015-09-14 7:50 ` Minfei Huang
2015-09-14 8:44 ` Dave Young
2015-09-15 3:08 ` Minfei Huang
2015-09-22 16:07 ` Minfei Huang
2015-09-23 1:37 ` Dave Young
2015-09-23 2:49 ` Baoquan He
2015-09-23 5:14 ` Minfei Huang
2015-09-23 5:26 ` Baoquan He
2015-09-23 5:44 ` Minfei Huang
2015-09-23 7:01 ` Dave Young [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=20150923070121.GC4394@dhcp-129-160.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.com \
--cc=mnfhuang@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
all inboxes | Powered by JetHome®