public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Pavel Machek <pavel@denx.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Wolfram Sang <wsa@kernel.org>,
	krzysztof.kozlowski@canonical.com, semen.protsenko@linaro.org,
	robh@kernel.org, yangyicong@hisilicon.com,
	geert+renesas@glider.be, 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.19 12/13] i2c: qup: allow COMPILE_TEST
Date: Wed, 2 Mar 2022 16:01:56 -0500	[thread overview]
Message-ID: <Yh/bRJv7utMEXHnZ@sashalap> (raw)
In-Reply-To: <20220224224126.GC6522@duo.ucw.cz>

On Thu, Feb 24, 2022 at 11:41:26PM +0100, Pavel Machek wrote:
>Hi!
>
>> [ Upstream commit 5de717974005fcad2502281e9f82e139ca91f4bb ]
>>
>> Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
>> and easier maintenance.
>
>I believe this does not fix a bug and so is not suitable for stable.

It does not, but it helps us catch bugs we otherwise wouldn't have.

-- 
Thanks,
Sasha

      reply	other threads:[~2022-03-02 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220223023152.242065-1-sashal@kernel.org>
2022-02-23  2:31 ` [PATCH AUTOSEL 4.19 03/13] i2c: bcm2835: Avoid clock stretching timeouts Sasha Levin
2022-02-23  2:31 ` [PATCH AUTOSEL 4.19 11/13] i2c: cadence: allow COMPILE_TEST Sasha Levin
2022-02-23  2:31 ` [PATCH AUTOSEL 4.19 12/13] i2c: qup: " Sasha Levin
2022-02-24 22:41   ` Pavel Machek
2022-03-02 21:01     ` Sasha Levin [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=Yh/bRJv7utMEXHnZ@sashalap \
    --to=sashal@kernel.org \
    --cc=bence98@sch.bme.hu \
    --cc=geert+renesas@glider.be \
    --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=pavel@denx.de \
    --cc=robh@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