From: kernel@martin.sperl.org
To: Eric Anholt <eric@anholt.net>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-pm@vger.kernel.org, Lee Jones <lee@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Eduardo Valentin <edubezval@gmail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-rpi-kernel@lists.infradead.org,
Zhang Rui <rui.zhang@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V7 2/6] thermal: bcm2835: add thermal driver for bcm2835 soc
Date: Wed, 2 Nov 2016 11:14:35 +0100 [thread overview]
Message-ID: <F7D54C7C-FD75-4F66-AF67-CD5C302EEECC@martin.sperl.org> (raw)
In-Reply-To: <87eg35snvg.fsf@eliezer.anholt.net>
> On 24.10.2016, at 18:38, Eric Anholt <eric@anholt.net> wrote:
>
> Stefan Wahren <stefan.wahren@i2se.com> writes:
>
>> Hi Martin,
>>
>> i think it's necessary to rebase the whole series. Maybe we could get it
>> into 4.10.
>
> Why would it need to be rebased? The status, as far as I know, is that
> we're still waiting for the subsystem maintainer to respond.
Sending out a rebased version 8 (specifically needed for patch 2 and 6).
Martin
next prev parent reply other threads:[~2016-11-02 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 8:23 [PATCH V7 0/6] thermal: bcm2835: add thermal driver kernel-TqfNSX0MhmxHKSADF0wUEw
2016-09-21 8:23 ` [PATCH V7 1/6] dt: bindings: add thermal device driver for bcm2835 kernel
[not found] ` <1474446227-1147-1-git-send-email-kernel-TqfNSX0MhmxHKSADF0wUEw@public.gmane.org>
2016-09-21 8:23 ` [PATCH V7 2/6] thermal: bcm2835: add thermal driver for bcm2835 soc kernel-TqfNSX0MhmxHKSADF0wUEw
2016-09-28 21:10 ` Eric Anholt
[not found] ` <87twczg27x.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2016-10-20 18:57 ` Stefan Wahren
2016-10-24 16:21 ` Stefan Wahren
2016-10-24 16:38 ` Eric Anholt
2016-10-24 18:25 ` Stefan Wahren
[not found] ` <1190898538.120930.02d69662-0b1a-447d-9c29-782aec7a1189.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-10-25 2:47 ` Zhang Rui
2016-10-31 21:06 ` Eric Anholt
2016-11-02 10:14 ` kernel [this message]
2016-09-21 8:23 ` [PATCH V7 6/6] ARM64: bcm2835: add thermal driver to default_config kernel-TqfNSX0MhmxHKSADF0wUEw
2016-09-21 8:23 ` [PATCH V7 3/6] ARM: bcm2835: dts: add thermal node to device-tree of bcm283x kernel
2016-09-21 8:23 ` [PATCH V7 4/6] ARM64: bcm2835: dts: add thermal node to device-tree of bcm2837 kernel
2016-09-21 8:23 ` [PATCH V7 5/6] ARM: bcm2835: add thermal driver to default_config kernel
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=F7D54C7C-FD75-4F66-AF67-CD5C302EEECC@martin.sperl.org \
--to=kernel@martin.sperl.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.org \
--cc=will.deacon@arm.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).