From: Andrew Carlotti <andrew.carlotti@arm.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] aarch64: Update Architecture Extensions documentation
Date: Tue, 23 Jan 2024 18:36:16 +0000 [thread overview]
Message-ID: <8e384d43-f5e7-7446-03a9-71e46baa5495@e124511.cambridge.arm.com> (raw)
In-Reply-To: <e27376bb-ebb9-4dfa-8866-dab733b8cc3e@redhat.com>
On Mon, Jan 22, 2024 at 05:11:19PM +0000, Nick Clifton wrote:
> Hi Andrew,
>
> > Restructure the architecture extensions table, add a new table for architecture
> > version dependencies, add missing architecture extensions, and improve some
> > extension descriptions.
> >
> > Ok for master and 2.42 branch?
>
> Approved for master. Not approved for the branch. (This is not really a bug
> fix, so it does not meet the criteria for branch commits).
I agree it's not a bug fix, but your announcement said:
> The rules for the branch are:
> ...
> * Documentation updates/fixes are OK.
Of course, if you don't want it in the branch then it won't go in.
> Cheers
> Nick
>
next prev parent reply other threads:[~2024-01-23 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 17:29 Andrew Carlotti
2024-01-22 17:11 ` Nick Clifton
2024-01-23 18:36 ` Andrew Carlotti [this message]
2024-01-24 17:13 ` Nick Clifton
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=8e384d43-f5e7-7446-03a9-71e46baa5495@e124511.cambridge.arm.com \
--to=andrew.carlotti@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).