From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Wolfram Sang <wsa@kernel.org>,
krzysztof.kozlowski@canonical.com, robh@kernel.org,
semen.protsenko@linaro.org, yangyicong@hisilicon.com,
sven@svenpeter.dev, jie.deng@intel.com, bence98@sch.bme.hu,
lukas.bulwahn@gmail.com, linux-i2c@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.9 8/9] i2c: qup: allow COMPILE_TEST
Date: Thu, 24 Feb 2022 23:39:53 +0100 [thread overview]
Message-ID: <20220224223953.GB6522@duo.ucw.cz> (raw)
In-Reply-To: <20220223023300.242616-8-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Tue 2022-02-22 21:32:59, Sasha Levin wrote:
> From: Wolfram Sang <wsa@kernel.org>
>
> [ Upstream commit 5de717974005fcad2502281e9f82e139ca91f4bb ]
>
> Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
> and easier maintenance.
I don't believe this is suitable for stable.
Best regards,
Pavel
> +++ b/drivers/i2c/busses/Kconfig
> @@ -783,7 +783,7 @@ config I2C_PXA_SLAVE
>
> config I2C_QUP
> tristate "Qualcomm QUP based I2C controller"
> - depends on ARCH_QCOM
> + depends on ARCH_QCOM || COMPILE_TEST
> help
> If you say yes to this option, support will be included for the
> built-in I2C interface on the Qualcomm SoCs.
> --
> 2.34.1
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-02-24 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220223023300.242616-1-sashal@kernel.org>
2022-02-23 2:32 ` [PATCH AUTOSEL 4.9 3/9] i2c: bcm2835: Avoid clock stretching timeouts Sasha Levin
2022-02-23 2:32 ` [PATCH AUTOSEL 4.9 8/9] i2c: qup: allow COMPILE_TEST Sasha Levin
2022-02-24 22:39 ` Pavel Machek [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=20220224223953.GB6522@duo.ucw.cz \
--to=pavel@denx.de \
--cc=bence98@sch.bme.hu \
--cc=jie.deng@intel.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=robh@kernel.org \
--cc=sashal@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=stable@vger.kernel.org \
--cc=sven@svenpeter.dev \
--cc=wsa@kernel.org \
--cc=yangyicong@hisilicon.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