From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] touchscreen: sun4i-ts: Really fix A10 temperature reporting
Date: Wed, 24 Jun 2015 09:31:41 +0200 [thread overview]
Message-ID: <558A5CDD.1070704@redhat.com> (raw)
In-Reply-To: <20150624072840.GV2266@lukather>
Hi,
On 24-06-15 09:28, Maxime Ripard wrote:
> Hi,
>
> On Wed, Jun 24, 2015 at 09:16:54AM +0200, Hans de Goede wrote:
>> Maxime I think we should send the mentioned dts patch to stable for
>> 4.1 , do you agree ?
>
> Yep. We should definitely do that. You take care of this?
Yes I'll try to do so later today.
Regards,
Hans
next prev parent reply other threads:[~2015-06-24 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 9:37 [PATCH] touchscreen: sun4i-ts: Really fix A10 temperature reporting Hans de Goede
2015-03-12 21:54 ` Dmitry Torokhov
2015-06-23 15:06 ` m.silentcreek at gmail.com
2015-06-23 19:46 ` Hans de Goede
2015-06-23 19:54 ` Dmitry Torokhov
2015-06-24 7:16 ` Hans de Goede
2015-06-24 7:28 ` Maxime Ripard
2015-06-24 7:31 ` Hans de Goede [this message]
2015-06-23 20:39 ` m.silentcreek at gmail.com
2015-06-23 21:06 ` m.silentcreek at gmail.com
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=558A5CDD.1070704@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).