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
| ||
|
Date: Mon, 30 Jan 2012 15:45:03 -0800 From: Joe Perches <joe@...ches.com> To: Larry Finger <Larry.Finger@...inger.net> Cc: "Devendra.Naga" <devendra.aaru@...il.com>, chaoming_li@...lsil.com.cn, linville@...driver.com, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/1] wireless: remove return in _rtl_pci_switch_clk_req On Mon, 2012-01-30 at 17:35 -0600, Larry Finger wrote: > The patch is OK, but the patch subject is bad. You should have "[PATCH] > rtlwifi:...". Your patch is for rtlwifi, not wireless. Hi Devendra. A reasonable rule of thumb is use the deepest directory path basename you can to prefix the patch. Something like: [PATCH] $(basename $(dirname $file)): terse description If you are patching drivers/net/ethernet/realtek/apt.c this becomes: [PATCH] realtek: terse description There are some exceptions though. One of them is if the patch is in staging, prefix with [PATCH] staging: $(basename $(dirname $file)): description cheers, Joe -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists