From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
kernel@pengutronix.de,
Sven Schneider <s.schneider@arkona-technologies.de>
Subject: Re: [PATCH v2] lib/fonts: add font 6x8 for OLED display
Date: Tue, 8 Sep 2020 13:37:19 +0200 [thread overview]
Message-ID: <421b685e-4932-9f12-e795-62e8460d9948@samsung.com> (raw)
In-Reply-To: <20200820084239.GB1001857@kroah.com>
On 8/20/20 10:42 AM, Greg Kroah-Hartman wrote:
> On Thu, Aug 20, 2020 at 10:21:37AM +0200, Sascha Hauer wrote:
>> From: Sven Schneider <s.schneider@arkona-technologies.de>
>>
>> This font is derived from lib/fonts/font_6x10.c and is useful for small
>> OLED displays
>>
>> Signed-off-by: Sven Schneider <s.schneider@arkona-technologies.de>
>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Applied to drm-misc-next tree, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2020-09-08 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 8:21 [PATCH v2] lib/fonts: add font 6x8 for OLED display Sascha Hauer
2020-08-20 8:42 ` Greg Kroah-Hartman
2020-09-08 11:37 ` Bartlomiej Zolnierkiewicz [this message]
2020-10-18 18:12 ` [PATCH 1/2] Fonts: Support FONT_EXTRA_WORDS macros for font_6x8 Peilin Ye
2020-10-18 18:14 ` [PATCH 2/2] docs: fb: Add font_6x8 to available built-in fonts Peilin Ye
2020-10-18 20:54 ` [PATCH 2/2 RESEND] " Peilin Ye
2020-10-19 15:56 ` Daniel Vetter
2020-10-18 20:09 ` [PATCH 1/2] Fonts: Support FONT_EXTRA_WORDS macros for font_6x8 Daniel Vetter
2020-10-18 20:18 ` Peilin Ye
2020-10-18 20:33 ` Daniel Vetter
2020-10-18 20:44 ` Peilin Ye
2020-10-18 21:51 ` Daniel Vetter
2020-10-19 9:55 ` Peilin Ye
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=421b685e-4932-9f12-e795-62e8460d9948@samsung.com \
--to=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s.schneider@arkona-technologies.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;
as well as URLs for NNTP newsgroup(s).