From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: ERROR: "sst_context_init" [sound/soc/intel/atom/sst/snd-intel-sst-acpi.ko] undefined!
Date: Thu, 15 Feb 2018 11:20:41 +0000 [thread overview]
Message-ID: <20180215112041.GB8374@sirena.org.uk> (raw)
In-Reply-To: <bc8a4057-f666-30a4-9144-3bd01db1b6ba@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Wed, Feb 14, 2018 at 03:41:22PM -0600, Pierre-Louis Bossart wrote:
> On 02/14/2018 01:23 PM, kbuild test robot wrote:
> This was reported by Arnd Bergman and fixed with a patch sent on January 24
> to alsa-devel ("ASoC: Intel: atom: fix ACPI/PCI Kconfig"), but I don't see
> it in Mark's tree?
> http://mailman.alsa-project.org/pipermail/alsa-devel/2018-January/130979.html
Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, though there are some other maintainers who like them - if in
doubt look at how patches for the subsystem are normally handled.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-02-15 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 19:23 kbuild test robot
2018-02-14 21:41 ` Pierre-Louis Bossart
2018-02-15 11:20 ` Mark Brown [this message]
2018-03-11 3:19 kbuild test robot
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=20180215112041.GB8374@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.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
all inboxes | Powered by JetHome®