From: Tillmann Heidsieck <theidsieck@leenox.de>
To: punit vara <punitvara@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Julia Lawall <Julia.Lawall@lip6.fr>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant on the right side of test
Date: Sun, 18 Oct 2015 20:54:57 +0200 [thread overview]
Message-ID: <c2a1fdfe0ad167e5923f7173031fb725@mail.leenox.de> (raw)
In-Reply-To: <CABXAfNJmFwrK-sXOWOXBm1qKQXwB4m06EY1tFP2ZjuOqSP8YDw@mail.gmail.com>
Hi,
On 2015-10-18 08:32, punit vara wrote:
> On Sat, Oct 17, 2015 at 10:46 AM, Greg KH <gregkh@linuxfoundation.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@gmail.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
next prev parent reply other threads:[~2015-10-18 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 18:25 [PATCH RESEND 0/4] Staging: rtl8712: Fix coding style warnings Punit Vara
2015-10-14 18:25 ` [PATCH RESEND 1/4] Staging: rtl8712: Fix warning prefer eth_broadcast_addr() over memset() Punit Vara
2015-10-14 18:25 ` [PATCH v2 2/4] Staging: rtl8712: Use ether_addr_equal() over memcmp() Punit Vara
2015-10-14 18:25 ` [PATCH RESEND 3/4] Staging: rtl8712: Coding style warnings fix for block comments Punit Vara
2015-10-14 18:25 ` [PATCH v2 4/4] Staging: rtl8712: fix warning for placing constant on the right side of test Punit Vara
2015-10-17 5:16 ` Greg KH
2015-10-18 6:32 ` punit vara
2015-10-18 18:54 ` Tillmann Heidsieck [this message]
2015-10-18 19:14 ` Tillmann Heidsieck
2015-10-19 2:00 ` Greg KH
2015-10-19 2:44 ` Larry Finger
2015-10-19 15:21 ` punit vara
2015-10-22 19:04 ` punit vara
2015-10-22 19:14 ` Greg KH
2015-10-22 19:22 ` Dan Carpenter
2015-10-22 20:03 ` punit vara
2015-10-22 20:34 ` Dan Carpenter
2015-10-24 7:11 ` punit vara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2a1fdfe0ad167e5923f7173031fb725@mail.leenox.de \
--to=theidsieck@leenox.de \
--cc=Julia.Lawall@lip6.fr \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=punitvara@gmail.com \
--cc=sudipm.mukherjee@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®