mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 11 [drivers/tty/serial/cpm_uart.ko]
Date: Tue, 12 Sep 2023 07:18:01 +0000	[thread overview]
Message-ID: <89194056-cd44-82ec-c39b-393b2a93ee9d@csgroup.eu> (raw)
In-Reply-To: <22d044d8-581f-0694-f7e1-b6caf11de089@infradead.org>



Le 11/09/2023 à 23:03, Randy Dunlap a écrit :
> 
> 
> On 9/10/23 19:11, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do *not* include material destined for v6.7 in your linux-next
>> included branches until *after* v6.6-rc1 has been released.  Also,
>> do *not* rebase your linu-next included branches onto v6.5.
>>
>> Changes since 20230908:
>>
>> Non-merge commits (relative to Linus' tree): 643
>>   614 files changed, 227990 insertions(+), 9502 deletions(-)
>>
>> ----------------------------------------------------------------------------
> 
> on ppc32:
> 
> ERROR: modpost: "get_brgfreq" [drivers/tty/serial/cpm_uart.ko] undefined!
> 
> 
> Full randconfig file is attached.
> 
> 

Bisected to eb5aa2137275 ("powerpc/82xx: Remove CONFIG_8260 and 
CONFIG_8272")

Seems like previously FSL_SOC was always selected together with CPM2. 
After the mentioned commit it looks like it is now possible to select 
CPM2 manually without FSL_SOC.

I'll try to find a way to fix that.

Christophe

      reply	other threads:[~2023-09-12  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  2:11 linux-next: Tree for Sep 11 Stephen Rothwell
2023-09-11 19:13 ` linux-next: Tree for Sep 11 (drivers/gpu/drm/i915/display/intel_backlight.o) Randy Dunlap
2023-09-12  7:47   ` Jani Nikula
2023-09-12 14:52     ` Randy Dunlap
2023-09-13  3:13       ` Randy Dunlap
2023-09-11 21:03 ` linux-next: Tree for Sep 11 [drivers/tty/serial/cpm_uart.ko] Randy Dunlap
2023-09-12  7:18   ` Christophe Leroy [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=89194056-cd44-82ec-c39b-393b2a93ee9d@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --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

all inboxes | Powered by JetHome®