public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Carl Love <cel@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
	       Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH, rs6000]  Fix typo in documentation file.
Date: Mon, 29 Jan 2018 19:23:00 -0000	[thread overview]
Message-ID: <20180129162558.GA21977@gate.crashing.org> (raw)
In-Reply-To: <1517242110.3596.1.camel@us.ibm.com>

Hi Carl,

On Mon, Jan 29, 2018 at 08:08:30AM -0800, Carl Love wrote:
> The following patch contains fixes for the GCC documentation file. 
> There is a missing space between vector and the type __int128_t in the
> second argument of the documented function.  
> 
> The patch makes no functional changes to GCC, just fixes a trivial
> typo.

This is fine for trunk (all trivial/obvious patches are).  Thanks!

But, still needs a changelog ;-)


Segher

      reply	other threads:[~2018-01-29 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 18:14 Carl Love
2018-01-29 19:23 ` Segher Boessenkool [this message]

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=20180129162558.GA21977@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=cel@us.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=wschmidt@linux.vnet.ibm.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).