From: Yulia Koval <vaalfreja@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix typo.
Date: Tue, 03 Nov 2015 16:04:00 -0000 [thread overview]
Message-ID: <CAE0nxxi2f9g2Vs_YkZ+KkNn-TLMZq4J=XYhMoPuNR+v2eLE9YA@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4ZNrGHb62XdoHJ4eYwKQCOfnPqtnLkcCsYyPM0Bfq2_nQ@mail.gmail.com>
Here it is.
gcc/
* config/i386/i386.c (m_SKYLAKE_AVX512): Fix typo.
Yulia
On Tue, Nov 3, 2015 at 5:32 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> On Tue, Nov 3, 2015 at 3:16 PM, Yulia Koval <vaalfreja@gmail.com> wrote:
>> Hi,
>>
>> This patch fixes a typo: PROCESSOT -> PROCESSOR. Ok for trunk?
>
> Trivial patch, OK with a suitable ChangeLog.
>
> Uros.
next prev parent reply other threads:[~2015-11-03 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 14:16 Yulia Koval
2015-11-03 14:32 ` Uros Bizjak
2015-11-03 16:04 ` Yulia Koval [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-23 3:01 Xionghu Luo
2019-10-24 11:20 Richard Biener
2015-05-10 21:01 Paulo Matos
2015-05-11 4:07 ` Jeff Law
2015-05-11 18:15 ` Paulo Matos
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='CAE0nxxi2f9g2Vs_YkZ+KkNn-TLMZq4J=XYhMoPuNR+v2eLE9YA@mail.gmail.com' \
--to=vaalfreja@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).