From: "Timo S." <m.silentcreek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
wens-jdAy2FN1RRM@public.gmane.org,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH] touchscreen: sun4i-ts: Really fix A10 temperature reporting
Date: Wed, 24 Jun 2015 13:59:17 +0200 [thread overview]
Message-ID: <CAKLfuV2rvTy2vSLQfN+db-4J+nTvcRuH6kfGzw4E16wTLjSP4Q@mail.gmail.com> (raw)
In-Reply-To: <558A5966.9010908-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Hi Hans,
On Wed, Jun 24, 2015 at 9:16 AM, Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
Ah yes, something went wrong during the 4.1 cycle wrt merging ARM patches
> which have caused almost all ARM patches intended for 4.1 to get delayed to
> 4.2, including that one, that is the problem.
>
> We did our best to update the driver and the dts in lockstep, and you
> should
> have never seen this problem, but the missing of the merge window for all
> ARM patches during the 4.1 cycle has caused our carefully planned lock-step
> update to fail, sorry about that.
>
No need to apologize. Things happen. Glad to see this cleared up so quickly.
Thanks for the help (and all the other work you do ;)).
Kind regards,
Timo
--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Type: text/html, Size: 1724 bytes --]
next prev parent reply other threads:[~2015-06-24 11:59 UTC|newest]
Thread overview: 11+ 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
[not found] ` <1425893870-28715-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-03-12 21:54 ` Dmitry Torokhov
2015-06-23 15:06 ` m.silentcreek-Re5JQEeQqe8AvxtiuMwx3w
2015-06-23 19:46 ` Hans de Goede
[not found] ` <5589B78C.4080600-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-23 19:54 ` Dmitry Torokhov
2015-06-24 7:16 ` Hans de Goede
[not found] ` <558A5966.9010908-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-24 7:28 ` Maxime Ripard
2015-06-24 7:31 ` Hans de Goede
2015-06-24 11:59 ` Timo S. [this message]
2015-06-23 20:39 ` m.silentcreek-Re5JQEeQqe8AvxtiuMwx3w
2015-06-23 21:06 ` m.silentcreek-Re5JQEeQqe8AvxtiuMwx3w
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=CAKLfuV2rvTy2vSLQfN+db-4J+nTvcRuH6kfGzw4E16wTLjSP4Q@mail.gmail.com \
--to=m.silentcreek-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=wens-jdAy2FN1RRM@public.gmane.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).