public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	James Schulman <james.schulman@cirrus.com>,
	David Rhodes <david.rhodes@cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: linux-next: Tree for Sep 15 (drivers/mfd/cs42l43.o)
Date: Tue, 19 Sep 2023 15:21:40 +0100	[thread overview]
Message-ID: <20230919142140.GW13143@google.com> (raw)
In-Reply-To: <5baf9fcb-1c53-48b3-8742-ca3c98d82ebc@infradead.org>

On Mon, 18 Sep 2023, Randy Dunlap wrote:

> 
> 
> On 9/18/23 07:40, Lee Jones wrote:
> > On Fri, 15 Sep 2023, Randy Dunlap wrote:
> > 
> >>
> >>
> >> On 9/14/23 19:01, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20230914:
> >>>
> >>> The btrfs tree gained a conflist against the mm tree.
> >>>
> >>> The device-mapper tree gained a build failure so I used the version
> >>> from next-20230914.
> >>>
> >>> The kspp tree lost its build failure.
> >>>
> >>> Non-merge commits (relative to Linus' tree): 5026
> >>>  2501 files changed, 391711 insertions(+), 34318 deletions(-)
> >>>
> >>> ----------------------------------------------------------------------------
> >>>
> >>
> >> on arm64:
> >>
> >> aarch64-linux-ld: drivers/mfd/cs42l43.o: in function `cs42l43_boot_work':
> >> cs42l43.c:(.text+0x19d4): undefined reference to `devm_regmap_add_irq_chip'
> >>
> >> Using GCC 13.2.0 from kernel.org crosstools.
> >>
> >> Full randconfig file is attached.
> > 
> > Who is the intended consumer of this report?
> > 
> 
> I Cc-ed the driver maintainers and the subsystem maintainer.
> However, I missed Cc-ing the person who git blame identifies
> for this patch. (added now)
> 
> > Are you planning on following up with a patch?
> 
> Sure, I will do that.

Thanks for considering it.  Thanks again for actually doing it.

And sorry that a fix (that I hadn't yet seen) was already on the list.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2023-09-19 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  2:01 linux-next: Tree for Sep 15 Stephen Rothwell
2023-09-15 19:20 ` linux-next: Tree for Sep 15 (drivers/mfd/cs42l43.o) Randy Dunlap
2023-09-18 14:40   ` Lee Jones
2023-09-18 19:25     ` Randy Dunlap
2023-09-19 14:21       ` Lee Jones [this message]
2023-09-15 19:30 ` linux-next: Tree for Sep 15 (drivers/firmware/qcom) Randy Dunlap

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=20230919142140.GW13143@google.com \
    --to=lee@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=james.schulman@cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rf@opensource.cirrus.com \
    --cc=sfr@canb.auug.org.au \
    /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