From: Corey Minyard <minyard@acm.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: avifishman70@gmail.com, tali.perry1@gmail.com, joel@jms.id.au,
venture@google.com, yuenn@google.com, benjaminfair@google.com,
jic23@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, openbmc@lists.ozlabs.org,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 0/2] char: ipmi: kcs: add Arbel NPCM8XX support
Date: Mon, 18 Jul 2022 07:51:55 -0500 [thread overview]
Message-ID: <20220718125155.GA40038@minyard.net> (raw)
In-Reply-To: <20220717121124.154734-1-tmaimon77@gmail.com>
On Sun, Jul 17, 2022 at 03:11:22PM +0300, Tomer Maimon wrote:
> This patch set adds Arbel NPCM8XX Keyboard Controller Style (KCS) support to
> KCS NPCM driver.
>
> The NPCM KCS driver tested on NPCM845 evaluation board.
This seems reasonable, I've pulled it into my tree. If anyone has any
issues with this, please respond.
-corey
>
> Tomer Maimon (2):
> dt-bindings: ipmi: Add npcm845 compatible
> char: ipmi: modify NPCM KCS configuration
>
> Documentation/devicetree/bindings/ipmi/npcm7xx-kcs-bmc.txt | 5 +++--
> drivers/char/ipmi/Kconfig | 6 +++---
> 2 files changed, 6 insertions(+), 5 deletions(-)
>
> --
> 2.33.0
>
next prev parent reply other threads:[~2022-07-18 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 12:11 [PATCH v1 0/2] char: ipmi: kcs: add Arbel NPCM8XX support Tomer Maimon
2022-07-17 12:11 ` [PATCH v1 1/2] dt-bindings: ipmi: Add npcm845 compatible Tomer Maimon
2022-07-18 13:43 ` Krzysztof Kozlowski
2022-07-17 12:11 ` [PATCH v1 2/2] char: ipmi: modify NPCM KCS configuration Tomer Maimon
2022-07-18 12:51 ` Corey Minyard [this message]
2022-07-26 19:41 ` [PATCH v1 0/2] char: ipmi: kcs: add Arbel NPCM8XX support Tomer Maimon
2022-07-26 19:47 ` Corey Minyard
2022-07-27 5:39 ` Tomer Maimon
2022-07-27 15:47 ` Corey Minyard
2022-08-04 14:57 ` Tomer Maimon
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=20220718125155.GA40038@minyard.net \
--to=minyard@acm.org \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).