From: Eric Anholt <eric@anholt.net>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/3] ARM: bcm2835: Add the Raspberry Pi firmware driver
Date: Mon, 01 Jun 2015 10:57:06 -0700 [thread overview]
Message-ID: <87vbf75n2l.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1433148509.2361.35.camel@x220>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
Paul Bolle <pebolle@tiscali.nl> writes:
> On Fri, 2015-05-29 at 12:42 -0700, 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.
>> v6: Drop the try_module_get/module_put stuff, since all clients will
>> be referencing our symbols in order to call those functions,
>> anyway. Fix the kerneldoc comments for the changes in v5.
>
> (This style of commit explanation is getting quite common. I must say I
> rather dislike it. I think people should just update the entire commit
> explanation when needed, and not simply paste any changes at the end of
> it, thereby forcing the the reader to determine which older parts are
> actually overruled by newer parts. Besides, many, or maybe even most, of
> the changes are really not interesting enough to keep in the commit
> explanation.)
It was a slip-up that I didn't move it below the '---'this time (I
changed my workflow a bit, and missed the step). I was assuming that
Lee would just trim them on pulling in the changes.
>> --- /dev/null
>> +++ b/drivers/firmware/raspberrypi.c
>
>> +EXPORT_SYMBOL_GPL(rpi_firmware_property_list);
>
>> +EXPORT_SYMBOL_GPL(rpi_firmware_property);
>
> A patch that uses these exports hit lkml recently:
> https://lkml.org/lkml/2015/5/28/596 .
>
>> +EXPORT_SYMBOL_GPL(rpi_firmware_get);
>
> But I didn't spot a (recent) patch that uses this export. Is it queued
> somewhere?
This is from the v5 changes due to review feedback, and the clients need
to be changed to use it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-06-01 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 19:42 [PATCH v6 1/3] dt/bindings: Add binding for " Eric Anholt
2015-05-29 19:42 ` [PATCH v6 2/3] ARM: bcm2835: Add " Eric Anholt
2015-06-01 8:48 ` Paul Bolle
2015-06-01 17:57 ` Eric Anholt [this message]
2015-06-03 21:35 ` Lee Jones
2015-05-29 19:42 ` [PATCH v6 3/3] ARM: bcm2835: Add the firmware driver information to the RPi DT Eric Anholt
2015-06-03 21:30 ` [PATCH v6 1/3] dt/bindings: Add binding for the Raspberry Pi firmware driver Lee Jones
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=87vbf75n2l.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=pebolle@tiscali.nl \
--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
Powered by JetHome