From: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>
To: Info <info@ministro.hu>
Cc: 'Rob Herring' <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: silabs si4455 serial driver
Date: Wed, 9 Dec 2020 13:02:22 +0100 [thread overview]
Message-ID: <X9C8zlCMvTev7ELE@kroah.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAM7AkQxKEJRHh2BgMNSTrQkBAExvbAW64DNBoXXP8CRioZMAAAAzfOEAABAAAAAJUqiRO33GQqGIHffCVyG/AQAAAAA=@ministro.hu>
On Wed, Dec 09, 2020 at 12:09:58PM +0100, Info wrote:
> This is a serial port driver for
> Silicon Labs Si4455 Sub-GHz transciver.
>
> Signed-off-by: József Horváth <info@ministro.hu>
Note, your From: line does not match this line, so I can't take this.
But:
> ---
> .../bindings/staging/serial/silabs,si4455.txt | 39 +
staging drivers need to be self-contained, so this should be here. It
needs to be reviewed by the DT maintainers when moving out of staging.
> index 000000000000..aee5c7613b31
> --- /dev/null
> +++ b/drivers/staging/si4455/TODO
> @@ -0,0 +1,3 @@
> +TODO:
> + - add variable packet length support
> + - add firmware patching support in case of Si4455-C2A
Why are these a requirement to get it out of staging? Why go into
staging at all? Why not go into the 'real' part of the kernel directly?
What is keeping that from happening today?
These look like new features that you can add later, and shouldn't be a
requirement for acceptance into the normal part of the kernel for this
driver. Why have you not tried doing that first?
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-09 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 11:09 [PATCH] Staging: silabs si4455 serial driver Info
2020-12-09 12:02 ` 'Greg Kroah-Hartman' [this message]
2020-12-09 12:57 ` ***UNCHECKED*** " Info
2020-12-09 12:42 ` Dan Carpenter
2020-12-09 18:56 ` József Horváth
2020-12-09 18:59 ` Dan Carpenter
2020-12-09 17:38 ` Jérôme Pouiller
2020-12-09 19:41 ` József Horváth
2020-12-10 8:00 ` Dan Carpenter
2020-12-10 3:06 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 12:20 József Horváth
2020-12-10 12:55 ` 'Greg Kroah-Hartman'
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=X9C8zlCMvTev7ELE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=info@ministro.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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