public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Alex Davis <alex47794@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Borislav Petkov <bp@alien8.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	John Ogness <john.ogness@linutronix.de>,
	linux-serial <linux-serial@vger.kernel.org>
Subject: Re: [Regression] depmod fails on kernel 6.17.1 rc1
Date: Fri, 7 Nov 2025 10:17:55 +0200	[thread overview]
Message-ID: <aQ2rM3KOrCaMqXi6@smile.fi.intel.com> (raw)
In-Reply-To: <aQzliw1B5DPKcwi5@smile.fi.intel.com>

On Thu, Nov 06, 2025 at 08:14:35PM +0200, Andy Shevchenko wrote:
> On Thu, Nov 06, 2025 at 08:00:36PM +0200, Ilpo Järvinen wrote:
> > On Thu, 6 Nov 2025, Ilpo Järvinen wrote:
> > > On Thu, 6 Nov 2025, Borislav Petkov wrote:
> > > > On Thu, Nov 06, 2025 at 06:15:57PM +0200, Andy Shevchenko wrote:
> > > > > > So I'm seeing this with an allmodconfig build too:
> > > > 			       ^^^^^^^^^^^^
> > > > > > depmod: ERROR: Cycle detected: 8250 -> 8250_base -> 8250
> > > > > > depmod: ERROR: Found 2 modules in dependency cycles!
> > > > > 
> > > > > I'm surprised it took so long to people to start complaining.
> > > > > 
> > > > > So, some of those are modules? Can you share the
> > > > > 
> > > > > 	grep 8250 .config
> > > > > 
> > > > > part?
> > > > 
> > > > See above.
> > > 
> > > https://lore.kernel.org/all/87frc3sd8d.fsf@posteo.net/
> > > 
> > > I wonder if 8250_rsa.o can be put into 8250_base.o where most of its 
> > > callers are anyway?
> > 
> > This seems to resolve the build issue for me:
> 
> I prefer this solution to anything that suggests to merge the 8250_rsa in
> another module.

Oh, I meant "merge the source of the 8250_rsa", and here we are talking about
merging the object file, which is totally fine! Sorry for the confusion it
might made.

> If it fixes for the reporters, feel free to add my
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-11-07  8:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADiockCvM6v+d+UoFZpJSMoLAdpy99_h-hJdzUsdfaWGn3W7-g@mail.gmail.com>
2025-11-06 16:02 ` [Regression] depmod fails on kernel 6.17.1 rc1 Borislav Petkov
2025-11-06 16:15   ` Andy Shevchenko
2025-11-06 16:24     ` Borislav Petkov
2025-11-06 16:35       ` Ilpo Järvinen
2025-11-06 18:00         ` Ilpo Järvinen
2025-11-06 18:14           ` Andy Shevchenko
2025-11-07  8:17             ` Andy Shevchenko [this message]
2025-11-07  9:40               ` Ilpo Järvinen
2025-11-07  6:20           ` Jiri Slaby
2025-11-08 13:32             ` Borislav Petkov
2025-11-08 23:52             ` Stephen Rothwell
2025-11-09  0:49               ` Greg Kroah-Hartman
2025-11-09  6:34                 ` Stephen Rothwell
2025-11-10 10:43                   ` Ilpo Järvinen

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=aQ2rM3KOrCaMqXi6@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alex47794@gmail.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.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