From: "Varghese, Vipin" <vipin.varghese@amd.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Neerav.Parikh@amd.com, Ferruh.Yigit@amd.com,
Clinton.France@amd.com
Subject: Re: [RFC] doc/linux_gsg: add amd configuration section
Date: Wed, 20 Dec 2023 15:06:15 +0530 [thread overview]
Message-ID: <d110b2ca-b60f-4266-b18a-7ddbeb20c3b9@amd.com> (raw)
In-Reply-To: <CAJFAV8yi4=s9PTdkt3rRs1j0iNPnDhJ0jr9-=UW0NoO6aBwiOw@mail.gmail.com>
On 12/20/2023 3:02 PM, David Marchand wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Wed, Dec 20, 2023 at 10:31 AM Varghese, Vipin <vipin.varghese@amd.com> wrote:
>> On 12/20/2023 2:57 PM, David Marchand wrote:
>>> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>>>
>>>
>>> On Wed, Dec 20, 2023 at 10:25 AM Varghese, Vipin <vipin.varghese@amd.com> wrote:
>>>> Got `Superseded` is there a new version shared for `AMD tuning guide`?
>>> That's a question for yourself.
>>> I saw two patches with the same title.
>> I am searching for the second one that you have mentioned.
>>
>>> More checks were passing on the more recent one.
>>> I marked the first as superseded.
>> I will reach out in slack if I am not able to find so.
> https://patchwork.dpdk.org/project/dpdk/list/?submitter=2511&state=*
I now understand. Checked the same, and fixed the windows git-bash. Did
not notice this,
Thanks for helping.
>
>
> --
> David Marchand
>
next prev parent reply other threads:[~2023-12-20 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:34 Vipin Varghese
2023-12-20 9:24 ` Varghese, Vipin
2023-12-20 9:27 ` David Marchand
2023-12-20 9:31 ` Varghese, Vipin
2023-12-20 9:32 ` David Marchand
2023-12-20 9:36 ` Varghese, Vipin [this message]
2024-01-16 15:14 ` Thomas Monjalon
2024-01-24 18:11 ` Varghese, Vipin
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 15:25 Vipin Varghese
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=d110b2ca-b60f-4266-b18a-7ddbeb20c3b9@amd.com \
--to=vipin.varghese@amd.com \
--cc=Clinton.France@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Neerav.Parikh@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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 NNTP newsgroup(s).