From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Alaa Emad <alaaemadhossney.ae@gmail.com>,
Brad Love <brad@nextdimension.cc>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxim Plotnikov <wgh@torlan.ru>, Sean Young <sean@mess.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] media: sp8870: move it to staging
Date: Tue, 1 Jun 2021 06:50:54 +0200 [thread overview]
Message-ID: <YLW8rkDRNp1TdWqY@kroah.com> (raw)
In-Reply-To: <5e694bc1b0670b58b93a9fea5712ed0f306e6050.1622493461.git.mchehab+huawei@kernel.org>
On Mon, May 31, 2021 at 10:37:54PM +0200, Mauro Carvalho Chehab wrote:
> This driver is used only ba av7110, which is preparing for
> its retirement. So, move this ancillary driver to stay together
> with av7110.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> drivers/media/dvb-frontends/Kconfig | 12 -----------
> drivers/media/dvb-frontends/Makefile | 1 -
> drivers/staging/media/av7110/Kconfig | 20 +++++++++++++++++++
> drivers/staging/media/av7110/Makefile | 2 ++
> .../media/av7110}/sp8870.c | 0
> .../media/av7110}/sp8870.h | 0
> 6 files changed, 22 insertions(+), 13 deletions(-)
> rename drivers/{media/dvb-frontends => staging/media/av7110}/sp8870.c (100%)
> rename drivers/{media/dvb-frontends => staging/media/av7110}/sp8870.h (100%)
Don't you need a TODO file for these moves that says what is wrong with
the driver and when it will be removed and to not send cleanups for it?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-01 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 20:37 [PATCH] media: sp8870: move it to staging Mauro Carvalho Chehab
2021-06-01 4:50 ` Greg Kroah-Hartman [this message]
2021-06-01 8:28 ` Mauro Carvalho Chehab
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=YLW8rkDRNp1TdWqY@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alaaemadhossney.ae@gmail.com \
--cc=brad@nextdimension.cc \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=sean@mess.org \
--cc=wgh@torlan.ru \
/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