From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH], Patch #10, move PowerPC data structures & helper functions from rs6000.c to rs6000-internal.h
Date: Mon, 22 Jul 2019 20:45:00 -0000 [thread overview]
Message-ID: <20190722195555.GG20882@gate.crashing.org> (raw)
In-Reply-To: <20190722183600.GB30230@ibm-toto.the-meissners.org>
On Mon, Jul 22, 2019 at 02:36:00PM -0400, Michael Meissner wrote:
> On Sun, Jul 21, 2019 at 12:41:51PM -0500, Segher Boessenkool wrote:
> > On Sat, Jul 20, 2019 at 12:13:08PM -0400, Michael Meissner wrote:
> > > I will be iterating on patch #9 and sending out a replacement shortly.
> > >
> > > This is patch #10. It moves the various data structures from rs6000.c to
> >
> > I'll review this tomorrow, fwiw.
> >
> > A general request: please don't send patches as replies to other emails.
>
> In the past you had asked me to group patches under a single overview patch. I
> can go back to sending patches individually.
When you send a *series*, please send it as series; when you send
individual patches, please send them individually. This is all about
how people will get it in their email, and how they will handle it.
This really *is* a series, just most patches do not exist yet, if I
understand correctly. That is not ideal of course -- I cannot review
it as a series, because I don't have the later patches. Sending the
patches as replies to weeks-old other patches is less than useful.
Segher
next prev parent reply other threads:[~2019-07-22 19:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 0:06 Add support for PowerPC prefixed memory instructions and pc-relative support (Intro) Michael Meissner
2019-06-28 0:12 ` [PATCH] PowerPC Prefixed Memory, Patch #3, Update predicates Michael Meissner
2019-06-28 13:20 ` Segher Boessenkool
2019-06-28 14:56 ` Bill Schmidt
2019-06-28 18:54 ` Michael Meissner
2019-06-28 18:50 ` [PATCH] PowerPC Prefixed Memory, Patch #4, Add pc-relative reference support Michael Meissner
2019-07-03 22:20 ` Segher Boessenkool
2019-07-08 18:53 ` Michael Meissner
2019-07-08 18:54 ` Segher Boessenkool
2019-07-09 17:36 ` [PATCH, committed] PowerPC Prefixed Memory, Patch #5 (move create_TOC_reference) Michael Meissner
2019-07-09 18:34 ` Segher Boessenkool
2019-07-09 22:42 ` [PATCH], PowerPC, Patch #6, Create pc-relative addressing insns Michael Meissner
2019-07-10 17:43 ` Segher Boessenkool
2019-07-10 17:57 ` Michael Meissner
2019-07-10 18:55 ` Segher Boessenkool
2019-07-10 21:51 ` [PATCH], PowerPC, Patch #6, revision 2, " Michael Meissner
2019-07-11 20:10 ` Segher Boessenkool
2019-07-11 21:04 ` Michael Meissner
2019-07-11 21:38 ` Segher Boessenkool
2019-07-10 0:28 ` [PATCH], PowerPC, Patch #7, Split up SIGNED_34BIT and SIGNED_16BIT macros Michael Meissner
2019-07-10 18:37 ` Segher Boessenkool
2019-07-11 12:17 ` [PATCH], PowerPC, Patch #8, rename rs6000_prefixed_address Michael Meissner
2019-07-11 21:37 ` Segher Boessenkool
2019-07-11 19:45 ` [PATCH], PowerPC, Patch #9, Refine calculation of whether an address offset is d-form, ds-form, or dq-form Michael Meissner
2019-07-12 17:05 ` Segher Boessenkool
2019-07-16 18:00 ` Michael Meissner
2019-07-16 23:31 ` Segher Boessenkool
2019-07-16 6:35 ` [PATCH], Patch #6, revision 3, Create pc-relative addressing insns Michael Meissner
2019-07-16 21:09 ` Segher Boessenkool
2019-07-18 19:34 ` Michael Meissner
2019-07-18 19:43 ` Segher Boessenkool
2019-07-17 5:44 ` [PATCH], Patch #6, revision 3, (Test on AIX and Darwin) Michael Meissner
2019-07-20 16:28 ` [PATCH], Patch #10, move PowerPC data structures & helper functions from rs6000.c to rs6000-internal.h Michael Meissner
2019-07-20 16:54 ` David Edelsohn
2019-07-22 18:37 ` Michael Meissner
2019-07-22 19:55 ` Segher Boessenkool
2019-07-21 18:13 ` Segher Boessenkool
2019-07-22 18:59 ` Michael Meissner
2019-07-22 20:45 ` Segher Boessenkool [this message]
2019-07-22 5:56 ` Segher Boessenkool
2019-07-22 19:33 ` Michael Meissner
2019-07-22 21:33 ` Segher Boessenkool
2019-07-22 23:11 ` Michael Meissner
2019-07-25 13:30 ` Segher Boessenkool
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=20190722195555.GG20882@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@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).