From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: sparclinux@vger.kernel.org, kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"David S. Miller" <davem@davemloft.net>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Randy Dunlap <rdunlap@infradead.org>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] sparc: Use shared font data
Date: Sat, 12 Aug 2023 01:06:27 +0000 [thread overview]
Message-ID: <ZNbbEyLRZG+CGePc@gallifrey> (raw)
In-Reply-To: <8c0ea24d-9993-492c-a7bd-fbdac7800479@web.de>
* Markus Elfring (Markus.Elfring@web.de) wrote:
> …
> > v3
> > Added 'select FONT_SUPPORT' (to stop modconfig causing the font to be
> > linked into a module rather than the main kernel)
> >
> > ---
> > arch/sparc/Kconfig | 2 +
> …
>
> I hope that the placement of the version description (or the marker line) will be reconsidered once more
> for the final commit.
Oops yes, I think I got this right in the v3 of the PPC one I just sent.
Do we want a new version sent to move that --- or will someone (who??)
fix that up during commit?
Dave
> See also:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc5#n711
>
> Regards,
> Markus
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2023-08-12 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 1:09 [PATCH v3] sparc: Use shared font data linux
2023-08-07 17:12 ` Sam Ravnborg
2023-08-08 15:51 ` Randy Dunlap
2023-08-08 16:36 ` Sam Ravnborg
[not found] ` <8c0ea24d-9993-492c-a7bd-fbdac7800479@web.de>
2023-08-12 1:06 ` Dr. David Alan Gilbert [this message]
2023-11-04 1:21 ` Dr. David Alan Gilbert
2023-11-04 8:53 ` John Paul Adrian Glaubitz
2023-11-04 16:16 ` Randy Dunlap
2024-02-16 16:16 ` Andreas Larsson
2024-02-17 15:43 ` Dr. David Alan Gilbert
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=ZNbbEyLRZG+CGePc@gallifrey \
--to=linux@treblig.org \
--cc=Markus.Elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
/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