From: Lee Jones <lee@kernel•org>
To: "Heiko Stübner" <heiko@sntech•de>
Cc: Srinivas Kandagatla <srini@kernel•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the nvmem tree
Date: Wed, 20 Aug 2025 08:14:19 +0100 [thread overview]
Message-ID: <20250820071419.GI7508@google.com> (raw)
In-Reply-To: <3593278.som1txNFv6@diego>
On Tue, 19 Aug 2025, Heiko Stübner wrote:
> Am Dienstag, 19. August 2025, 15:58:32 Mitteleuropäische Sommerzeit schrieb Srinivas Kandagatla:
> >
> > On 8/19/25 2:54 PM, Heiko Stübner wrote:
> > > Am Dienstag, 19. August 2025, 13:22:04 Mitteleuropäische Sommerzeit schrieb Srinivas Kandagatla:
> > >> On 8/19/25 12:14 PM, Heiko Stübner wrote:
> > >>> Hi,
> > >>>
> > >>> Am Dienstag, 19. August 2025, 05:40:39 Mitteleuropäische Sommerzeit schrieb Stephen Rothwell:
> > >>>> After merging the nvmem tree, today's linux-next build (x86_64
> > >>>> allmodconfig) failed like this:
> > >>>>
> > >>>> In file included from drivers/nvmem/qnap-mcu-eeprom.c:12:
> > >>>> include/linux/mfd/qnap-mcu.h:13:9: error: unknown type name 'u32'
> > >>>> 13 | u32 baud_rate;
> > >>>> | ^~~
> > >>>
> > >>> [...]
> > >>>
> > >>>>
> > >>>> Caused by commit
> > >>>>
> > >>>> 117c3f3014a9 ("nvmem: add driver for the eeprom in qnap-mcu controllers")
> > >>>>
> > >>>> I have used the nvmem tree from next-20250818 for today.
> > >>>
> > >>> bah, sorry about messing this up.
> > >>>
> > >>> While I encountered this, and fixed that with the pending
> > >>> https://lore.kernel.org/all/20250804130726.3180806-2-heiko@sntech.de/
> > >>>
> > >>> I completely missed that the nvmem driver applied alone would break
> > >>> without that change :-( .
> > >>
> > >> I have now reverted this change, @Heiko Please let me know if you want
> > >> to take this to mfd tree or vice-versa.
> > >
> > > ok, no worries :-) .
> > >
> > > I guess for now, I'll just make sure the header patch gets somewhere.
> > > And I guess I'll re-try the nvmem driver once that has happened,
> > > probably for the next cycle.
> >
> > I don't think we need to wait till next cycle, Lee can pick up this
> > patch via mfd tree if header change is going via mfd tree.
>
> Okay ... if that is fine with you then great.
>
> I guess for less confusion, I'll re-submit the driver, reference the header
> patch it needs and you can Ack it to go via the mfd tree.
Sounds fine.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-08-20 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 3:40 linux-next: build failure after merge of the nvmem tree Stephen Rothwell
2025-08-19 11:14 ` Heiko Stübner
2025-08-19 11:22 ` Srinivas Kandagatla
2025-08-19 13:54 ` Heiko Stübner
2025-08-19 13:58 ` Srinivas Kandagatla
2025-08-19 14:49 ` Heiko Stübner
2025-08-20 7:14 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 5:49 Stephen Rothwell
2023-12-11 10:23 ` Srinivas Kandagatla
2023-12-11 10:30 ` Miquel Raynal
2023-12-11 11:10 ` Srinivas Kandagatla
2023-12-11 13:53 ` Miquel Raynal
2023-08-15 10:25 Stephen Rothwell
2023-08-20 23:48 ` Stephen Rothwell
2023-08-21 5:27 ` Komal Bajaj
2022-11-01 3:21 Stephen Rothwell
2022-11-01 7:27 ` Srinivas Kandagatla
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=20250820071419.GI7508@google.com \
--to=lee@kernel$(echo .)org \
--cc=heiko@sntech$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=srini@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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