All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] media: flexcop-usb: probe cleanups
Date: Mon, 25 Jul 2022 13:23:18 +0200	[thread overview]
Message-ID: <Yt59Jv6PWPHQEuJR@hovoldconsulting.com> (raw)
In-Reply-To: <YsvyXJ2a0ILnB+vu@hovoldconsulting.com>

On Mon, Jul 11, 2022 at 11:50:20AM +0200, Johan Hovold wrote:
> On Thu, Jun 09, 2022 at 04:26:02PM +0200, Johan Hovold wrote:
> > This series cleans up the probe helper functions a bit to make the code
> > more readable.
> > 
> > Note that these apply on top of the fix posted here:
> > 
> > 	https://lore.kernel.org/all/20220609135341.19941-1-johan@kernel.org/
> 
> > Johan Hovold (3):
> >   media: flexcop-usb: clean up endpoint sanity checks
> >   media: flexcop-usb: clean up URB initialisation
> >   media: flexcop-usb: use usb_endpoint_maxp()
> 
> I haven't received any notification about this series being added to any
> tree and the status is still set to "NEW" in the patch tracker so
> sending a reminder.

Another two weeks without a reply so sending another reminder.

Any chance of getting these (and the separate fix) into 5.20?

> >  drivers/media/usb/b2c2/flexcop-usb.c | 22 ++++++++++++++--------
> >  1 file changed, 14 insertions(+), 8 deletions(-)

Johan

      reply	other threads:[~2022-07-25 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 14:26 [PATCH 0/3] media: flexcop-usb: probe cleanups Johan Hovold
2022-06-09 14:26 ` [PATCH 1/3] media: flexcop-usb: clean up endpoint sanity checks Johan Hovold
2022-06-09 14:26 ` [PATCH 2/3] media: flexcop-usb: clean up URB initialisation Johan Hovold
2022-06-09 14:26 ` [PATCH 3/3] media: flexcop-usb: use usb_endpoint_maxp() Johan Hovold
2022-07-11  9:50 ` [PATCH 0/3] media: flexcop-usb: probe cleanups Johan Hovold
2022-07-25 11:23   ` Johan Hovold [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=Yt59Jv6PWPHQEuJR@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 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.