Linux Input/HID development
 help / color / mirror / Atom feed
From: Aveline Noir <jm5905938@gmail.com>
To: Helge Deller <deller@gmx.de>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	linux-input@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 2/2] HID: picolcd: Avoid framebuffer last-close deadlock
Date: Tue, 27 Oct 2026 01:22:46 -0700 (PDT)	[thread overview]
Message-ID: <179308935900.645289.17780178981863221787@gmail.com> (raw)
In-Reply-To: <76cddcc5-2cf8-40da-9139-e78353975e41@gmx.de>

Hi Helge,

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-10-27  8:22 UTC|newest]

Thread overview: 6+ 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 [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=179308935900.645289.17780178981863221787@gmail.com \
    --to=jm5905938@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=deller@gmx.de \
    --cc=jikos@kernel.org \
    --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