From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Muggeridge, Matt" <matt.muggeridge2@hpe.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Submitted a patch, got error "Patch does not apply to net-next-0"
Date: Thu, 19 Sep 2024 07:57:24 +0200 [thread overview]
Message-ID: <2a39433c-3448-4375-9d69-6067e833d988@gmail.com> (raw)
In-Reply-To: <SJ0PR84MB208883688BD13CC7AA8F880ED8632@SJ0PR84MB2088.NAMPRD84.PROD.OUTLOOK.COM>
On 19.09.2024 04:23, Muggeridge, Matt wrote:
> Hi,
>
> First time submitter and it seems I did something wrong, as I got the error "Patch does not apply to net-next-0". I suspected it was complaining about a missing end-of-line, so I resubmitted and get the error "Patch does not apply to net-next-1". So now I'm unsure how to correct this.
>
> My patch is: Netlink flag for creating IPv6 Default Routes (https://patchwork.kernel.org/project/netdevbpf/patch/SJ0PR84MB2088B1B93C75A4AAC5B90490D8632@SJ0PR84MB2088.NAMPRD84.PROD.OUTLOOK.COM/).
>
> I followed the instructions at https://www.kernel.org/doc/html/v5.12/networking/netdev-FAQ.html.
>
> Here's my local repo:
>
> $ git remote -v
> origin https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git (fetch)
> origin https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git (push)
>
> After committing my changes, I ran:
>
> $ git format-patch --subject-prefix='PATCH net-next' -1 95c6e5c898d3
>
> It produced the file "0001-Netlink-flag-for-creating-IPv6-Default-Routes.patch". I emailed the contents of that file to this list.
>
> How do I correct this?
>
> Thanks,
> Matt.
>
>
There's few issues with your submission:
- net-next is closed currently. There's a section in the FAQ explaining when and why it's closed.
- Please only one version of a patch per day
- Your commit message states that the patch fixes something. So you should add a Fixes tag.
If applicable also cc the patch to stable.
https://www.kernel.org/doc/Documentation/process/stable-kernel-rules.rst
- If the fixed change isn't in net-next only, your patch should be based on and tagged "net".
- Patch title should be prefixed ipv6 or net/ipv6. Not sure which is preferred, both are common.
See change history of net/ipv6/route.c
next prev parent reply other threads:[~2024-09-19 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 2:23 Submitted a patch, got error "Patch does not apply to net-next-0" Muggeridge, Matt
2024-09-19 5:57 ` Heiner Kallweit [this message]
2024-09-19 20:30 ` Muggeridge, Matt
2024-09-19 20:57 ` Heiner Kallweit
2024-09-19 22:53 ` Muggeridge, Matt
2024-09-20 2:31 ` Stephen Hemminger
2024-09-19 6:31 ` Philo Lu
2024-09-19 7:50 ` Paolo Abeni
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=2a39433c-3448-4375-9d69-6067e833d988@gmail.com \
--to=hkallweit1@gmail.com \
--cc=matt.muggeridge2@hpe.com \
--cc=netdev@vger.kernel.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).