public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: johannes@sipsolutions.net, backports@vger.kernel.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] backports: add support for voltage / current regulator drivers
Date: Mon, 15 Apr 2013 17:25:34 +0100	[thread overview]
Message-ID: <20130415162534.GJ15837@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1365862424-6530-6-git-send-email-mcgrof@do-not-panic.com>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

On Sat, Apr 13, 2013 at 07:13:42AM -0700, Luis R. Rodriguez wrote:

> This backports the latest regulator drivers for kernels >= 3.4.
> We enable the regulator only on kernels >= 3.4 given that
> it relies on the new probe deferral mechanism which would
> otherwise mean having to support drivers that do not probe

There's no great reliance on deferred probes here...

> correctly. Note that 3.2 had a base regulator implementation
> but that was just stubs.

I'm sorry, what on earth makes you say that?  The regulator API has been
usefully functional since it was merged.

> I did look into a way to upgrade the core kernel regulator
> but given that it relies on late_initcall() and core_initcall()
> we can't update this part of the kernel. I even looked at
> using ksplice for this but it seems ksplice can't be used to
> update init sections on the vmlinux ELF. I also haven't much
> updates to these routines since 3.4 except for 86f5fcfc.

Again I'm not sure what you're talking about here?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-04-15 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1365862424-6530-1-git-send-email-mcgrof@do-not-panic.com>
2013-04-13 14:13 ` [PATCH 5/7] backports: add support for voltage / current regulator drivers Luis R. Rodriguez
2013-04-13 21:01   ` Johannes Berg
2013-04-15 16:26     ` Mark Brown
2013-04-15 16:33       ` Johannes Berg
2013-04-22 13:11         ` Mark Brown
2013-04-23  6:18           ` Luis R. Rodriguez
2013-04-15 16:25   ` Mark Brown [this message]
2013-04-13 14:13 ` [PATCH 6/7] backports: add media subsystem drivers Luis R. Rodriguez
2013-04-13 21:02   ` Johannes Berg

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=20130415162534.GJ15837@opensource.wolfsonmicro.com \
    --to=broonie@kernel.org \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.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