From: Julia Lawall <julia.lawall@lip6.fr>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] Re: [PATCH v2 3/3] staging: rtl8192u: Prefer using the BIT macro
Date: Fri, 24 Feb 2017 21:46:07 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702242145060.2152@hadrien> (raw)
In-Reply-To: <e1cde734-003d-4b3d-bba0-d37f5edd8e2b@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
On Fri, 24 Feb 2017, SIMRAN SINGHAL wrote:
>
>
> On Friday, February 24, 2017 at 10:46:21 PM UTC+5:30, gregkh wrote:
> On Fri, Feb 17, 2017 at 11:20:59PM +0530, simran singhal wrote:
> > Replaces left shift operation (1 << d) by BIT(x) macro.
> >
> > Fix the checkpatch.pl issue:
> > CHECK: Prefer using the BIT macro replacing
> >
> > Signed-off-by: simran singhal <singhal...@gmail.com>
> > ---
> >
> > V2:
> > -modified patch message.
> >
> > drivers/staging/rtl8192u/ieee80211/ieee80211.h | 140
> ++++++++++++-------------
> > 1 file changed, 70 insertions(+), 70 deletions(-)
>
> The last chunk of this patch did not apply, please fix up and
> resend.
>
> thanks,
>
> greg k-h
>
>
> Can you please elaborate what's the problem with the last chunk of this
> patch and
> to be more precise what do you mean by "last chunk of this patch". I am
> not getting
> what's the problem with this patch.
I would say "hunk" rather than "chunk", but he probably means the code
from the last @@ @@ to the end.
The best thing is to just pull the most recent version of the kernel and
see what happens when you try to apply your patch.
julia
next prev parent reply other threads:[~2017-02-24 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 17:50 simran singhal
2017-02-24 17:16 ` Greg KH
[not found] ` <e1cde734-003d-4b3d-bba0-d37f5edd8e2b@googlegroups.com>
2017-02-24 20:46 ` Julia Lawall [this message]
2017-02-25 7:54 ` [Outreachy kernel] " Greg KH
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=alpine.DEB.2.20.1702242145060.2152@hadrien \
--to=julia.lawall@lip6.fr \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=singhalsimran0@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
Powered by JetHome