linux-kernel - Re: [PATCH RFT 2/2] regulator: max1586: Convert max1586_v3_ops to set_voltage_sel and map_voltage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAF+7xWm_C5tZaXPsH3944_f-h4vuvRb1MorPuTB0fWTVhT9RPA@mail.gmail.com>
Date:	Mon, 11 Jun 2012 07:27:15 +0800
From:	Axel Lin <axel.lin@...il.com>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH RFT 2/2] regulator: max1586: Convert max1586_v3_ops to
 set_voltage_sel and map_voltage_linear

2012/6/11 Robert Jarzmik <robert.jarzmik@...e.fr>:
> Axel Lin <axel.lin@...il.com> writes:
>
>> Signed-off-by: Axel Lin <axel.lin@...il.com>
> Hi Axel,
>
> The patches look OK to me, but I cannot build them.
> Even on top of linux-next, I get :
> drivers/regulator/max1586.c: In function 'max1586_v6_set_voltage_sel':
> drivers/regulator/max1586.c:86:2: error: 'const struct regulator_desc' has no member named 'volt_table'
> drivers/regulator/max1586.c: At top level:
> drivers/regulator/max1586.c:105:18: error: 'regulator_list_voltage_table' undeclared here (not in a function)
> drivers/regulator/max1586.c:123:3: error: unknown field 'volt_table' specified in initializer
> drivers/regulator/max1586.c:123:3: warning: initialization from incompatible pointer type [enabled by default]
> drivers/regulator/max1586.c:123:3: warning: (near initialization for 'max1586_reg[1].ops') [enabled by default]
>
> I suppose you're basing your tree on top of a set of commits not available in
> linux-next (maybe Mark's regulator tree ?). As I don't have that tree in mind,
> it would be kind to tell me which tree you're basing your work on, so that I
> could test your last patches.

I think all the necessary patches are already in linux-next tree.
I have no problem to build it with linux-next 20120608.

Regards,
Axel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/