From: Jan Beulich <jbeulich@suse.com>
To: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>
Cc: "hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>,
"Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] Add AMD znver5 processor support
Date: Thu, 4 Jan 2024 09:19:33 +0100 [thread overview]
Message-ID: <95c91b49-0b0e-48e9-8ded-c5a22240bfbe@suse.com> (raw)
In-Reply-To: <DM6PR12MB479505C484AB7D35F3D18CFDE398A@DM6PR12MB4795.namprd12.prod.outlook.com>
On 26.12.2023 04:29, Joshi, Tejas Sanjay wrote:
> Thanks for the review! Can you please commit on my behalf?
Sure, but then please re-base over recent changes and submit a v2.
Jan
next prev parent reply other threads:[~2024-01-04 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 7:12 Joshi, Tejas Sanjay
2023-12-22 11:15 ` Jan Beulich
2023-12-26 3:29 ` Joshi, Tejas Sanjay
2024-01-04 8:19 ` Jan Beulich [this message]
2024-01-04 9:30 ` Joshi, Tejas Sanjay
2024-01-05 8:29 ` Jan Beulich
2024-01-05 9:35 ` Nick Clifton
2024-01-05 11:11 ` Jan Beulich
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=95c91b49-0b0e-48e9-8ded-c5a22240bfbe@suse.com \
--to=jbeulich@suse.com \
--cc=Ganesh.Gopalasubramanian@amd.com \
--cc=TejasSanjay.Joshi@amd.com \
--cc=Venkataramanan.Kumar@amd.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).