public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Uwe Kleine-König" <ukleinek@kernel•org>
Cc: Michal Wilczynski <m.wilczynski@samsung•com>,
	Danilo Krummrich <dakr@kernel•org>,
	Boqun Feng <boqun.feng@gmail•com>,
	Daniel Almeida <daniel.almeida@collabora•com>,
	Peter Colberg <pcolberg@redhat•com>,
	Lyude Paul <lyude@redhat•com>, Miguel Ojeda <ojeda@kernel•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the pwm tree
Date: Mon, 27 Oct 2025 12:51:48 +1100	[thread overview]
Message-ID: <20251027125148.7f7d8ed6@canb.auug.org.au> (raw)

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

Hi all,

After merging the pwm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

error[E0277]: the trait bound `core::result::Result<core::pin::Pin<Box<Th1520PwmPlatformDriver, Kmalloc>>, kernel::error::Error>: PinInit<Th1520PwmPlatformDriver, kernel::error::Error>` is not satisfied
   --> drivers/pwm/pwm_th1520.rs:331:10
    |
331 |     ) -> Result<Pin<KBox<Self>>> {
    |          ^^^^^^^^^^^^^^^^^^^^^^^ unsatisfied trait bound
    |
    = help: the trait `PinInit<Th1520PwmPlatformDriver, kernel::error::Error>` is not implemented for `Result<Pin<Box<Th1520PwmPlatformDriver, Kmalloc>>, Error>`
            but trait `PinInit<core::pin::Pin<Box<Th1520PwmPlatformDriver, Kmalloc>>, kernel::error::Error>` is implemented for it
    = help: for that trait implementation, expected `core::pin::Pin<Box<Th1520PwmPlatformDriver, Kmalloc>>`, found `Th1520PwmPlatformDriver`
note: required by a bound in `kernel::platform::Driver::{synthetic#0}`
   --> rust/kernel/platform.rs:196:15
    |
196 |     ) -> impl PinInit<Self, Error>;
    |               ^^^^^^^^^^^^^^^^^^^^ required by this bound in `Driver::{synthetic#0}`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.

Caused by commit

  fb3957af9ec6 ("pwm: Add Rust driver for T-HEAD TH1520 SoC")

presumably interacting with something merged earlier in my tree.
If someone could provide me with an appropriate merge resolution, I will
apply it.

I have used the pwm tree from next-20251024 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2025-10-27  1:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20251027015241eucas1p1784b974d0c150e8c3513f32401205669@eucas1p1.samsung.com>
2025-10-27  1:51 ` Stephen Rothwell [this message]
2025-10-27  8:11   ` linux-next: build failure after merge of the pwm tree Uwe Kleine-König
2025-10-27  9:38     ` Danilo Krummrich
2025-10-28  1:51       ` Stephen Rothwell
2025-12-05  3:33         ` Stephen Rothwell
2025-10-27 13:40     ` Uwe Kleine-König
2025-10-27 13:49       ` Danilo Krummrich
2025-10-28  9:52     ` linux-next: build failure after merge of the pwm tree' Alice Ryhl
2025-10-27  8:36   ` linux-next: build failure after merge of the pwm tree Michal Wilczynski
2023-12-21  5:58 Stephen Rothwell
2023-12-21  9:25 ` Thierry Reding
2023-12-21 10:09   ` Lee Jones
2023-12-21 12:13     ` Sean Young
2023-12-21 12:51       ` Lee Jones
  -- strict thread matches above, loose matches on Subject: below --
2019-01-12  6:01 Stephen Rothwell
2019-01-12  6:08 ` Stephen Rothwell
2019-01-12 15:27   ` Uwe Kleine-König
2014-08-22 21:07 Stephen Rothwell
2014-08-22 22:06 ` Thierry Reding
2014-08-22 22:15   ` Thierry Reding
2014-08-22 22:30     ` Stephen Rothwell

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=20251027125148.7f7d8ed6@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=boqun.feng@gmail$(echo .)com \
    --cc=dakr@kernel$(echo .)org \
    --cc=daniel.almeida@collabora$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lyude@redhat$(echo .)com \
    --cc=m.wilczynski@samsung$(echo .)com \
    --cc=ojeda@kernel$(echo .)org \
    --cc=pcolberg@redhat$(echo .)com \
    --cc=ukleinek@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox