From: Roman Kiryanov <rkir@google.com>
To: b.zolnierkie@samsung.com
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] ANDROID: goldfish_fb: Set pixclock = 0
Date: Fri, 08 Jun 2018 23:40:12 +0000 [thread overview]
Message-ID: <CAOGAQeqSNpzyJ=644HH-XwW=pwwZBEuX4uVK1ekMSEoMpYMBMw@mail.gmail.com> (raw)
In-Reply-To: <2257447.FoZO9vJcxE@amdc3058>
Hi,
thank you for reviewing our patches. I sent "v2".
Regards,
Roman.
On Fri, Jun 8, 2018 at 9:24 AM Bartlomiej Zolnierkiewicz
<b.zolnierkie@samsung.com> wrote:
>
>
> [ + 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
>
prev parent reply other threads:[~2018-06-08 23:40 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 ` [PATCH 3/3] ANDROID: goldfish_fb: Set pixclock = 0 Bartlomiej Zolnierkiewicz
2018-06-08 23:40 ` Roman Kiryanov [this message]
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='CAOGAQeqSNpzyJ=644HH-XwW=pwwZBEuX4uVK1ekMSEoMpYMBMw@mail.gmail.com' \
--to=rkir@google.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).