From: Greg KH <gregkh@linuxfoundation.org>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Cc: linux-kernel@vger.kernel.org, noralf@tronnes.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: fbtft: Fix bug in fbtft-core
Date: Sun, 2 Oct 2016 17:16:53 +0200 [thread overview]
Message-ID: <20161002151653.GB12676@kroah.com> (raw)
In-Reply-To: <1475314852-4648-1-git-send-email-ksenija.stanojevic@gmail.com>
On Sat, Oct 01, 2016 at 11:40:52AM +0200, Ksenija Stanojevic wrote:
> Commit 367e8560e8d7a62d96e9b1d644028a3816e04206 introduced a bug
> in fbtft-core where fps is always 0, this is because variable
> update_time is not assigned correctly.
>
> Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Can you add a "Fixes:" tag here, showing the short sha1 id and name of
the patch this is fixing, and add a cc: stable line as well? That way
we can know to backport this to the relevant kernels (4.4 and newer).
thanks,
greg k-h
prev parent reply other threads:[~2016-10-02 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 9:40 [PATCH] Staging: fbtft: Fix bug in fbtft-core Ksenija Stanojevic
2016-10-02 15:16 ` Greg KH [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=20161002151653.GB12676@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=ksenija.stanojevic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.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).