linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: rkir@google.com
Cc: Peter Maydell <peter.maydell@linaro.org>,
	linux-fbdev@vger.kernel.org,
	Christoffer Dall <christoffer.dall@linaro.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] ANDROID: goldfish_fb: Set pixclock = 0
Date: Fri, 08 Jun 2018 16:23:52 +0000	[thread overview]
Message-ID: <2257447.FoZO9vJcxE@amdc3058> (raw)
In-Reply-To: <20180531220252.58679-3-rkir@google.com>


[ + linux-fbdev ML ]

On Thursday, May 31, 2018 03:02:52 PM rkir@google.com wrote:
> From: Christoffer Dall <christoffer.dall@linaro.org>
> 
> User space Android code identifies pixclock = 0 as a sign for emulation
> and will set the frame rate to 60 fps when reading this value, which is
> the desired outcome.
> 
> Change-Id: I759bf518bf6683446bc786bf1be3cafa02dd8d42

please drop your local Change-Id from the upstream kernel submissions

> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

your S-o-b line is also needed

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


  parent reply	other threads:[~2018-06-08 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180531220252.58679-1-rkir@google.com>
     [not found] ` <CGME20180531220437epcas3p4a16627f3bfdfcf6f1d0629bb613374d0@epcas3p4.samsung.com>
     [not found]   ` <20180531220252.58679-2-rkir@google.com>
2018-06-08 16:21     ` [PATCH 2/3] goldfish: Enable ACPI-based enumeration for goldfish framebuffer Bartlomiej Zolnierkiewicz
     [not found] ` <CGME20180531220440epcas3p39993702c36d5cd4f97e251629d61949c@epcas3p3.samsung.com>
     [not found]   ` <20180531220252.58679-3-rkir@google.com>
2018-06-08 16:23     ` Bartlomiej Zolnierkiewicz [this message]
2018-06-08 23:40       ` [PATCH 3/3] ANDROID: goldfish_fb: Set pixclock = 0 Roman Kiryanov

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=2257447.FoZO9vJcxE@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=christoffer.dall@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=rkir@google.com \
    /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).