From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Joshi, Tejas Sanjay" <TejasSanjay.Joshi@amd.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
Jan Beulich <jbeulich@suse.com>,
"Gopalasubramanian, Ganesh" <Ganesh.Gopalasubramanian@amd.com>
Subject: Re: [PATCH] Add znver4 processor support
Date: Tue, 15 Nov 2022 08:12:49 -0800 [thread overview]
Message-ID: <CAMe9rOpHv3T6E7n=B14Y5EA2nLAZnCGxr0V5hYZZDx9poeT6MQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR12MB4795CC5E47B1B5B62C56A8A3E3049@DM6PR12MB4795.namprd12.prod.outlook.com>
On Mon, Nov 14, 2022 at 9:20 PM Joshi, Tejas Sanjay
<TejasSanjay.Joshi@amd.com> wrote:
>
> [Public]
>
> > Please generate your patch with "git format-patch" and send it as an attachment.
>
> Please find the patch attached herewith.
>
> Thanks and Regards,
> Tejas
Your patch doesn't apply:
Applying: Add AMD znver4 processor support
error: patch failed: gas/config/tc-i386.c:1095
error: gas/config/tc-i386.c: patch does not apply
Patch failed at 0001 Add AMD znver4 processor support
Please rebase your patch.
--
H.J.
next prev parent reply other threads:[~2022-11-15 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 7:20 [PATCH] Joshi, Tejas Sanjay
2022-10-28 7:22 ` [PATCH] Add znver4 processor support Joshi, Tejas Sanjay
2022-10-28 8:15 ` [PATCH] Jan Beulich
2022-10-28 15:45 ` [PATCH] H.J. Lu
2022-10-31 4:37 ` [PATCH] Joshi, Tejas Sanjay
2022-10-31 9:37 ` [PATCH] Jan Beulich
2022-11-08 10:18 ` [PATCH] Add znver4 processor support Jan Beulich
2022-11-09 7:14 ` Joshi, Tejas Sanjay
2022-11-09 20:18 ` H.J. Lu
2022-11-12 19:00 ` Joshi, Tejas Sanjay
2022-11-14 22:58 ` H.J. Lu
2022-11-15 5:20 ` Joshi, Tejas Sanjay
2022-11-15 16:12 ` H.J. Lu [this message]
2022-11-15 17:51 ` Joshi, Tejas Sanjay
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='CAMe9rOpHv3T6E7n=B14Y5EA2nLAZnCGxr0V5hYZZDx9poeT6MQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=Ganesh.Gopalasubramanian@amd.com \
--cc=TejasSanjay.Joshi@amd.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).