From: Nick Clifton <nickc@redhat.com>
To: Andrew Carlotti <andrew.carlotti@arm.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] aarch64: Update Architecture Extensions documentation
Date: Wed, 24 Jan 2024 17:13:26 +0000 [thread overview]
Message-ID: <1b5a3f58-f34f-41ae-a400-5e00b866b69e@redhat.com> (raw)
In-Reply-To: <8e384d43-f5e7-7446-03a9-71e46baa5495@e124511.cambridge.arm.com>
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.
You know what - you are right and I am wrong. Documentation patches are
OK and I should have approved the patch for the branch. So I am doing so
now - please apply to the 2.42 branch.
Cheers
Nick
prev parent reply other threads:[~2024-01-24 17:13 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
2024-01-24 17:13 ` Nick Clifton [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=1b5a3f58-f34f-41ae-a400-5e00b866b69e@redhat.com \
--to=nickc@redhat.com \
--cc=andrew.carlotti@arm.com \
--cc=binutils@sourceware.org \
/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).