From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ardb@kernel.org>, Joey Gouly <Joey.Gouly@arm.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
"leif@nuviainc.com" <leif@nuviainc.com>,
Andreas Sandberg <Andreas.Sandberg@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH] ArmPkg/ArmGic: Fix maximum number of interrupts in GICv3
Date: Mon, 24 May 2021 12:58:42 +0000 [thread overview]
Message-ID: <AS8PR08MB680639A3E37A1F1575EFAECB84269@AS8PR08MB6806.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <9af50a9a-d64f-7036-8b0f-a2aeda9acf8f@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
Hi Laszlo,
Joey is not in office today. I will submit this patch shortly so that we can include this in the release.
Regards,
Sami Mujawar
From: Laszlo Ersek <lersek@redhat.com>
Date: Sunday, 23 May 2021 at 12:27
To: Ard Biesheuvel <ardb@kernel.org>, Joey Gouly <Joey.Gouly@arm.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>, ardb+tianocore@kernel.org <ardb+tianocore@kernel.org>, leif@nuviainc.com <leif@nuviainc.com>, Sami Mujawar <Sami.Mujawar@arm.com>, Andreas Sandberg <Andreas.Sandberg@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH] ArmPkg/ArmGic: Fix maximum number of interrupts in GICv3
On 05/23/21 11:03, Ard Biesheuvel wrote:
> On Sun, 23 May 2021 at 10:55, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>> On 05/21/21 12:49, Joey Gouly wrote:
>>>> From: Joey Gouly <joey.gouly@arm.com>
>>>> Sent: 09 March 2021 16:45
>>>> Subject: [PATCH] ArmPkg/ArmGic: Fix maximum number of interrupts in GICv3
>>>
>>> Hi,
>>>
>>> A little ping on this. Can someone take a look?
>>>
>>> There was a similar patch here, that addressed the same issue https://edk2.groups.io/g/devel/topic/82327316#74401 so I think it would be good get this in.
>>
>> This even looks like a candidate for edk2-stable202105 to me (it's small
>> and arguably a clear-cut bugfix).
>>
>> NB the comment style should be:
>>
>> //
>> // Interrupt ID 1020-1023 are reserved:
>> //
>>
>> IOW, we need a trailing and a leading empty comment line, plus the
>> semicolon at the end of the comment should likely be a colon, or maybe
>> just a period.
>>
>
> With that,
>
> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
>
Thank you, Ard!
Joey, can you please resubmit the patch with the comment fix, and Ard's
R-b, quickly?
Please use the following subject prefix:
[edk2-devel202105 PATCH v2]
Also, please file a bugzilla ticket for this issue at
<https://bugzilla.tianocore.org/>, and include the BZ URL in the commit
message. (It wouldn't be really necessary for such a small patch, but a
ticket is required during the feature freeze.)
Thanks
Laszlo
[-- Attachment #2: Type: text/html, Size: 4944 bytes --]
next prev parent reply other threads:[~2021-05-24 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:45 [PATCH] ArmPkg/ArmGic: Fix maximum number of interrupts in GICv3 Joey Gouly
2021-05-21 10:49 ` Joey Gouly
2021-05-23 8:55 ` [edk2-devel] " Laszlo Ersek
2021-05-23 9:03 ` Ard Biesheuvel
2021-05-23 11:26 ` Laszlo Ersek
2021-05-24 12:58 ` Sami Mujawar [this message]
2021-05-25 11:55 ` Laszlo Ersek
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=AS8PR08MB680639A3E37A1F1575EFAECB84269@AS8PR08MB6806.eurprd08.prod.outlook.com \
--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