From: "Shashi Mallela" <shashi.mallela@linaro.org>
To: leif@nuviainc.com, ard.biesheuvel@arm.com, graeme@nuviainc.com
Cc: devel@edk2.groups.io
Subject: [PATCH v1 0/1] sbsa-wdt interrupt id update
Date: Mon, 14 Dec 2020 12:21:01 -0500 [thread overview]
Message-ID: <20201214172102.10598-1-shashi.mallela@linaro.org> (raw)
The previous value of interrupt id used was not in sync
with the interrupt id being used in qemu sbsa-ref platform
due to a conflict before merging and was missed in last review.
This was preventing the watchdog interrupt from getting
identified.Updated SBSA-wdt interrupt id in Gtdt table
to rectify the issue.
Shashi Mallela (1):
Silicon/Qemu/Sbsa: sbsa-wdt interrupt id update
Silicon/Qemu/SbsaQemu/AcpiTables/Gtdt.aslc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.27.0
next reply other threads:[~2020-12-14 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 17:21 Shashi Mallela [this message]
2020-12-14 17:21 ` [PATCH v1 1/1] Silicon/Qemu/Sbsa: sbsa-wdt interrupt id update Shashi Mallela
-- strict thread matches above, loose matches on Subject: below --
2020-12-11 17:03 [PATCH v1 0/1] " Shashi Mallela
2020-12-10 1:30 Shashi Mallela
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=20201214172102.10598-1-shashi.mallela@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