From: Hans de Goede <hdegoede@redhat.com>
To: Henning Schild <henning.schild@siemens.com>,
Mark Gross <markgross@kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 0/2] simatic-ipc: enable one more board
Date: Thu, 12 Jan 2023 19:43:53 +0100 [thread overview]
Message-ID: <4ad4fcf9-06b5-857c-f5a4-3db72b6f0e1a@redhat.com> (raw)
In-Reply-To: <20221222103720.8546-1-henning.schild@siemens.com>
Hi,
On 12/22/22 11:37, Henning Schild wrote:
> This series is rather trivial. It renames a few variables to use the
> product names as known by end users and enables the current driver
> to pick up on a board they also work for.
Thank you for your patch series, I've applied this series
to my fixes branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=fixes
Note it will show up in my fixes branch once I've pushed my
local branch there, which might take a while.
I will include this series in my next fixes pull-req to Linus
for the current kernel development cycle.
Regards,
Hans
>
> Henning Schild (2):
> platform/x86: simatic-ipc: correct name of a model
> platform/x86: simatic-ipc: add another model
>
> drivers/platform/x86/simatic-ipc.c | 3 ++-
> include/linux/platform_data/x86/simatic-ipc.h | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2023-01-12 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 10:37 Henning Schild
2022-12-22 10:37 ` [PATCH 1/2] platform/x86: simatic-ipc: correct name of a model Henning Schild
2022-12-22 12:44 ` Andy Shevchenko
2022-12-22 14:04 ` Henning Schild
2022-12-27 20:18 ` Andy Shevchenko
2022-12-22 10:37 ` [PATCH 2/2] platform/x86: simatic-ipc: add another model Henning Schild
2023-01-12 18:43 ` Hans de Goede [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=4ad4fcf9-06b5-857c-f5a4-3db72b6f0e1a@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=henning.schild@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®