From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Cc: Sai Praneeth Prakhya
<sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
Ricardo Neri
<ricardo.neri-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Glenn P Williamson
<glenn.p.williamson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Ravi Shankar
<ravi.v.shankar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH V2] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled
Date: Sat, 17 Oct 2015 19:26:51 +0100 [thread overview]
Message-ID: <20151017182651.GA9866@codeblueprint.co.uk> (raw)
In-Reply-To: <20151017094738.GA3669-fF5Pk5pvG8Y@public.gmane.org>
On Sat, 17 Oct, at 11:47:38AM, Borislav Petkov wrote:
>
> Looks ok to me, these minor nitpicks can be adjusted when applying, no
> need to send another version.
>
> Which brings me to the next question: Matt, are you picking this up or
> should I?
I'll pick it up and make your suggested changes.
> If you, then
>
> Reviewed-by: Borislav Petkov <bp-l3A5Bk7waGM@public.gmane.org>
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Borislav Petkov <bp@alien8.de>
Cc: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
dave.hansen@intel.com, Ricardo Neri <ricardo.neri@intel.com>,
Glenn P Williamson <glenn.p.williamson@intel.com>,
Ravi Shankar <ravi.v.shankar@intel.com>
Subject: Re: [PATCH V2] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled
Date: Sat, 17 Oct 2015 19:26:51 +0100 [thread overview]
Message-ID: <20151017182651.GA9866@codeblueprint.co.uk> (raw)
In-Reply-To: <20151017094738.GA3669@pd.tnic>
On Sat, 17 Oct, at 11:47:38AM, Borislav Petkov wrote:
>
> Looks ok to me, these minor nitpicks can be adjusted when applying, no
> need to send another version.
>
> Which brings me to the next question: Matt, are you picking this up or
> should I?
I'll pick it up and make your suggested changes.
> If you, then
>
> Reviewed-by: Borislav Petkov <bp@suse.de>
Thanks!
next prev parent reply other threads:[~2015-10-17 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 23:20 [PATCH V2] x86/efi: Fix kernel panic when CONFIG_DEBUG_VIRTUAL is enabled Sai Praneeth Prakhya
2015-10-16 23:20 ` Sai Praneeth Prakhya
[not found] ` <1445037627-6488-1-git-send-email-sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-10-17 9:47 ` Borislav Petkov
2015-10-17 9:47 ` Borislav Petkov
[not found] ` <20151017094738.GA3669-fF5Pk5pvG8Y@public.gmane.org>
2015-10-17 18:26 ` Matt Fleming [this message]
2015-10-17 18:26 ` Matt Fleming
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=20151017182651.GA9866@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=glenn.p.williamson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ravi.v.shankar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=ricardo.neri-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.