From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marcin Ciupak <marcin.s.ciupak@gmail.com>
Cc: Joe Perches <joe@perches.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v4] staging: nrf24: add new driver for 2.4GHz radio transceiver
Date: Sat, 23 Feb 2019 09:00:17 +0100 [thread overview]
Message-ID: <20190223080017.GC2640@kroah.com> (raw)
In-Reply-To: <20190222202055.udjbsm5qkxzkqcdh@metis.ciupak.eu>
On Fri, Feb 22, 2019 at 09:20:56PM +0100, Marcin Ciupak wrote:
> On Tue, Feb 19, 2019 at 11:20:10AM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Feb 13, 2019 at 08:40:35PM +0100, Marcin Ciupak wrote:
> > > This patch adds driver for Nordic Semiconductor nRF24L01+ radio
> > > transceiver.
> > >
> > > Signed-off-by: Marcin Ciupak <marcin.s.ciupak@gmail.com>
> > > ---
> > > Changes in v2:
> > > - add terminating newlines to all logging formats
> > > Changes in v3:
> > > - patch subject
> > > - comments cleanup
> > > - goto labels cleanup
> > > - scnprintf bugfix
> > > - ida_simple_remove bugfix
> > > Changes in v4:
> > > - fix smatch warnings
> >
> > What is preventing this from being merged today with the normal
> > subsystem for this type of drivers? Why does this have to go into
> > staging?
> >
> > thanks,
> >
> > greg k-h
>
> As per TODO file:
> +Todo:
> +- opening and closing pipes via sysfs
That's not what sysfs is for, so that can't be a TODO item :)
> +- improve switching in between RX and TX
> +- improve handling of MAX_RT interrupt
That's just logic cleanup, no reason to have it in staging.
> +- find and fix bugs
Same here.
> +- code cleanup
What specifically do you mean by this? And why can't you just spend a
day and do it now?
>
> Additionally, I would like to add ioctl (or any similar) interface
> as configuration via sysfs is not very efficent in here.
sysfs is not for configuration, that is what configfs is for, please use
that instead.
> My beliefes are that this driver needs some time in staging, but I might
> be wrong and if you believe otherwise just let me know and I will try to
> push it ti regular sybsystem.
I think you need to use the standard apis that the kernel has for
drivers like this (v4l?) and work on getting the driver into the proper
subsystem first. I don't see what the goal of getting it into staging
is going to do to help you out with that.
thanks,
greg k-h
prev parent reply other threads:[~2019-02-23 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 19:40 [PATCH v4] staging: nrf24: add new driver for 2.4GHz radio transceiver Marcin Ciupak
2019-02-19 10:20 ` Greg Kroah-Hartman
2019-02-22 20:20 ` Marcin Ciupak
2019-02-23 8:00 ` Greg Kroah-Hartman [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=20190223080017.GC2640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.s.ciupak@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.