From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] ARM: Implement ARCH_HAS_CC_CAN_LINK
Date: Fri, 6 Feb 2026 13:52:16 +0000 [thread overview]
Message-ID: <aYXyEIwnYdmcl7Lr@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260206143150-e32f59b4-eaf7-4c2c-ba14-5cd03906bb18@linutronix.de>
On Fri, Feb 06, 2026 at 02:32:42PM +0100, Thomas Weißschuh wrote:
> On Fri, Feb 06, 2026 at 01:29:31PM +0000, Russell King (Oracle) wrote:
> > On Fri, Feb 06, 2026 at 02:02:38PM +0100, Thomas Weißschuh wrote:
> > > The generic CC_CAN_LINK detection does not handle different byte orders.
> > > This may lead to userprogs which are not actually runnable on the target
> > > kernel.
> > >
> > > Use architecture-specific logic supporting byte orders instead.
> > >
> > > Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> >
> > Damn, I've recently merged your v1 patch. Can you send a follow-up
> > patch to my patch system please?
>
> Oh, sorry. That was a fast application.
>
> Do you want an incremental patch on top or the full v2?
Incremental please.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2026-02-06 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 13:02 [PATCH v2] ARM: Implement ARCH_HAS_CC_CAN_LINK Thomas Weißschuh
2026-02-06 13:29 ` Russell King (Oracle)
2026-02-06 13:32 ` Thomas Weißschuh
2026-02-06 13:52 ` Russell King (Oracle) [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=aYXyEIwnYdmcl7Lr@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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.