From: Pedro Alves <palves@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
"jan.kratochvil@redhat.com" <jan.kratochvil@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] i386-cpuid: add support for identifying a processor
Date: Thu, 13 Feb 2014 18:32:00 -0000 [thread overview]
Message-ID: <52FD0FC4.9030007@redhat.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B230AA65499@IRSMSX104.ger.corp.intel.com>
On 02/13/2014 01:34 PM, Metzger, Markus T wrote:
> I need this for btrace
Please always send a rationale along with patches. I
looked over both patches, but couldn't figure out
what motivated them.
--
Pedro Alves
next prev parent reply other threads:[~2014-02-13 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 12:30 Markus Metzger
2014-02-13 12:30 ` [PATCH 2/2] btrace: use i386-cpuid's cpu identifier Markus Metzger
2014-02-13 13:29 ` [PATCH 1/2] i386-cpuid: add support for identifying a processor Mark Kettenis
2014-02-13 13:34 ` Metzger, Markus T
2014-02-13 18:32 ` Pedro Alves [this message]
2014-02-14 8:30 ` Metzger, Markus T
2014-02-14 17:29 ` Mike Frysinger
2014-02-17 8:04 ` Metzger, Markus T
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=52FD0FC4.9030007@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=markus.t.metzger@intel.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