From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Bogicevic Sasa <brutallesale@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drivers:staging:gdm724x Fill all alignment should match open parentheses
Date: Fri, 30 Oct 2015 17:42:58 +0530 [thread overview]
Message-ID: <20151030121258.GA22698@sudip-pc> (raw)
In-Reply-To: <20151030120508.GB13155@gmail.com>
On Fri, Oct 30, 2015 at 01:05:08PM +0100, Bogicevic Sasa wrote:
> On 10/30/2015, Sudip Mukherjee wrote:
> >On Fri, Oct 30, 2015 at 12:48:09PM +0100, Bogicevic Sasa wrote:
> >>On 10/30/2015, Sudip Mukherjee wrote:
> >>>On Fri, Oct 30, 2015 at 09:59:19AM +0100, Bogicevic Sasa wrote:
> >>>>On 10/30/2015, Sudip Mukherjee wrote:
> >>>>>On Thu, Oct 29, 2015 at 09:15:01PM +0100, Bogicevic Sasa wrote:
> ><snip>
> >>
> >>Ah so that might be the catch I didnt use the -n option while creating
> >>patches. Thanks for your help
> >
> >No, -n is for numbered output. You can try -N
> >see man git-format-patch for more details.
> >
> >regards
>
> Will do thanks. Can you tell me what kernel tree to pull for my start of
> development work. Untill now I just pulled latest stable is this correct
> ?
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
No, use staging-testing branch of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
regards
sudip
prev parent reply other threads:[~2015-10-30 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:15 [PATCH 2/2] drivers:staging:gdm724x Fill all alignment should match open parentheses Bogicevic Sasa
2015-10-30 7:31 ` Sudip Mukherjee
2015-10-30 8:59 ` Bogicevic Sasa
2015-10-30 9:36 ` Sudip Mukherjee
2015-10-30 11:48 ` Bogicevic Sasa
2015-10-30 11:55 ` Sudip Mukherjee
2015-10-30 12:05 ` Bogicevic Sasa
2015-10-30 12:12 ` Sudip Mukherjee [this message]
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=20151030121258.GA22698@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=brutallesale@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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