From: David Miller <davem@davemloft.net>
To: syrjala@sci.fi
Cc: sparclinux@vger.kernel.org, linux-fbdev@vger.kernel.org,
mpatocka@redhat.com, dri-devel@lists.freedesktop.org,
b.zolnierkie@samsung.com
Subject: Re: [PATCH] mach64: detect the dot clock divider correctly on sparc
Date: Mon, 08 Oct 2018 05:56:50 +0000 [thread overview]
Message-ID: <20181007.225650.255111318936186975.davem@davemloft.net> (raw)
In-Reply-To: <20180824115851.GC11867@sci.fi>
From: Ville Syrjälä <syrjala@sci.fi>
Date: Fri, 24 Aug 2018 14:58:52 +0300
> But yeah, given the V2CLK thing /5 seems like a perfectly good
> value to use here.
Patch applied.
next prev parent reply other threads:[~2018-10-08 5:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 19:19 [PATCH] mach64: detect the dot clock divider correctly on sparc Mikulas Patocka
2018-08-17 19:29 ` David Miller
2018-08-19 10:36 ` Ville Syrjälä
2018-08-23 21:17 ` Mikulas Patocka
2018-08-24 11:58 ` Ville Syrjälä
2018-10-08 5:56 ` David Miller [this message]
2018-10-08 10:31 ` Bartlomiej Zolnierkiewicz
2018-10-08 10:27 ` 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=20181007.225650.255111318936186975.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=syrjala@sci.fi \
/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).