From: Helge Deller <deller@gmx.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: Re: [RFC PATCH] fbdev: maxinefb: fix build issues
Date: Thu, 13 Aug 2026 22:52:43 +0200 [thread overview]
Message-ID: <00fca3fb-28a8-4f52-b40c-5dd88b8de0d2@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2608131914280.48788@angie.orcam.me.uk>
On 8/13/26 20:16, Maciej W. Rozycki wrote:
> On Thu, 13 Aug 2026, Helge Deller wrote:
>
>>> This is all ancient source code from the beginning of git time.
>>> Now builds cleanly on 32-bit and 64-bit MACH_DECSTATION.
>>>
>> I've added the various comments from the mail thread to the
>> patch and applied the patch as-is for now.
>
> Given the statement of the problem as per the quotation above I don't
> think there was a need to fast-track it without giving me a chance to
> chime in.
Don't worry. I'm happy to drop the intermediate patch anytime.
Helge
next prev parent reply other threads:[~2026-08-13 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 23:48 [RFC PATCH] fbdev: maxinefb: fix build issues Randy Dunlap
[not found] ` <20260810000251.55AD61F000E9@smtp.kernel.org>
2026-08-10 0:27 ` Randy Dunlap
2026-08-14 2:46 ` Randy Dunlap
2026-08-10 3:24 ` Philippe Mathieu-Daudé
2026-08-10 3:29 ` Randy Dunlap
2026-08-13 18:14 ` Maciej W. Rozycki
2026-08-13 16:11 ` Helge Deller
2026-08-13 18:16 ` Maciej W. Rozycki
2026-08-13 20:52 ` Helge Deller [this message]
2026-08-13 17:31 ` Maciej W. Rozycki
2026-08-13 21:46 ` Randy Dunlap
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=00fca3fb-28a8-4f52-b40c-5dd88b8de0d2@gmx.de \
--to=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=rdunlap@infradead.org \
--cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox