From: Greg KH <gregkh@linuxfoundation.org>
To: "Simon Sandström" <simon@nikanor.nu>
Cc: devel@driverdev.osuosl.org, linux@Wolf-Entwicklungen.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] staging: pi433: Split rf69_set_crc_enabled into two functions
Date: Thu, 7 Dec 2017 17:52:57 +0100 [thread overview]
Message-ID: <20171207165257.GB23902@kroah.com> (raw)
In-Reply-To: <20171207145801.pvi25ppkkygwofir@gamma.nikanor.nu>
On Thu, Dec 07, 2017 at 03:58:01PM +0100, Simon Sandström wrote:
> On Thu, Dec 07, 2017 at 03:38:57PM +0100, Greg KH wrote:
> > On Wed, Dec 06, 2017 at 09:42:19PM +0100, Simon Sandström wrote:
> > > Splits rf69_set_crc_enabled(dev, enabled) into
> > > rf69_enable_crc(dev) and rf69_disable_crc(dev).
> > >
> > > Signed-off-by: Simon Sandström <simon@nikanor.nu>
> > > ---
> > > drivers/staging/pi433/pi433_if.c | 22 ++++++++++++++++++++--
> > > drivers/staging/pi433/rf69.c | 18 ++++++------------
> > > drivers/staging/pi433/rf69.h | 4 ++--
> > > 3 files changed, 28 insertions(+), 16 deletions(-)
> >
> > This series did not apply at all.
> >
> > What tree and branch did you make it against?
> >
> > Please redo it against my staging.git tree, the staging-next branch
> > should be fine, or the staging-testing will work as well.
> >
> > thanks,
> >
> > greg k-h
>
> Hmm. Haven't you already applied these?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-testing&id=39252a4bcf63d9dbc168b9ef56eb4ca42e045b9d
>
> >patch "staging: pi433: Split rf69_set_crc_enabled into two functions" added to staging-testing
> >
> >This is a note to let you know that I've just added the patch titled
> >
> > staging: pi433: Split rf69_set_crc_enabled into two functions
> >
> > ...
Odd, I guess so, why did they end up in my mbox again? strange...
greg k-h
next prev parent reply other threads:[~2017-12-07 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 20:42 [PATCH 0/6] staging: pi433: Minor cleanup and style fixes Simon Sandström
2017-12-06 20:42 ` [PATCH 1/6] staging: pi433: Split rf69_set_crc_enabled into two functions Simon Sandström
2017-12-07 14:38 ` Greg KH
2017-12-07 14:58 ` Simon Sandström
2017-12-07 16:52 ` Greg KH [this message]
2017-12-06 20:42 ` [PATCH 2/6] staging: pi433: Split rf69_set_sync_enabled " Simon Sandström
2017-12-06 20:42 ` [PATCH 3/6] staging: pi433: Remove enum data_mode Simon Sandström
2017-12-06 20:42 ` [PATCH 4/6] staging: pi433: Combine all rf69_set_amplifier_x() Simon Sandström
2017-12-06 20:42 ` [PATCH 5/6] staging: pi433: Move enum option_on_off to pi433_if.h Simon Sandström
2017-12-06 22:24 ` Marcus Wolf
2017-12-07 6:14 ` Greg KH
2017-12-06 20:42 ` [PATCH 6/6] staging: pi433: Remove SET_CHECKED usage from pi433_probe Simon Sandström
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=20171207165257.GB23902@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@Wolf-Entwicklungen.de \
--cc=simon@nikanor.nu \
/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