From: Greg KH <greg@kroah.com>
To: akendo <akendo@akendo.eu>
Cc: "Subramaniam, Sujana" <sujana.subramaniam@sap.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Yevgeny Kliteynik <kliteyn@nvidia.com>,
Itamar Gozlan <igozlan@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Tariq Toukan <tariqt@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] net/mlx5: HWS, change error flow on matcher disconnect
Date: Wed, 3 Sep 2025 14:31:26 +0200 [thread overview]
Message-ID: <2025090307-exposure-demeanor-c016@gregkh> (raw)
In-Reply-To: <6c5efc80-9dcc-4943-9840-5e1046182101@akendo.eu>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Sep 03, 2025 at 02:21:29PM +0200, akendo wrote:
> Hello Greg,
>
> Thank you for your responses. We’re in the process of learning the process
> and figuring out how to get the git send-mail out.
>
> This patch aims for the kernel 6.12 and backports the changes for the mlx5
> from 6.13 to it. We use the 1ce840c7a659aa53a31ef49f0271b4fd0dc10296 commit
> from upsteam to do it. We had to update the path within the patch to make
> the patch apply that’s the only change we made. We roll this out in our
> kernel and test it already.
>
> I forgot to add my full name to it, we will fix Sujana's Name is correct.
> Please, I apologize for the puzzlement we might have caused.
Great, please fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-03 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 8:40 [PATCH] net/mlx5: HWS, change error flow on matcher disconnect Subramaniam, Sujana
2025-09-03 9:41 ` Greg KH
2025-09-03 12:21 ` akendo
2025-09-03 12:31 ` Greg KH [this message]
2025-09-03 12:46 ` akendo
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=2025090307-exposure-demeanor-c016@gregkh \
--to=greg@kroah.com \
--cc=akendo@akendo.eu \
--cc=igozlan@nvidia.com \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=mbloch@nvidia.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sujana.subramaniam@sap.com \
--cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.