From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Rapoport <mike@compulab.co.il>,
Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: linux-next: Tree for May 16 (mfd/tpx6586x)
Date: Sat, 19 May 2012 17:53:27 +0100 [thread overview]
Message-ID: <20120519165327.GU4039@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FB7C310.3010403@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Sat, May 19, 2012 at 08:58:08AM -0700, Randy Dunlap wrote:
> On 05/19/2012 07:25 AM, Samuel Ortiz wrote:
> > On Wed, May 16, 2012 at 09:16:03AM -0700, Randy Dunlap wrote:
> >> On 05/16/2012 03:14 AM, Stephen Rothwell wrote:
> >> drivers/built-in.o: In function `tps6586x_i2c_probe':
> >> tps6586x.c:(.devinit.text+0x144e0): undefined reference to `of_regulator_match'
> > Is this one fixed now ? It's coming from Mark's regulator tree, not the MFD
> > one.
> It still fails in linux-next of 20120518.
Probably because the selection of people mailed is rather random - not
only is this the first I've heard about this nobody who actually works
on the driver was contacted either... I don't know how the recipient
list was picked but I'd suggest including a look at the git history
might be in order.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-19 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 10:14 linux-next: Tree for May 16 Stephen Rothwell
2012-05-16 16:01 ` linux-next: Tree for May 16 (mfd/mc13xxx) Randy Dunlap
2012-05-16 18:04 ` Uwe Kleine-König
2012-05-18 11:04 ` Samuel Ortiz
2012-05-16 16:16 ` linux-next: Tree for May 16 (mfd/tpx6586x) Randy Dunlap
2012-05-19 14:25 ` Samuel Ortiz
2012-05-19 15:58 ` Randy Dunlap
2012-05-19 16:53 ` Mark Brown [this message]
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=20120519165327.GU4039@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@avionic-design.de \
/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.