linux-kernel - Re: [PATCH v4 14/15] net: wireless: ath: Remove unneeded variable ret returning 0

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] [day] [month] [year] [list]

Message-ID: <CABXAfNJf5dBNx-F=6O0SsBRE3jtasK-=1-2FFb_KNDvb+hrR_g@mail.gmail.com>
Date:	Wed, 28 Oct 2015 00:39:53 +0530
From:	punit vara <punitvara@...il.com>
To:	Kalle Valo <kvalo@...eaurora.org>
Cc:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>,
	jirislaby@...il.com, Nick Kossifidis <mickflemm@...il.com>,
	mcgrof@...not-panic.com, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 14/15] net: wireless: ath: Remove unneeded variable ret
 returning 0

On Tue, Oct 27, 2015 at 1:42 PM, Kalle Valo <kvalo@...eaurora.org> wrote:
> punit vara <punitvara@...il.com> writes:
>
>> Will my other patches which are already correct be added to wireless
>> tree ? or I have to resend everything ?
>
> Yes, please resend the whole patchset. I don't apply patches
> individually from a patchset, it's just too time consuming and error
> prone.
>
> Also, as you seem to be new here, I don't recommend sending big
> patchsets in the beginning. Start slow, send just few a patch or two at
> a time, and once you gain more experience send bigger patchsets.
>
> --
> Kalle Valo
Next time I will send 2-3 patches only . This time I have resent you
all the patches that I have created before . Thank you for suggestion.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/