From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mfd: bcm590xx: add support for second i2c slave address space
Date: Wed, 16 Apr 2014 22:31:41 +0100 [thread overview]
Message-ID: <20140416213141.GD12304@sirena.org.uk> (raw)
In-Reply-To: <20140416110603.GA19671@lee--X1>
On Wed, Apr 16, 2014 at 12:06:03PM +0100, Lee Jones wrote:
> s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
> addmap{0,1} doesn't quite sit right with me.
> REVISIT: Ah, it's address-map, rather than add map. Okay, not as bad
> as I first thought, but still, is there a better naming convention you
> could use?
addrmap or something?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140416/eb361ccd/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Matt Porter <mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Devicetree List
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Tim Kryger <tim.kryger-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Markus Mayer
<markus.mayer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux ARM Kernel List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 2/4] mfd: bcm590xx: add support for second i2c slave address space
Date: Wed, 16 Apr 2014 22:31:41 +0100 [thread overview]
Message-ID: <20140416213141.GD12304@sirena.org.uk> (raw)
In-Reply-To: <20140416110603.GA19671@lee--X1>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Wed, Apr 16, 2014 at 12:06:03PM +0100, Lee Jones wrote:
> s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
> addmap{0,1} doesn't quite sit right with me.
> REVISIT: Ah, it's address-map, rather than add map. Okay, not as bad
> as I first thought, but still, is there a better naming convention you
> could use?
addrmap or something?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Matt Porter <mporter@linaro.org>,
Devicetree List <devicetree@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Tim Kryger <tim.kryger@linaro.org>,
Markus Mayer <markus.mayer@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/4] mfd: bcm590xx: add support for second i2c slave address space
Date: Wed, 16 Apr 2014 22:31:41 +0100 [thread overview]
Message-ID: <20140416213141.GD12304@sirena.org.uk> (raw)
In-Reply-To: <20140416110603.GA19671@lee--X1>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Wed, Apr 16, 2014 at 12:06:03PM +0100, Lee Jones wrote:
> s/regmap/Regmap
It's consistently written regmap in all the documentation and so on :)
> addmap{0,1} doesn't quite sit right with me.
> REVISIT: Ah, it's address-map, rather than add map. Okay, not as bad
> as I first thought, but still, is there a better naming convention you
> could use?
addrmap or something?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-16 21:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 18:50 [PATCH 0/4] Support additional regulators on BCM590xx Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-14 18:50 ` [PATCH 1/4] mfd: bcm590xx: update binding with additional BCM59056 regulators Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-14 18:50 ` [PATCH 2/4] mfd: bcm590xx: add support for second i2c slave address space Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-16 11:06 ` Lee Jones
2014-04-16 11:06 ` Lee Jones
2014-04-16 11:06 ` Lee Jones
2014-04-16 21:31 ` Mark Brown [this message]
2014-04-16 21:31 ` Mark Brown
2014-04-16 21:31 ` Mark Brown
2014-04-17 6:57 ` Lee Jones
2014-04-17 6:57 ` Lee Jones
2014-04-17 6:57 ` Lee Jones
2014-04-17 22:26 ` Matt Porter
2014-04-17 22:26 ` Matt Porter
2014-04-17 22:26 ` Matt Porter
2014-04-22 8:21 ` Lee Jones
2014-04-22 8:21 ` Lee Jones
2014-04-23 22:01 ` Matt Porter
2014-04-23 22:01 ` Matt Porter
2014-04-23 22:05 ` Matt Porter
2014-04-23 22:05 ` Matt Porter
2014-04-28 9:29 ` Lee Jones
2014-04-28 9:29 ` Lee Jones
2014-04-28 9:29 ` Lee Jones
2014-04-17 22:30 ` Matt Porter
2014-04-17 22:30 ` Matt Porter
2014-04-17 22:30 ` Matt Porter
2014-04-14 18:50 ` [PATCH 3/4] regulator: bcm590xx: add support for regulators on secondary i2c slave Matt Porter
2014-04-14 18:50 ` Matt Porter
2014-04-14 19:59 ` Mark Brown
2014-04-14 19:59 ` Mark Brown
2014-04-14 18:50 ` [PATCH 4/4] ARM: dts: bcm590xx: add support for GPLDO and VBUS regulators Matt Porter
2014-04-14 18:50 ` Matt Porter
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=20140416213141.GD12304@sirena.org.uk \
--to=broonie@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.