From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: s.nawrocki@samsung.com, jrdr.linux@gmail.com,
lgirdwood@gmail.com, alsa-devel@alsa-project.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: samsung: s3c24xx-i2s: Fix typo in DAIFMT handling
Date: Mon, 27 Jun 2022 11:49:46 +0200 [thread overview]
Message-ID: <803785ef-42b7-647c-9653-702067439ae9@linaro.org> (raw)
In-Reply-To: <20220627094335.3051210-1-ckeepax@opensource.cirrus.com>
On 27/06/2022 11:43, Charles Keepax wrote:
> The conversion of the set_fmt callback to direct clock specification
> included a small typo, correct the affected code.
>
> Fixes: 91c49199e6d6 ("ASoC: samsung: Update to use set_fmt_new callback")
Where is this commit from? It's not in next.
> Reported-by: kernel test robot <lkp@intel.com>
You should put such big patchsets in your own repo (e.g. on
Github/Gitlab) and feed it to linux-next or at least to LKP.
This way you would get build coverage... because it seems the build was
missing in your case.
If you prefer not to include it in LKP or linux-next, no problem, but
then you need to build it.
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-27 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:43 Charles Keepax
2022-06-27 9:49 ` Krzysztof Kozlowski [this message]
2022-06-27 11:45 ` Mark Brown
2022-06-27 12:11 ` Krzysztof Kozlowski
2022-06-27 13:07 ` Charles Keepax
2022-06-27 13:16 ` Charles Keepax
2022-06-27 13:19 ` Krzysztof Kozlowski
2022-06-27 13:23 ` Mark Brown
2022-06-27 13:28 ` Krzysztof Kozlowski
2022-06-27 20:46 ` Mark Brown
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=803785ef-42b7-647c-9653-702067439ae9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jrdr.linux@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=s.nawrocki@samsung.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
all inboxes | Powered by JetHome®