From: Greg KH <gregkh@linuxfoundation.org>
To: Derek Robson <robsonde@gmail.com>
Cc: wsa@the-dreams.de, karniksayli1995@gmail.com,
nrosbrook@mail.smcvt.edu, elfring@users.sourceforge.net,
mattkilgore12@gmail.com, shiva@exdev.nl, bhumirks@gmail.com,
sabitha.george@gmail.com, punitvara@gmail.com,
weiyongjun1@huawei.com, georgiana.chelu93@gmail.com,
goudapatilk@gmail.com, mihaela.muraru21@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ks7010 - fixed style block comments
Date: Tue, 21 Mar 2017 19:45:51 +0100 [thread overview]
Message-ID: <20170321184551.GA25484@kroah.com> (raw)
In-Reply-To: <20170321182950.GA7902@bigbird>
On Wed, Mar 22, 2017 at 07:29:50AM +1300, Derek Robson wrote:
> On Tue, Mar 21, 2017 at 08:56:25AM +0100, Greg KH wrote:
> > On Sun, Mar 19, 2017 at 01:07:17PM +1300, Derek Robson wrote:
> > > Fixed style of all block comments across whole driver
> > > Found by checkpatch
> > >
> > > Signed-off-by: Derek Robson <robsonde@gmail.com>
> > > ---
> > > drivers/staging/ks7010/ks7010_sdio.c | 3 ++-
> > > drivers/staging/ks7010/ks_hostif.h | 35 +++++++++++++++++++++---------
> > > drivers/staging/ks7010/ks_wlan.h | 3 ++-
> > > drivers/staging/ks7010/ks_wlan_net.c | 41 +++++++++++++++++++++++-------------
> > > 4 files changed, 55 insertions(+), 27 deletions(-)
> >
> > This patch doesn't apply to my tree at all :(
> >
>
> Am I working from the right/best tree for driver/staging?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
What branch did you use? You should use staging-next, or worse case,
staging-testing. Don't use 'master', as that tracks Linus's tree and is
usually quite old.
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-21 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 0:07 [PATCH] Staging: ks7010 - fixed style block comments Derek Robson
2017-03-21 7:56 ` Greg KH
2017-03-21 18:29 ` Derek Robson
2017-03-21 18:45 ` Greg KH [this message]
2017-03-21 23:34 ` Tobin C. Harding
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=20170321184551.GA25484@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhumirks@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=elfring@users.sourceforge.net \
--cc=georgiana.chelu93@gmail.com \
--cc=goudapatilk@gmail.com \
--cc=karniksayli1995@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattkilgore12@gmail.com \
--cc=mihaela.muraru21@gmail.com \
--cc=nrosbrook@mail.smcvt.edu \
--cc=punitvara@gmail.com \
--cc=robsonde@gmail.com \
--cc=sabitha.george@gmail.com \
--cc=shiva@exdev.nl \
--cc=weiyongjun1@huawei.com \
--cc=wsa@the-dreams.de \
/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.