public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: ti: ams-delta: Allow it to be test compiled
Date: Sat, 21 Oct 2023 01:19:20 +0200	[thread overview]
Message-ID: <13380212.uLZWGnKmhe@dell> (raw)
In-Reply-To: <9bbab4c8-f616-4abc-9eee-022c19c6921d@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

On Thursday, 19 October 2023 13:40:57 CEST Mark Brown wrote:
> On Sun, Oct 08, 2023 at 03:53:10PM +0200, Janusz Krzysztofik wrote:
> > The driver is now built only when MACH_AMS_DELTA is selected, which
> > requires a very specific selection of ARCH settings.  As a consequence, it
> > gets very little attention from build-bots, if not none.
> 
> Acked-by: Mark Brown <broonie@kernel.org>

Hi Mark,

Thanks for your Ack.

Since the fix required for successful compilation of the ams-delta ASoC 
driver already reached v6.6, my former suggestion to pass this change also 
via Greg's tty tree is probably no longer vital.

Thanks,
Janusz


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-10-20 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08 13:53 [PATCH] ASoC: ti: ams-delta: Allow it to be test compiled Janusz Krzysztofik
2023-10-08 18:03 ` kernel test robot
2023-10-09 21:34   ` Janusz Krzysztofik
2023-10-08 19:25 ` kernel test robot
2023-10-19 11:40 ` Mark Brown
2023-10-20 23:19   ` Janusz Krzysztofik [this message]
2023-10-24 18:53 ` 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=13380212.uLZWGnKmhe@dell \
    --to=jmkrzyszt@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.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