From: Karl Mehltretter <kmehltretter@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Nicolas Pitre <nico@fluxnic.net>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64
Date: Fri, 17 Jul 2026 12:25:26 +0200 [thread overview]
Message-ID: <aloCa9hBXW_7I-QQ@unknown748F3CBA5068> (raw)
In-Reply-To: <8a4b1bb8-57ec-4746-8c98-3bcc13e9ffd9@app.fastmail.com>
On Fri, Jul 17, 2026 at 10:04:17AM +0100, Arnd Bergmann wrote:
> On Fri, Jul 17, 2026, at 09:22, Greg Kroah-Hartman wrote:
> >
> > What about testing builds?
>
> The driver only builds on arm32 or arm64, and there is little
> value of build-testing it on armv4/v5.
>
Oh I already sent a v2 with COMPILE_TEST before reading this.
I'm happy with either version.
thanks,
Karl
next prev parent reply other threads:[~2026-07-17 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 7:16 [PATCH] tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 Karl Mehltretter
2026-07-17 7:22 ` Greg Kroah-Hartman
2026-07-17 8:04 ` Arnd Bergmann
2026-07-17 10:25 ` Karl Mehltretter [this message]
2026-07-17 10:51 ` Greg Kroah-Hartman
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=aloCa9hBXW_7I-QQ@unknown748F3CBA5068 \
--to=kmehltretter@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nico@fluxnic.net \
/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