From: Simon Horman <horms@kernel.org>
To: Andrew Kreimer <algonell@gmail.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] net/mlx5: Fix typos
Date: Wed, 2 Oct 2024 14:48:11 +0100 [thread overview]
Message-ID: <20241002134811.GI1310185@kernel.org> (raw)
In-Reply-To: <20240915114225.99680-1-algonell@gmail.com>
On Sun, Sep 15, 2024 at 02:42:25PM +0300, Andrew Kreimer wrote:
> Fix typos in comments.
>
> Reported-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Andrew Kreimer <algonell@gmail.com>
Hi Andrew,
These changes look good to me.
However, the patch was posted while net-next was closed for the v6.12 merge
window. And, I assume because of that, it has been marked as deferred in
Patchwork.
In the meantime, net-next has reopened, so could you consider reposting
your patch. If you do so please mark it as v2 or repost of something like
that. And please include the target tree, net-next, in the subject.
Subject [PATCH net-next repost] ...
For reference, Netdev processes are documented here:
https://docs.kernel.org/process/maintainer-netdev.html
...
next prev parent reply other threads:[~2024-10-02 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 11:42 [PATCH] net/mlx5: Fix typos Andrew Kreimer
2024-10-02 13:48 ` Simon Horman [this message]
2024-10-02 15:48 ` Andrew Kreimer
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=20241002134811.GI1310185@kernel.org \
--to=horms@kernel.org \
--cc=algonell@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=willy@infradead.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).