Linux Input/HID development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Aveline Noir <jm5905938@gmail.com>
Cc: linux-input@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 2/2] HID: picolcd: Avoid framebuffer last-close deadlock
Date: Wed, 18 Nov 2026 22:13:55 +0100	[thread overview]
Message-ID: <f52cd9ed-4e23-4160-b305-650d853bc18b@gmx.de> (raw)
In-Reply-To: <179308935900.645289.17780178981863221787@gmail.com>

Jiri & Benjamin, can you check and decide on patch #1 of this series ?

Thanks!
Helge

On 10/27/26 09:22, Aveline Noir wrote:
> On Sun, 25 Oct 2026 09:20:36 +0100, Helge Deller wrote:
>> For this patch:
>> Acked-by: Helge Deller <deller@gmx.de> # fbdev
> 
> Thanks for the ack!
> 
>> I'm not sure about how to handle this patch series at all.
>> There is still a review missing for patch #1.
>> Shall I take this patch (#2 of 2) via fbdev git tree?
> 
> Since patch #2 depends on patch #1, I think it would make sense
> to keep both patches together, perhaps through the HID tree.
> 
> Jiri, Benjamin, could you take a look at patch #1 and let us
> know how you'd prefer to handle the series?
> 
> Thanks,
> Aveline


  reply	other threads:[~2026-11-18 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 16:15 [PATCH v2 0/2] HID: picolcd: Fix output-request and framebuffer locking Aveline Noir
2026-09-28 16:17 ` [PATCH v2 1/2] HID: picolcd: Move output requests out of spinlocked sections Aveline Noir
2026-09-28 16:17 ` [PATCH v2 2/2] HID: picolcd: Avoid framebuffer last-close deadlock Aveline Noir
2026-10-25  8:20   ` Helge Deller
2026-10-27  8:22     ` Aveline Noir
2026-11-18 21:13       ` Helge Deller [this message]
2026-10-14 11:06 ` [PATCH v2 0/2] HID: picolcd: Fix output-request and framebuffer locking Aveline Noir

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=f52cd9ed-4e23-4160-b305-650d853bc18b@gmx.de \
    --to=deller@gmx.de \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=jm5905938@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox