From: "Devendra.Naga" <redacted>
the return value from _rtl_pci_switch_clk_req is not used by any of its callers.
Signed-off-by: Devendra.Naga <redacted>
---
drivers/net/wireless/rtlwifi/pci.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
@@ -198,7 +198,7 @@ static bool _rtl_pci_platform_switch_device_pci_aspm(}/*When we set 0x01 to enable clk request. Set 0x0 to disable clk req.*/-staticbool_rtl_pci_switch_clk_req(structieee80211_hw*hw,u8value)+staticvoid_rtl_pci_switch_clk_req(structieee80211_hw*hw,u8value){structrtl_pci*rtlpci=rtl_pcidev(rtl_pcipriv(hw));structrtl_hal*rtlhal=rtl_hal(rtl_priv(hw));
From: Larry Finger <hidden> Date: 2012-01-30 23:35:47
On 01/30/2012 06:46 AM, Devendra.Naga wrote:
From: "Devendra.Naga"<redacted>
the return value from _rtl_pci_switch_clk_req is not used by any of its callers.
Signed-off-by: Devendra.Naga<redacted>
---
drivers/net/wireless/rtlwifi/pci.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
The patch is OK, but the patch subject is bad. You should have "[PATCH]
rtlwifi:...". Your patch is for rtlwifi, not wireless.
Larry
@@ -198,7 +198,7 @@ static bool _rtl_pci_platform_switch_device_pci_aspm(}/*When we set 0x01 to enable clk request. Set 0x0 to disable clk req.*/-staticbool_rtl_pci_switch_clk_req(structieee80211_hw*hw,u8value)+staticvoid_rtl_pci_switch_clk_req(structieee80211_hw*hw,u8value){structrtl_pci*rtlpci=rtl_pcidev(rtl_pcipriv(hw));structrtl_hal*rtlhal=rtl_hal(rtl_priv(hw));
From: Joe Perches <joe@perches.com> Date: 2012-01-30 23:45:28
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
On Mon, Jan 30, 2012 at 6:45 PM, Joe Perches [off-list ref] wrote:
On Mon, 2012-01-30 at 17:35 -0600, Larry Finger wrote:
quoted
The patch is OK, but the patch subject is bad. You should have "[PATCH]
rtlwifi:...". Your patch is for rtlwifi, not wireless.
Will post a new patch, Thanks !!
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
Thanks a lot Joe, will follow your suggestions :).
Devendra.