From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: wschmidt@linux.ibm.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v3 0/6] rs6000: Support more SSE4 intrinsics
Date: Mon, 11 Oct 2021 19:15:34 -0500 [thread overview]
Message-ID: <20211012001534.GG10333@gate.crashing.org> (raw)
In-Reply-To: <20211008002926.GB243632@li-24c3614c-2adc-11b2-a85c-85f334518bdb.ibm.com>
On Thu, Oct 07, 2021 at 07:29:26PM -0500, Paul A. Clarke wrote:
> On Thu, Oct 07, 2021 at 05:25:54PM -0500, Segher Boessenkool wrote:
> > On Mon, Aug 23, 2021 at 02:03:04PM -0500, Paul A. Clarke wrote:
> > > v3: Add "nmmintrin.h". _mm_cmpgt_epi64 is part of SSE4.2
> >
> > There should not be a "v3" in the commit message. The easy way to
> > achieve this is put it inside the [] in the subject (as you did), and to
> > mention the version history after a --- (see --notes for git-format-patch
> > for example).
>
> This is just a cover letter. Does it matter in that context?
Ha no, it just confused me apparently :-)
Segher
prev parent reply other threads:[~2021-10-12 0:17 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 19:03 Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 1/6] rs6000: Support SSE4.1 "round" intrinsics Paul A. Clarke
2021-08-27 13:44 ` Bill Schmidt
2021-08-27 13:47 ` Bill Schmidt
2021-08-30 21:16 ` Paul A. Clarke
2021-08-30 21:24 ` Bill Schmidt
2021-10-07 23:08 ` Segher Boessenkool
2021-10-07 23:39 ` Segher Boessenkool
2021-10-08 1:04 ` Paul A. Clarke
2021-10-08 17:39 ` Segher Boessenkool
2021-10-08 19:27 ` Paul A. Clarke
2021-10-08 22:31 ` Segher Boessenkool
2021-10-11 13:46 ` Paul A. Clarke
2021-10-11 16:28 ` Segher Boessenkool
2021-10-11 17:31 ` Paul A. Clarke
2021-10-11 22:04 ` Segher Boessenkool
2021-10-12 19:35 ` Paul A. Clarke
2021-10-12 22:25 ` Segher Boessenkool
2021-10-19 0:36 ` Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 2/6] rs6000: Support SSE4.1 "min" and "max" intrinsics Paul A. Clarke
2021-08-27 13:47 ` Bill Schmidt
2021-10-11 19:28 ` Segher Boessenkool
2021-10-12 1:42 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 3/6] rs6000: Simplify some SSE4.1 "test" intrinsics Paul A. Clarke
2021-08-27 13:48 ` Bill Schmidt
2021-10-11 20:50 ` Segher Boessenkool
2021-10-12 1:47 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 4/6] rs6000: Support SSE4.1 "cvt" intrinsics Paul A. Clarke
2021-08-27 13:49 ` Bill Schmidt
2021-10-11 21:52 ` Segher Boessenkool
2021-10-12 1:51 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 5/6] rs6000: Support more SSE4 "cmp", "mul", "pack" intrinsics Paul A. Clarke
2021-08-27 15:21 ` Bill Schmidt
2021-08-27 18:52 ` Paul A. Clarke
2021-10-11 23:07 ` Segher Boessenkool
2021-10-12 1:55 ` [COMMITTED v4 " Paul A. Clarke
2021-08-23 19:03 ` [PATCH v3 6/6] rs6000: Guard some x86 intrinsics implementations Paul A. Clarke
2021-08-27 15:25 ` Bill Schmidt
2021-10-12 0:11 ` Segher Boessenkool
2021-10-13 17:04 ` Paul A. Clarke
2021-10-13 23:47 ` Segher Boessenkool
2021-10-19 0:26 ` Paul A. Clarke
2021-09-16 14:59 ` [PATCH v3 0/6] rs6000: Support more SSE4 intrinsics Paul A. Clarke
2021-10-04 18:26 ` Paul A. Clarke
2021-10-07 22:25 ` Segher Boessenkool
2021-10-08 0:29 ` Paul A. Clarke
2021-10-12 0:15 ` 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=20211012001534.GG10333@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pc@us.ibm.com \
--cc=wschmidt@linux.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).