From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: kernel test robot <lkp@intel.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 12/12] regulator/core: use rdev->dev.driver_data
Date: Wed, 1 May 2024 13:11:14 +0200 [thread overview]
Message-ID: <ZjIjUiTPenTPXMaO@qmqm.qmqm.pl> (raw)
In-Reply-To: <202404301218.URkWO6dj-lkp@intel.com>
On Tue, Apr 30, 2024 at 12:53:02PM +0800, kernel test robot wrote:
> Hi Michał,
>
> kernel test robot noticed the following build errors:
[...]
> drivers/pinctrl/renesas/pfc-sh73a0.c: In function 'sh73a0_vccq_mc0_endisable':
> >> drivers/pinctrl/renesas/pfc-sh73a0.c:4027:33: error: 'struct regulator_dev' has no member named 'reg_data'
> 4027 | struct sh_pfc *pfc = reg->reg_data;
> | ^~
> drivers/pinctrl/renesas/pfc-sh73a0.c: In function 'sh73a0_vccq_mc0_is_enabled':
> drivers/pinctrl/renesas/pfc-sh73a0.c:4060:33: error: 'struct regulator_dev' has no member named 'reg_data'
> 4060 | struct sh_pfc *pfc = reg->reg_data;
> | ^~
A patch for the driver coming in v3.
Best Regards
Michał Mirosław
prev parent reply other threads:[~2024-05-01 11:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 14:45 [PATCH v2 00/12] regulator/core: Trivial cleanups and improvements Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 02/12] regulator/core: set_consumer_device_supply: remove `has_dev` Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 01/12] regulator/core: _regulator_get: simplify error returns Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 04/12] regulator/core: regulator_bulk_get: remove redundant NULL stores Michał Mirosław
2024-04-29 16:01 ` Mark Brown
2024-05-01 10:55 ` Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 03/12] regulator/core: of_get_child_regulator: remove goto Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 05/12] regulator/core: regulator_ena_gpio_ctrl: pull in ena_gpio state handling Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 06/12] regulator/core: remove regulator_init callback Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 07/12] regulator/core: remove regulator_get_init_drvdata() Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 08/12] regulator/core: set_consumer_device_supply: avoid copying const data Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 09/12] regulator/tps68470: use rdev_get_drvdata() Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 10/12] regulator/core: use dev_to_rdev() for device -> regulator_dev cast Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 11/12] regulator/core: remove regulator_get/set_drvdata Michał Mirosław
2024-04-29 14:45 ` [PATCH v2 12/12] regulator/core: use rdev->dev.driver_data Michał Mirosław
2024-04-30 2:54 ` kernel test robot
2024-04-30 4:53 ` kernel test robot
2024-05-01 11:11 ` Michał Mirosław [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=ZjIjUiTPenTPXMaO@qmqm.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®