From: Lee Jones <lee@kernel.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Eric Anholt <eric@anholt.net>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 2/3] ARM: bcm2835: Add the Raspberry Pi firmware driver
Date: Fri, 5 Jun 2015 20:21:35 +0100 [thread overview]
Message-ID: <20150605192135.GA3301@x1> (raw)
In-Reply-To: <55711428.4080506@wwwdotorg.org>
On Thu, 04 Jun 2015, Stephen Warren wrote:
> On 06/04/2015 02:11 PM, Eric Anholt wrote:
> > This gives us a function for making mailbox property channel requests
> > of the firmware, which is most notable in that it will let us get and
> > set clock rates.
>
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Does anyone know how drivers/firmware/ is managed? I don't seem to be
able to find a maintainer/supporter listed in MAINTAINERS.
next prev parent reply other threads:[~2015-06-05 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 20:11 [PATCH v7 1/3] dt/bindings: Add binding for the Raspberry Pi firmware driver Eric Anholt
[not found] ` <1433448707-18104-1-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-06-04 20:11 ` [PATCH v7 2/3] ARM: bcm2835: Add " Eric Anholt
2015-06-05 3:14 ` Stephen Warren
2015-06-05 19:21 ` Lee Jones [this message]
2015-06-05 19:41 ` Stephen Warren
2015-06-04 20:11 ` [PATCH v7 3/3] ARM: bcm2835: Add the firmware driver information to the RPi DT Eric Anholt
[not found] ` <1433448707-18104-3-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-06-05 19:24 ` Lee Jones
2015-06-05 19:23 ` [PATCH v7 1/3] dt/bindings: Add binding for the Raspberry Pi firmware driver Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2015-07-18 5:54 Eric Anholt
2015-07-18 5:54 ` [PATCH v7 2/3] ARM: bcm2835: Add " Eric Anholt
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=20150605192135.GA3301@x1 \
--to=lee@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.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).