public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v2 0/8] ArmCpuInfo improvements
Date: Mon, 24 Jul 2023 17:33:04 +0200	[thread overview]
Message-ID: <28b90501-1287-b401-df31-8bddaa6c10f9@linaro.org> (raw)
In-Reply-To: <349c2c6d-775d-94cc-366e-3437b36b2b28@linaro.org>

W dniu 23.06.2023 o 13:08, Marcin Juszkiewicz pisze:
> W dniu 5.06.2023 o 08:37, Marcin Juszkiewicz via groups.io pisze:
>> This changeset was supposed to add SVE/SME information but got some
>> updates to improve output of ArmCpuInfo application a bit too.
>>
>> Probably would need to definition of system registers for older
>> toolchains.
>>
>> Changes since v1:
>> - show stage 2 granule support on Neoverse-N1
> 
> Can someone review that patchset? Or should I abandon any hope?

Summer time feels like bad time for sending code upstream.

Reviewers are either on holidays or exhausted because of heat.


August will be 'read some docs' month rather than 'submit some code' 
while waiting for September/October to get maintainers alive again.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107174): https://edk2.groups.io/g/devel/message/107174
Mute This Topic: https://groups.io/mt/99335290/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



      reply	other threads:[~2023-07-24 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1765AFEF07E7788C.3349@groups.io>
2023-06-23 11:08 ` [edk2-devel] [PATCH v2 0/8] ArmCpuInfo improvements Marcin Juszkiewicz
2023-07-24 15:33   ` Marcin Juszkiewicz [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-list 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=28b90501-1287-b401-df31-8bddaa6c10f9@linaro.org \
    --to=devel@edk2.groups.io \
    /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