From: Greg KH <gregkh@linuxfoundation.org>
To: Ioana Ciornei <ciorneiioana@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: wil1000: fix misspelled words
Date: Wed, 30 Sep 2015 12:29:49 +0200 [thread overview]
Message-ID: <20150930102949.GA15101@kroah.com> (raw)
In-Reply-To: <CAHWJYFkFhEBVCKFBm6rmtd0j4077QewS8mj-txCxowp5RTHa_w@mail.gmail.com>
On Wed, Sep 30, 2015 at 01:21:53PM +0300, Ioana Ciornei wrote:
> On Wed, Sep 30, 2015 at 5:00 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Sep 30, 2015 at 03:17:06AM +0300, Ioana Ciornei wrote:
> > > Fix misspelled words throughout the entire subsystem
> > >
> > > Signed-off-by: Ioana Ciornei <ciorneiioana@gmail.com>
> > > ---
> > > drivers/staging/wilc1000/coreconfigurator.c | 2 +-
> > > drivers/staging/wilc1000/host_interface.c | 26 +++++++++++------------
> > > drivers/staging/wilc1000/host_interface.h | 8 +++----
> > > drivers/staging/wilc1000/linux_mon.c | 2 +-
> > > drivers/staging/wilc1000/linux_wlan.c | 18 ++++++++--------
> > > drivers/staging/wilc1000/wilc_msgqueue.c | 2 +-
> > > drivers/staging/wilc1000/wilc_msgqueue.h | 8 +++----
> > > drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 22 +++++++++----------
> > > drivers/staging/wilc1000/wilc_wfi_cfgoperations.h | 4 ++--
> > > drivers/staging/wilc1000/wilc_wlan.c | 4 ++--
> > > 10 files changed, 48 insertions(+), 48 deletions(-)
> >
> > This patch doesn't apply to my staging-testing branch at all, due to
> > other changes that happened in the past few days with this driver.
> > Please refresh your tree and rebase your patch and resend it so that I
> > can apply it.
>
> Just to be sure.. are we supposed to keep track and apply patches on
> top of the staging-testing or staging-next branch?
> In the tutorials it appears staging-next to be the one to follow.
staging-testing usually only diverges from staging-next for less than 24
hours, so usually working on staging-next is fine to do. Except when
you are working on a driver, like this one, that is also being worked on
by other developers. For that, I recommend using staging-testing.
But note, this driver is averaging 10-20 patches every few days from
other developers, things are changing quickly in it, keeping up to date
and slip your patch in while that happens is going to be tricky. Expect
to have to rebase it a few times because of this, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-30 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 0:17 [PATCH] staging: wil1000: fix misspelled words Ioana Ciornei
2015-09-30 2:00 ` [Outreachy kernel] " Greg KH
2015-09-30 10:21 ` Ioana Ciornei
2015-09-30 10:26 ` Sudip Mukherjee
2015-09-30 10:29 ` Greg KH [this message]
2015-09-30 19:37 ` Ioana Ciornei
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=20150930102949.GA15101@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ciorneiioana@gmail.com \
--cc=outreachy-kernel@googlegroups.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.