All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: stable@vger.kernel.org, linux-media@vger.kernel.org,
	laurent.pinchart@ideasonboard.com, hansg@kernel.org,
	mchehab@kernel.org, Jay Chooi <jay@robocurve.org>
Subject: Re: uvcvideo: deadlock when async control drops the last PM reference from the status-event path
Date: Fri, 17 Jul 2026 09:27:49 +0200	[thread overview]
Message-ID: <2026071747-exposure-owl-c4f0@gregkh> (raw)
In-Reply-To: <CANiDSCs9T2iDaptLnv4g1ZxNyRQqTzNCD=Ay2uRQoPeSaGv+GQ@mail.gmail.com>

On Fri, Jul 17, 2026 at 09:07:12AM +0200, Ricardo Ribalda wrote:
> Hi Greg
> 
> No worries, thanks for the update.
> 
> Is there a public page where we can see the status of patches
> (queued/rejected) so we do not have to bother you?

Nope, not really, that would take more effort to set up and maintain
that it would be to just keep the mboxes locally as I currently do :)

And normally we do stay on top, this summer it's been a bit harder due
to massive conference travel combined with massive amounts of patches
being tagged for this -rc1 window.

thanks,

greg k-h

      reply	other threads:[~2026-07-17  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16  7:16 uvcvideo: deadlock when async control drops the last PM reference from the status-event path Jay Chooi
2026-07-16  7:26 ` Ricardo Ribalda
2026-07-17  1:58   ` Jay Chooi
2026-07-17  6:54     ` Ricardo Ribalda
2026-07-17  7:05       ` Greg KH
2026-07-17  7:07         ` Ricardo Ribalda
2026-07-17  7:27           ` Greg KH [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=2026071747-exposure-owl-c4f0@gregkh \
    --to=greg@kroah.com \
    --cc=hansg@kernel.org \
    --cc=jay@robocurve.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ribalda@chromium.org \
    --cc=stable@vger.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.