From: Simon Horman <horms@kernel.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Alexander Zubkov <green@qrator.net>,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
linux-newbie@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix misspelling of "accept*"
Date: Sun, 15 Sep 2024 19:54:25 +0100 [thread overview]
Message-ID: <20240915185425.GD167971@kernel.org> (raw)
In-Reply-To: <ZucKZcwmd28S_t24@gallifrey>
On Sun, Sep 15, 2024 at 04:25:09PM +0000, Dr. David Alan Gilbert wrote:
> * Alexander Zubkov (green@qrator.net) wrote:
> > Hi,
> >
> > I just wanted to kindly check in on the status of my patch. Please let
> > me know if any further action is needed from my side.
> >
> > Thanks for your time!
>
> I was only a reviewer on this; it'll need some of the netdev people
> to notice it for it to get further.
Hi,
Firstly I would suggest splitting the drivers/infiniband change into
a separate patch and sending it to the relevant Infiniband maintainers.
./scripts/get_maintainer.pl will help you find them.
And then posting what as left as a patch for net-next.
For guidance on that please see:
https://docs.kernel.org/process/maintainer-netdev.html
net-next is currently closed, as the merge window is open.
So you will need to wait until net-next reopens before posting
your patch for net-next. That will happen after v6.12-rc1
has been released, most likely a little over two weeks from now.
...
prev parent reply other threads:[~2024-09-15 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240622164013.24488-2-green@qrator.net>
2024-06-22 20:14 ` [PATCH] Fix misspelling of "accept*" Dr. David Alan Gilbert
2024-09-15 14:29 ` Alexander Zubkov
2024-09-15 16:25 ` Dr. David Alan Gilbert
2024-09-15 18:54 ` Simon Horman [this message]
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=20240915185425.GD167971@kernel.org \
--to=horms@kernel.org \
--cc=green@qrator.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=linux@treblig.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 NNTP newsgroup(s).