From: Matt Fleming <matt@codeblueprint.co.uk>
To: Alexander Popov <alpopov@ptsecurity.com>
Cc: Peter Jones <pjones@redhat.com>, Ingo Molnar <mingo@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH RFC 1/1] x86: fix bad memory access in fb_is_primary_device()
Date: Tue, 29 Mar 2016 12:53:47 +0100 [thread overview]
Message-ID: <20160329115347.GA3625@codeblueprint.co.uk> (raw)
In-Reply-To: <56F52111.6050500@ptsecurity.com>
On Fri, 25 Mar, at 02:29:21PM, Alexander Popov wrote:
>
> Excuse me, there is no reply for a long time. Did I touch any taboo topic?
> Hope to fix this bug. Thanks.
Unless anyone complains soonish I'll send this to tip as part of the
EFI urgent queue.
next prev parent reply other threads:[~2016-03-29 11:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 9:30 [PATCH RFC 1/1] x86: fix bad memory access in fb_is_primary_device() Alexander Popov
2016-02-16 7:55 ` Ingo Molnar
2016-02-16 13:49 ` Matt Fleming
[not found] ` <20160216134918.GD2769-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-02-16 15:18 ` Peter Jones
2016-02-16 15:18 ` Peter Jones
2016-03-09 12:46 ` Alexander Popov
2016-03-09 12:46 ` Alexander Popov
[not found] ` <56E01B0F.3000306-rHsQqRFQpp1OSnsfY10OVw@public.gmane.org>
2016-03-25 11:29 ` Alexander Popov
2016-03-25 11:29 ` Alexander Popov
2016-03-29 11:53 ` Matt Fleming [this message]
[not found] ` <20160329115347.GA3625-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-03-29 12:12 ` Matt Fleming
2016-03-29 12:12 ` Matt Fleming
[not found] ` <56F52111.6050500-rHsQqRFQpp1OSnsfY10OVw@public.gmane.org>
2016-03-31 13:31 ` Ingo Molnar
2016-03-31 13:31 ` Ingo Molnar
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=20160329115347.GA3625@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=alpopov@ptsecurity.com \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
--cc=tomi.valkeinen@ti.com \
--cc=x86@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 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.