From: Randy Dunlap <rdunlap@infradead.org>
To: Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
ajax@redhat.com,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: uvesafb: Fix URLs in the documentation
Date: Sat, 22 Sep 2018 03:45:58 +0000 [thread overview]
Message-ID: <71823a1d-52a6-5aa1-085c-c5e10c8fc2a8@infradead.org> (raw)
Hi,
I just noticed that the uvesafb.txt file needs to be updated
and then I found that Adam Jackson sent a patch for it last October.
patch:
https://marc.info/?l=linux-fbdev&m\x150765722422257&w=2
patchwork:
https://patchwork.kernel.org/patch/9996857/
What happened here? anything?
Anyway, for Adam's patch:
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
--
~Randy
next reply other threads:[~2018-09-22 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 3:45 Randy Dunlap [this message]
[not found] ` <CGME20180926160733eucas1p184cb12e376fa794603967119ed8a40eb@eucas1p1.samsung.com>
2018-09-26 16:07 ` uvesafb: Fix URLs in the documentation Bartlomiej Zolnierkiewicz
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=71823a1d-52a6-5aa1-085c-c5e10c8fc2a8@infradead.org \
--to=rdunlap@infradead.org \
--cc=ajax@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).