From: Mark Brown <broonie@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Liviu Dudau <liviu.dudau@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] regulator: vexpress: rename vexpress regulator implementation
Date: Mon, 15 Feb 2016 18:10:17 +0000 [thread overview]
Message-ID: <20160215181017.GU18988@sirena.org.uk> (raw)
In-Reply-To: <56BB8652.4000808@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Wed, Feb 10, 2016 at 06:49:54PM +0000, Sudeep Holla wrote:
> On 29/01/16 17:37, Sudeep Holla wrote:
> >The vexpress regulator implementation is currently just called vexpress.
> >This is a problem because it clashes with another module with the same
> >name in hardware monitors.
> >This patch renames the vexpress regulator implementation to
> >vexpress-regulator so that there will be no clash in the module namespace.
> Can you take this patch for v4.6 ? It was reported @[1]
Please allow a reasonable time for review. People get busy, go on
holiday, attend conferences and so on so unless there is some reason for
urgency (like critical bug fixes) please allow at least a couple of
weeks for review. Sending content free pings just adds to the mail
volume (if they are seen at all) and if something has gone wrong you'll
have to resend the patches anyway.
> [1] https://lkml.org/lkml/2016/1/29/7
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-02-15 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 17:37 [PATCH] regulator: vexpress: rename vexpress regulator implementation Sudeep Holla
2016-02-10 18:49 ` Sudeep Holla
2016-02-15 18:10 ` Mark Brown [this message]
2016-02-15 18:12 ` Mark Brown
2016-02-15 18:31 ` Sudeep Holla
2016-02-15 21:00 ` Mark Brown
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=20160215181017.GU18988@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=rusty@rustcorp.com.au \
--cc=sudeep.holla@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