Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
To: Pedro Alves <palves@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [OBV] amd64-features-makefile: add missing backslash.
Date: Wed, 20 Sep 2017 16:00:00 -0000	[thread overview]
Message-ID: <c25bbf7d-cce3-26d2-9617-928eb3addf5d@intel.com> (raw)
In-Reply-To: <29be83e6-2984-487d-2f18-cd4df17c8c4c@redhat.com>



On 09/20/2017 05:56 PM, Pedro Alves wrote:
> On 09/20/2017 04:09 PM, Tedeschi, Walfred wrote:
>> Hello All,
>>
>> I have pushed this patch as obvious, basically there was no need to regenerate files.
>> Those files were modified by Yao already.
>>
>> The change was only this:
>> -$(outdir)/i386/i386-avx-mpx-avx512-pku.dat: i386/32bit-core.xml
>> +$(outdir)/i386/i386-avx-mpx-avx512-pku.dat: i386/32bit-core.xml \
>>
>> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=1b7fa39ed9678fded7264636c1e5cc14c6d6ebc6
> We still need the fix (plus regeneration) on the 8.0 branch, right?
>
> Thanks,
> Pedro Alves
>

Yes, I have added the patch in the bugzilla. Can i commit also there?

Thanks and regards,
/Fred
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  parent reply	other threads:[~2017-09-20 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 15:09 Tedeschi, Walfred
     [not found] ` <29be83e6-2984-487d-2f18-cd4df17c8c4c@redhat.com>
2017-09-20 16:00   ` Tedeschi, Walfred [this message]
2017-09-20 16:06     ` Pedro Alves

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=c25bbf7d-cce3-26d2-9617-928eb3addf5d@intel.com \
    --to=walfred.tedeschi@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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