linux-kernel - Re: [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant on the right side of test

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: <c2a1fdfe0ad167e5923f7173031fb725@mail.leenox.de>
Date:	Sun, 18 Oct 2015 20:54:57 +0200
From:	Tillmann Heidsieck <theidsieck@...nox.de>
To:	punit vara <punitvara@...il.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org, Julia Lawall <Julia.Lawall@...6.fr>,
	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	Larry Finger <Larry.Finger@...inger.net>,
	linux-kernel-owner@...r.kernel.org
Subject: Re: [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant
 on the right side of test

Hi,

On 2015-10-18 08:32, punit vara wrote:
> On Sat, Oct 17, 2015 at 10:46 AM, Greg KH <gregkh@...uxfoundation.org> 
> wrote:
>> On Wed, Oct 14, 2015 at 11:55:55PM +0530, Punit Vara wrote:
>>> Put constant on the right side of a test.Problem found using 
>>> checkpatch:
>>> 
>>> Warning:Comparisons should place the constant on the right side of 
>>> the test
>>> 
>>> Signed-off-by: Punit Vara <punitvara@...il.com>
>>> ---
>>>  drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 16 ++++++++--------
>>>  1 file changed, 8 insertions(+), 8 deletions(-)
>> 
>> Didn't apply to my tree :(
> In this case what should I do ? Should I do git reset , git pull and
> then  do changes on latest tree ?
> 

Greg is probably trying to apply this series to the staging-next branch 
of his staging tree[0]
so you need to clone that one, or add it as an additional remote[1] to 
your clone of the kernel tree (much better option IMHO). After this you 
need to rebase[2] your changes onto the stating-next branch, fix up all 
conflicts in your code, and resend the patch.

I hope this helps

Tillmann

[0] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
[1] https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes
[2] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
--
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/