From: Greg KH <greg@kroah.com>
To: Luka Panio <lukapanio@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v10 2/2] Initial support for Xiaomi Pad 6 tablet, that have sm8250 soc.
Date: Sat, 25 Nov 2023 06:53:34 +0000 [thread overview]
Message-ID: <2023112511-pavestone-satin-3b3e@gregkh> (raw)
In-Reply-To: <20231124212732.731419-2-lukapanio@gmail.com>
On Fri, Nov 24, 2023 at 10:27:32PM +0100, Luka Panio wrote:
> Signed-off-by: Luka Panio <lukapanio@gmail.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Acked-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
> ---
> v2:
> Update commit message. Drop reserved gpio's as this device in reality do not have gpio, and pins are not protected.
Again, I see no commit message here, did something go wrong?
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-25 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 21:27 [PATCH v10 1/2] Add a compatible for Xiaomi Pad 6 Luka Panio
2023-11-24 21:27 ` [PATCH v10 2/2] Initial support for Xiaomi Pad 6 tablet, that have sm8250 soc Luka Panio
2023-11-25 6:53 ` Greg KH [this message]
2023-11-25 6:53 ` [PATCH v10 1/2] Add a compatible for Xiaomi Pad 6 Greg KH
2023-11-25 11:06 ` Conor Dooley
2023-11-25 12:09 ` Konrad Dybcio
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=2023112511-pavestone-satin-3b3e@gregkh \
--to=greg@kroah.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukapanio@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.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).