Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: WangYuli <wangyuli@uniontech.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhanjun@uniontech.com, niecheng1@uniontech.com,
	guanwentao@uniontech.com
Subject: Re: Gentle ping: [PATCH v2 0/6] MIPS: Resolve build problems on decstation_64
Date: Wed, 16 Jul 2025 21:24:02 +0200	[thread overview]
Message-ID: <aHf8Uo2FEcRqus9T@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2507071545400.56608@angie.orcam.me.uk>

On Mon, Jul 07, 2025 at 03:57:01PM +0100, Maciej W. Rozycki wrote:
> Hi WangYuli,
> 
> > This is a gentle ping.
> > 
> > I've addressed all the feedback from previous discussions and tried resending
> > multiple times, but haven't received any response
> 
>  Thank you for pinging.
> 
>  I've tried to verify your changes at run time and it's turned out that a 
> generic change to the serial communication subsystem made a while ago has 
> caused the port to become unbootable, and it now crashes early on in port 
> registration.

I'm hitting the same issue for IP22, my dirty hack to get serial console
back is

diff --git a/drivers/tty/serial/serial_base_bus.c b/drivers/tty/serial/serial_base_bus.c
index 5d1677f1b651..fccb0f1c3cc5 100644
--- a/drivers/tty/serial/serial_base_bus.c
+++ b/drivers/tty/serial/serial_base_bus.c
@@ -78,12 +78,14 @@ static int serial_base_device_init(struct uart_port *port,
 		return -EPROBE_DEFER;
 	}
 
+#if 0
 	if (type == &serial_ctrl_type)
 		return dev_set_name(dev, "%s:%d", dev_name(port->dev), ctrl_id);
 
 	if (type == &serial_port_type)
 		return dev_set_name(dev, "%s:%d.%d", dev_name(port->dev),
 				    ctrl_id, port_id);
+#endif
 
 	return -EINVAL;
 }

I'm not sure, if port->dev needs to be populated now for every serial
port or if there should be a check for port->dev == NULL in the code above...

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2025-07-16 19:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 10:18 [PATCH v2 0/6] MIPS: Resolve build problems on decstation_64 WangYuli
2025-04-22 10:22 ` [PATCH v2 1/6] MIPS: dec: Only check -msym32 when need compiler WangYuli
2025-04-22 10:22 ` [PATCH v2 2/6] MIPS: Eliminate Redundant KBUILD_SYM32 Checks WangYuli
2025-04-22 10:22 ` [PATCH v2 3/6] MIPS: dec: Create reset.h WangYuli
2025-04-22 10:22 ` [PATCH v2 4/6] MIPS: dec: Remove dec_irq_dispatch() WangYuli
2025-04-22 10:27   ` Philippe Mathieu-Daudé
2025-04-22 10:22 ` [PATCH v2 5/6] MIPS: decstation_64_defconfig: Update configs dependencies WangYuli
2025-04-22 10:22 ` [PATCH v2 6/6] MIPS: decstation_64_defconfig: Compile the kernel with warnings as errors WangYuli
2025-07-07  6:58 ` Gentle ping: [PATCH v2 0/6] MIPS: Resolve build problems on decstation_64 WangYuli
2025-07-07 14:57   ` Maciej W. Rozycki
2025-07-16 19:24     ` Thomas Bogendoerfer [this message]
2025-07-18 14:38       ` Maciej W. Rozycki
2026-06-23 13:26     ` WangYuli
2026-06-23 14:39       ` Maciej W. Rozycki

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=aHf8Uo2FEcRqus9T@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=guanwentao@uniontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=niecheng1@uniontech.com \
    --cc=wangyuli@uniontech.com \
    --cc=zhanjun@uniontech.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