From: Greg KH <gregkh@linuxfoundation.org>
To: Sohom Bhattacharjee <soham.bhattacharjee15@gmail.com>
Cc: devel@driverdev.osuosl.org, Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>, Ray Jui <rjui@broadcom.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradeed.org,
bcm-kernel-feedback-list@broadcom.com,
Hannes Reinecke <hare@suse.de>,
Nicholas Mc Guire <hofrat@osadl.org>,
Joe Perches <joe@perches.com>, RonitHalder <ronit.crj@gmail.com>,
James Bottomley <JBottomley@Odin.org>
Subject: Re: [PATCH] staging: rts5208: coding style clean-ups
Date: Mon, 21 Mar 2016 22:25:08 -0400 [thread overview]
Message-ID: <20160322022508.GA18726@kroah.com> (raw)
In-Reply-To: <20160322021525.GA3293@sam>
On Tue, Mar 22, 2016 at 07:45:25AM +0530, Sohom Bhattacharjee wrote:
> On Mon, Mar 21, 2016 at 05:29:24PM -0400, Greg KH wrote:
> > On Mon, Mar 21, 2016 at 10:53:36PM +0530, Sohom Bhattacharjee wrote:
> > > fixed *only* comments that did not follow kernel coding style.
> > > the errors were caught by the checkpatch.pl tool
> > >
> > > Signed-off-by: Sohom Bhattacharjee <soham.bhattacharjee15@gmail.com>
> >
> > Does not apply to the tree at all :(
> what do you mean ?
> i used the Linus's latest git tree. :)
That's usually quite a bit behind the current development tree. Always
use linux-next to work against, you can miss almost 3 months of
development effort at times.
thanks,
greg k-h
prev parent reply other threads:[~2016-03-22 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 17:23 [PATCH] staging: rts5208: coding style clean-ups Sohom Bhattacharjee
2016-03-21 21:29 ` Greg KH
2016-03-22 2:15 ` Sohom Bhattacharjee
2016-03-22 2:25 ` Greg KH [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=20160322022508.GA18726@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=JBottomley@Odin.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=hare@suse.de \
--cc=hofrat@osadl.org \
--cc=joe@perches.com \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradeed.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=ronit.crj@gmail.com \
--cc=sbranden@broadcom.com \
--cc=soham.bhattacharjee15@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.