From: Ronit Halder <ronit.crj@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: johnny.kim@atmel.com, rachel.kim@atmel.com,
linux-wireless@vger.kernel.org, chris.park@atmel.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
tony.cho@atmel.com, leo.kim@atmel.com
Subject: Re: [PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero
Date: Thu, 17 Sep 2015 09:09:35 +0530 [thread overview]
Message-ID: <1442461175.13630.20.camel@roni-HP> (raw)
In-Reply-To: <20150917031541.GA8579@kroah.com>
On Wed, 2015-09-16 at 20:15 -0700, Greg KH wrote:
> On Thu, Sep 17, 2015 at 08:28:52AM +0530, roni wrote:
> > Sorry for the ambiguity.
> > I am talking about my second patch in the series.
> > https://lkml.org/lkml/2015/9/15/293
> >
> > > > None of the line edited in first patch haven't changed after that.
> >
> > You applied the version 1 of the first patch in the series
> > https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/commit/?h=staging-testing&id=0e04f3f381c6a3ab3a7ef0ec9ded709e95996527
> >
> > Since then those lines I changed in the patch mentioned above haven't
> > changed.
> >
> > Why my second patch in this series doesn't apply?
>
> I don't remember, that was many hundreds of patches ago, sorry. Try it
> yourself to see if I messed up. Perhaps someone else had already sent
> in that same change before you did?
git-apply shows no error if I apply second patch on
staging/staging-testing.
regards
next prev parent reply other threads:[~2015-09-17 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 9:34 [PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero Ronit Halder
2015-09-15 9:38 ` [PATCH 2/2] Staging: wilc1000: fix NULL comparison style Ronit Halder
2015-09-15 13:54 ` [PATCH v2 1/2] Staging: wilc1000: Use NULL instead of zero Greg KH
2015-09-17 1:43 ` Ronit Halder
2015-09-17 2:22 ` Greg KH
2015-09-17 2:58 ` roni
2015-09-17 3:15 ` Greg KH
2015-09-17 3:39 ` Ronit Halder [this message]
2015-09-17 6:53 ` Sudip Mukherjee
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=1442461175.13630.20.camel@roni-HP \
--to=ronit.crj@gmail.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=leo.kim@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rachel.kim@atmel.com \
--cc=tony.cho@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.