All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
Cc: Hans de Goede <hansg@kernel.org>,
	linux-input@vger.kernel.org,  linux-kernel@vger.kernel.org,
	zhanjun@uniontech.com, niecheng1@uniontech.com,
	 Mingcong Bai <jeffbai@aosc.io>,
	Kexy Biscuit <kexybiscuit@aosc.io>,
	kernel@uniontech.com,  Hongfei Ren <lcrhf@outlook.com>,
	stable@kernel.org
Subject: Re: [PATCH] Input: atkbd - skip deactivate for HONOR BCC-N's internal keyboard
Date: Sat, 6 Jun 2026 14:01:40 -0700	[thread overview]
Message-ID: <aiSKsQCKmRh_FuzS@google.com> (raw)
In-Reply-To: <20260605-honor-v1-1-78e05e491193@linux.dev>

On Fri, Jun 05, 2026 at 03:27:21PM +0800, Cryolitia PukNgae wrote:
> After commit 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61 ("Input: atkbd -
> do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID"), HONOR
> BCC-N, aka HONOR MagicBook 14 2026's internal keyboard stops
> working. Adding the atkbd_deactivate_fixup quirk fixes it.
> 
> DMI: HONOR BCC-N/BCC-N-PCB, BIOS 1.04 04/07/2026
> 
> Fixes: 9cf6e24c9fbf17e52de9fff07f12be7565ea6d61 ("Input: atkbd - do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID")
> Reported-by: Hongfei Ren <lcrhf@outlook.com>
> Link: https://github.com/colorcube/Linux-on-Honor-Magicbook-14-Pro/issues/1#issuecomment-4562679891
> Tested-by: Hongfei Ren <lcrhf@outlook.com>
> Cc: stable@kernel.org
> Signed-off-by: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>

Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2026-06-06 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  7:27 [PATCH] Input: atkbd - skip deactivate for HONOR BCC-N's internal keyboard Cryolitia PukNgae
2026-06-06 21:01 ` Dmitry Torokhov [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=aiSKsQCKmRh_FuzS@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=cryolitia.pukngae@linux.dev \
    --cc=hansg@kernel.org \
    --cc=jeffbai@aosc.io \
    --cc=kernel@uniontech.com \
    --cc=kexybiscuit@aosc.io \
    --cc=lcrhf@outlook.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niecheng1@uniontech.com \
    --cc=stable@kernel.org \
    --cc=zhanjun@uniontech.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 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.