From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Sebastian Reichel" <sre@kernel.org>,
"kernel test robot" <lkp@intel.com>,
"Jelle van der Waa" <jvanderwaa@redhat.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Armin Wolf" <W_Armin@gmx.de>
Subject: Re: [pdx86-platform-drivers-x86:review-ilpo-next 109/109] drivers/platform/x86/ideapad-laptop.c:2044:3: error: field designator 'charge_types' does not refer to any field in type 'const struct power_supply_ext'
Date: Fri, 23 May 2025 12:43:10 +0300 (EEST) [thread overview]
Message-ID: <680a00ed-d701-4d5e-9195-af0b27f376b7@linux.intel.com> (raw)
In-Reply-To: <85091184-1d5b-4a11-a940-2d818d46afef@redhat.com>
On Thu, 22 May 2025, Hans de Goede wrote:
> On 22-May-25 3:52 PM, Sebastian Reichel wrote:
> > Hi,
> >
> > On Thu, May 22, 2025 at 11:36:47AM +0200, Hans de Goede wrote:
> >> On 22-May-25 4:39 AM, kernel test robot wrote:
> >>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git review-ilpo-next
> >>> head: b2012b38080e2f92d43eca59e8249c174a27527c
> >>> commit: b2012b38080e2f92d43eca59e8249c174a27527c [109/109] platform/x86: ideapad: Expose charge_types
> >>> config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250522/202505221051.khDhUKJ0-lkp@intel.com/config)
> >>> compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> >>> rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
> >>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250522/202505221051.khDhUKJ0-lkp@intel.com/reproduce)
> >>>
> >>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> >>> the same patch/commit), kindly add following tags
> >>> | Reported-by: kernel test robot <lkp@intel.com>
> >>> | Closes: https://lore.kernel.org/oe-kbuild-all/202505221051.khDhUKJ0-lkp@intel.com/
> >>>
> >>> All errors (new ones prefixed by >>):
> >>>
> >>>>> drivers/platform/x86/ideapad-laptop.c:2044:3: error: field designator 'charge_types' does not refer to any field in type 'const struct power_supply_ext'
> >>> 2044 | .charge_types = (BIT(POWER_SUPPLY_CHARGE_TYPE_STANDARD) |
> >>> | ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>> 2045 | BIT(POWER_SUPPLY_CHARGE_TYPE_LONGLIFE)),
> >>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>> 1 error generated.
> >>>
> >>>
> >>> vim +2044 drivers/platform/x86/ideapad-laptop.c
> >>
> >> Hmm, this patch depends on:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git/commit/?h=for-next&id=c1f7375a246e5f810191a6c3031d2fa2b80e9f5e
> >
> > I should have merged that through an immutable branch :(
> >
> >> I guess that that patch is not in review-ilpo-next,
> >> maybe Sebastian can take this patch instead of taking
> >> it through pdx86-next ? Or it can be merged after
> >> 6.16-rc1?
> >
> > I will be on trekking trip for 3 weeks starting on Monday (more or
> > less directly after sending my 6.16 PR), so I don't want to take any
> > late patches as I cannot handle potential problems.
>
> No worries, I guess we can just merge the patch after 6.16-rc1 then.
I'll handle it after 6.16-rc1.
It would be nice if the patch submitters would inform us maintainers about
such dependencies up front when submitting a patch.
Have a nice time.
> Enjoy your trekking trip.
>
> Regards,
>
> Hans
>
>
--
i.
prev parent reply other threads:[~2025-05-23 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 2:39 [pdx86-platform-drivers-x86:review-ilpo-next 109/109] drivers/platform/x86/ideapad-laptop.c:2044:3: error: field designator 'charge_types' does not refer to any field in type 'const struct power_supply_ext' kernel test robot
2025-05-22 9:36 ` Hans de Goede
2025-05-22 13:52 ` Sebastian Reichel
2025-05-22 15:11 ` Hans de Goede
2025-05-23 9:43 ` Ilpo Järvinen [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=680a00ed-d701-4d5e-9195-af0b27f376b7@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jvanderwaa@redhat.com \
--cc=linux@weissschuh.net \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sre@kernel.org \
/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