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: Thu, 24 Sep 2015 09:55:17 +0530 [thread overview]
Message-ID: <20150924042517.GA20187@sudip-pc> (raw)
In-Reply-To: <CABXAfN+n2CR4wDu_+GwPEBta9soYObOdY2m1oJAJe6AypuRgXA@mail.gmail.com>
On Wed, Sep 23, 2015 at 11:22:09PM +0530, punit vara wrote:
> On Wed, Sep 23, 2015 at 10:25 PM, punit vara <punitvara@gmail.com> wrote:
> > Thank you very much sir I will definitely follow that. I have seen so
> > many people fixing patches over here. Now I know process of submitting
> > patches.I am able to fix several patches created by checkpatch.pl .
> > But can you suggest me any driver to fix API or another small TODO
> > task. I have seen so many TODO but confuse where to start . Can you
> > give me some initial idea or though or any driver to fix bugs ? :-)
>
>
> Dear Sudip sir,
>
> I have used git format-patch master..my_local_branch But It also
> produce numbers in subject of patch.
> Now I have used git format-patch master..my_local_branch -N ..It does
> not generate any number in patch even if you have previous patches
Usually I will not diff between the master and my local branch. I will
sync my local branch with the master in the morning and commit my
changes there. Now while generating the patch if I want to generate my
last patch then I just use git format-patch -1. If you want last 2
patches then use git format-patch -2. If you want to have them in series
with the numbering in the subject use git format-patch -2 -n.
And please dont use "sir".
regards
sudip
next prev parent reply other threads:[~2015-09-24 4:25 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
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 [this message]
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=20150924042517.GA20187@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 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.