mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armin Wolf <W_Armin@gmx.de>, Hans de Goede <hansg@kernel.org>,
	 Werner Sembach <wse@tuxedocomputers.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: uniwill-laptop: Add 2 new feature defines for TUXEDO devices
Date: Tue, 21 Jul 2026 20:16:05 +0300	[thread overview]
Message-ID: <178465416530.18499.3063937849947940461.b4-ty@b4> (raw)
In-Reply-To: <20260708211950.568799-1-wse@tuxedocomputers.com>

On Wed, 08 Jul 2026 23:18:21 +0200, Werner Sembach wrote:

> Add 2 of the new feature defines, UNIWILL_FEATURE_AC_AUTO_BOOT and
> UNIWILL_FEATURE_USB_POWERSHARE, to TUXEDO devices where applicable.

Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.

FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.

The list of commits applied:
[1/2] platform/x86: uniwill-laptop: Add 2 new feature defines for TUXEDO devices
      commit: 527b1169526de6dbaeb646d48b20720a12b5a233
[2/2] platform/x86: uniwill-laptop: Add Avell A60 MUV support
      commit: e6137bbef0fe23feaf19e4714892457853064eb6

--
 i.


      parent reply	other threads:[~2026-07-21 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 21:18 Werner Sembach
2026-07-08 21:18 ` [PATCH 2/2] platform/x86: uniwill-laptop: Add Avell A60 MUV support Werner Sembach
2026-07-21 17:16 ` Ilpo Järvinen [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=178465416530.18499.3063937849947940461.b4-ty@b4 \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=W_Armin@gmx.de \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=wse@tuxedocomputers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®