All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: stable@vger.kernel.org, Bernhard Landauer <bernhard@manjaro.org>
Subject: Re: 5.10.192 fails to build (error: ‘RT711_JD2_100K’ undeclared here (not in a function))
Date: Mon, 28 Aug 2023 09:10:50 +0200	[thread overview]
Message-ID: <2023082825-release-opal-fdc4@gregkh> (raw)
In-Reply-To: <1fdd05f6-34fc-4ab7-b58e-090a542317c0@manjaro.org>

On Mon, Aug 28, 2023 at 08:49:14AM +0200, Philip Müller wrote:
> On 28.08.23 08:46, Greg Kroah-Hartman wrote:
> > On Mon, Aug 28, 2023 at 07:17:21AM +0200, Philip Müller wrote:
> > > Hi Greg,
> > > 
> > > Seems this needs to been backported too:
> > > 
> > > https://github.com/torvalds/linux/commit/8e6c00f1fdea9fdf727969d7485d417240d2a1f9
> > > 
> > > At least an #include "../../codecs/rt711.h" in
> > > sound/soc/intel/boards/sof_sdw.c
> > 
> > Now queued up, thanks.
> > 
> > And why are you the only one seeing this issue?  What odd config are you
> > using that none of the CI systems are catching this?
> > 
> > thanks,
> > 
> > greg k-h
> 
> I don't know if it is odd, but here it is:
> https://gitlab.manjaro.org/packages/core/linux510/-/raw/master/config

Thanks, that helped.  And verified that the above commit solved the
issue, thanks for the reporting and testing.

greg k-h

      reply	other threads:[~2023-08-28  7:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 20:36 5.10.192 fails to build (error: ‘RT711_JD2_100K’ undeclared here (not in a function)) Philip Müller
2023-08-27 18:29 ` Greg Kroah-Hartman
2023-08-28  5:09   ` Philip Müller
2023-08-28  5:17     ` Philip Müller
2023-08-28  6:46       ` Greg Kroah-Hartman
2023-08-28  6:49         ` Philip Müller
2023-08-28  7:10           ` Greg Kroah-Hartman [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=2023082825-release-opal-fdc4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bernhard@manjaro.org \
    --cc=philm@manjaro.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.