From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Adrien Thierry <athierry@redhat.com>,
Maxime Ripard <mripard@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] staging: bcm2835-audio: delete TODO
Date: Fri, 22 Apr 2022 17:13:11 +0200 [thread overview]
Message-ID: <YmLGB8bhHs8cRFVM@kroah.com> (raw)
In-Reply-To: <97917592-6e11-dd82-3f41-893da6b15f6a@i2se.com>
On Fri, Apr 22, 2022 at 04:58:22PM +0200, Stefan Wahren wrote:
> Hi Greg,
>
> Am 22.04.22 um 16:40 schrieb Greg Kroah-Hartman:
> > On Wed, Apr 20, 2022 at 01:44:00PM -0400, Adrien Thierry wrote:
> > > Delete TODO since all tasks were completed:
> > >
> > > 1 - fixed here:
> > > https://lore.kernel.org/all/20220408150359.26661-1-athierry@redhat.com/
> > >
> > > 2 - there are no remaining checkpatch.pl errors or warnings
> > >
> > > Signed-off-by: Adrien Thierry <athierry@redhat.com>
> > > ---
> > > drivers/staging/vc04_services/bcm2835-audio/TODO | 10 ----------
> > > 1 file changed, 10 deletions(-)
> > > delete mode 100644 drivers/staging/vc04_services/bcm2835-audio/TODO
> > >
> > > diff --git a/drivers/staging/vc04_services/bcm2835-audio/TODO b/drivers/staging/vc04_services/bcm2835-audio/TODO
> > > deleted file mode 100644
> > > index b85451255db0..000000000000
> > > --- a/drivers/staging/vc04_services/bcm2835-audio/TODO
> > > +++ /dev/null
> > > @@ -1,10 +0,0 @@
> > > -*****************************************************************************
> > > -* *
> > > -* TODO: BCM2835-AUDIO *
> > > -* *
> > > -*****************************************************************************
> > > -
> > > -1) Revisit multi-cards options and PCM route mixer control (as per comment
> > > -https://lore.kernel.org/lkml/s5hd0to5598.wl-tiwai@suse.de)
> > > -
> > > -2) Fix the remaining checkpatch.pl errors and warnings.
> > > --
> > > 2.35.1
> > >
> > >
> > Great, so now it can be merged to the real part of the kernel? If not,
> > what's left for that to happen?
>
> bcm2835-audio depends on interface/vchiq_arm in a parallel directory. Its
> TODO list is a little bit longer.
Ah, yeah, still more work to do :(
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-04-22 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:44 [PATCH] staging: bcm2835-audio: delete TODO Adrien Thierry
2022-04-22 14:40 ` Greg Kroah-Hartman
2022-04-22 14:58 ` Stefan Wahren
2022-04-22 15:13 ` 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=YmLGB8bhHs8cRFVM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=athierry@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=nsaenz@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).