From: Baoquan He <bhe@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: panand@redhat.com, kexec@lists.infradead.org,
Philip Prindeville <philipp_subx@redfish-solutions.com>,
Dave Young <dyoung@redhat.com>,
thgarnie@google.com
Subject: Re: [PATCH v3] Only print debug message when failed to serach for kernel symbol from /proc/kallsyms
Date: Fri, 10 Mar 2017 17:23:26 +0800 [thread overview]
Message-ID: <20170310092326.GA27791@x1> (raw)
In-Reply-To: <20170310091450.GC21820@verge.net.au>
On 03/10/17 at 10:14am, Simon Horman wrote:
> On Thu, Mar 09, 2017 at 03:29:45PM +0800, Baoquan He wrote:
> > On 03/08/17 at 09:13pm, Philip Prindeville wrote:
> > > Inline…
> > >
> > >
> > > > On Mar 5, 2017, at 6:46 PM, Dave Young <dyoung@redhat.com> wrote:
> > > >
> > > > On 03/03/17 at 11:52am, Baoquan He wrote:
> > > >> Kernel symbol page_offset_base could be unavailable when mm KASLR code is
> > > >> not compiled in kernel. It's unappropriate to print out error message
> > >
> > > I subscribed to the list the day after this patch went out… Anyway, change to “inappropriate”.
> >
> > Indeed, not sure if Simon want a repost.
>
> No need, I have fixed up the change log and applied the patch.
Thanks, Simon!
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-03-10 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 3:52 [PATCH v3] Only print debug message when failed to serach for kernel symbol from /proc/kallsyms Baoquan He
2017-03-03 4:05 ` Pratyush Anand
2017-03-06 1:46 ` Dave Young
2017-03-09 4:13 ` Philip Prindeville
2017-03-09 7:29 ` Baoquan He
2017-03-10 9:14 ` Simon Horman
2017-03-10 9:23 ` Baoquan He [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=20170310092326.GA27791@x1 \
--to=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=panand@redhat.com \
--cc=philipp_subx@redfish-solutions.com \
--cc=thgarnie@google.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