lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17c8bded-5d29-49e9-b38d-3f0c95e4b15b@linux.alibaba.com>
Date: Thu, 19 Sep 2024 14:31:23 +0800
From: Philo Lu <lulie@...ux.alibaba.com>
To: "Muggeridge, Matt" <matt.muggeridge2@....com>,
 "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Submitted a patch, got error "Patch does not apply to net-next-0"

Hi Matt,

On 2024/9/19 10: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?
> 

It's recommended to first correct the mail format, such as adding a 
"Signed-off-by", and send the patch with `git send-email`.

May this doc[0] helps you.

[0]https://www.kernel.org/doc/html/latest/process/submitting-patches.html

-- 
Philo


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ