From: Dmitry Selyutin <ghostmansd@gmail.com>
Cc: Alan Modra <amodra@gmail.com>,
Luke Leighton <luke.leighton@gmail.com>,
Luke Kenneth Casson Leighton <lkcl@lkcl.net>,
binutils@sourceware.org
Subject: Re: [PATCH 0/2] extend opindex and fx_pcrel_adjust to 16 bits
Date: Wed, 25 May 2022 07:11:16 +0300 [thread overview]
Message-ID: <CAMqzjetR2L+BVYopnQRKBE-j0SMBX=7edmG2pBbSt81jc5w0Hw@mail.gmail.com> (raw)
In-Reply-To: <Yo2XRwYGN3axyAa8@squeak.grove.modra.org>
It seems GMail smashed the addresses for some reason, effectively
joining Luke with binutils into a single entity. Let me quote the
whole mail so that it's delivered to everyone.
On Wed, May 25, 2022 at 6:56 AM Dmitry Selyutin <ghostmansd@gmail.com> wrote:
>
> On Wed, May 25, 2022 at 5:41 AM Alan Modra <amodra@gmail.com> wrote:
> >
> > I'm about to apply the ppc_opindex_t patches, squashed into one
>
> Shouldn't I get write access to the repo to be able to push on my own
> after the review? I couldn't find the exact instructions about how to
> get it, though.
>
> > I've made some comment changes, plus gone back to masking
>
> Sure, fine with me, perfectly reasonable. Thank you!
next prev parent reply other threads:[~2022-05-25 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 17:59 Dmitry Selyutin
2022-05-12 7:32 ` [PATCH v2 1/2] ppc: extend opindex " Dmitry Selyutin
2022-05-12 7:32 ` [PATCH v2 2/2] gas/write: extend fx_pcrel_adjust " Dmitry Selyutin
2022-05-17 11:20 ` [PATCH 0/2] extend opindex and " Dmitry Selyutin
2022-05-24 21:09 ` Dmitry Selyutin
2022-05-25 2:41 ` Alan Modra
2022-05-25 4:11 ` Dmitry Selyutin [this message]
2022-05-25 4:32 ` Alan Modra
2022-05-25 4:35 ` Alan Modra
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='CAMqzjetR2L+BVYopnQRKBE-j0SMBX=7edmG2pBbSt81jc5w0Hw@mail.gmail.com' \
--to=ghostmansd@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=lkcl@lkcl.net \
--cc=luke.leighton@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).