From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: punit vara <punitvara@gmail.com>
Cc: Jaime Arrocha <jarr@innercoder.com>,
Larry.Finger@lwfinger.net, devel@driverdev.osuosl.org,
Flo Schil <florian.c.schilhabel@googlemail.com>,
linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 13/13] Staging: rtl8712: Coding style warning fix for block comment
Date: Wed, 23 Sep 2015 21:04:44 +0530 [thread overview]
Message-ID: <20150923153443.GA13153@sudip-pc> (raw)
In-Reply-To: <CABXAfNLEu4qJsmvjR=SFu5=3fX6P4t4qeF7KQBepjDXuTZUzwA@mail.gmail.com>
On Wed, Sep 23, 2015 at 07:32:52PM +0530, punit vara wrote:
> On Wed, Sep 23, 2015 at 12:55 PM, Jaime Arrocha <jarr@innercoder.com> wrote:
> >
> > On 09/23/2015 12:31 AM, Sudip Mukherjee wrote:
> >>
> >> On Wed, Sep 23, 2015 at 02:03:56AM +0530, Punit Vara wrote:
<snip>
>
>
> It would be better if someone suggest me how to create independent
> patch when already I have few patches in directory . Or is it
> necessary to clear directory every time whenever we work on new
> problems ?
I think I have already told you how to use git format-patch to generate
single patch when you mailed me offlist.
regards
sudip
next prev parent reply other threads:[~2015-09-23 15:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 20:33 [PATCH 13/13] Staging: rtl8712: Coding style warning fix for block comment Punit Vara
2015-09-23 5:31 ` Sudip Mukherjee
2015-09-23 7:25 ` Jaime Arrocha
2015-09-23 14:02 ` punit vara
2015-09-23 15:34 ` Sudip Mukherjee [this message]
2015-09-23 16:21 ` punit vara
2015-09-23 16:33 ` Sudip Mukherjee
2015-09-23 16:55 ` punit vara
2015-09-23 17:52 ` punit vara
2015-09-24 4:25 ` Sudip Mukherjee
2015-09-24 16:36 ` 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=20150923153443.GA13153@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarr@innercoder.com \
--cc=linux-kernel@vger.kernel.org \
--cc=punitvara@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