From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tejun Heo <tj@kernel•org>
Cc: Tamir Duberstein <tamird@gmail•com>,
Benno Lossin <benno.lossin@proton•me>,
Alice Ryhl <aliceryhl@google•com>,
Andreas Hindborg <a.hindborg@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
helpdesk@kernel•org
Subject: Re: linux-next: build failure after merge of the workqueues tree
Date: Thu, 17 Apr 2025 16:35:30 +1000 [thread overview]
Message-ID: <20250417163530.3beb3e65@canb.auug.org.au> (raw)
In-Reply-To: <aACcc6VmbON_fy3J@slm.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
Hi Tejun,
On Wed, 16 Apr 2025 20:15:15 -1000 Tejun Heo <tj@kernel•org> wrote:
>
> On Thu, Apr 17, 2025 at 02:26:36PM +1000, Stephen Rothwell wrote:
> ...
> > I am still seeing this failure. Forgot to push out?
>
> Hah, we might be seeing some caching problem.
>
> htejun@slm ~/o/wq (for-next)> git rev-list for-next \^master --oneline
> 24cdab5787a0 workqueue: Better document teardown for delayed_work
> htejun@slm ~/o/wq (for-next)> git push git@gitolite•kernel.org:pub/scm/linux/kernel/git/tj/wq.git for-next:for-next
> Everything up-to-date
> htejun@slm ~/o/wq (for-next)> git fetch -f git@gitolite•kernel.org:pub/scm/linux/kernel/git/tj/wq.git for-next:tmp
> htejun@slm ~/o/wq (for-next)> git rev-list tmp \^master --oneline
> 24cdab5787a0 workqueue: Better document teardown for delayed_work
> htejun@slm ~/o/wq (for-next)> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-next:tmp2
> From https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
> * [new branch] for-next -> tmp2
> htejun@slm ~/o/wq (for-next)> git rev-list tmp2 \^master --oneline
> 2762750ac5c6 workqueue: Better document teardown for delayed_work
> 345e029b561e rust: workqueue: remove HasWork::OFFSET
>
> Cc'ing helpdesk@kernel•org. Imma leave the tree as-is for debugging. The
> tree only has a documentation patch, so it's fine to skip for linux-next for
> now. I'll wait a couple days and if the problem doesn't get resolved, I'll
> try to update the branch and see whether the stale cache clears.
Thanks for checking. I have a few days off now, so I guess we will see
what it is like on (my) Tuesday.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-17 6:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 4:01 linux-next: build failure after merge of the workqueues tree Stephen Rothwell
2025-04-15 13:24 ` Tamir Duberstein
2025-04-15 14:59 ` Tejun Heo
2025-04-17 4:26 ` Stephen Rothwell
2025-04-17 6:15 ` Tejun Heo
2025-04-17 6:35 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-02 3:34 Stephen Rothwell
2017-11-03 13:59 ` Tejun Heo
2015-06-20 10:26 Stephen Rothwell
2011-02-18 3:57 Stephen Rothwell
2011-02-18 9:07 ` Tejun Heo
2011-02-21 2:27 ` Stephen Rothwell
2011-02-21 5:48 ` Dmitry Torokhov
2011-02-17 3:33 Stephen Rothwell
2011-02-17 9:23 ` Tejun Heo
2011-02-09 4:12 Stephen Rothwell
2011-02-09 8:37 ` Tejun Heo
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=20250417163530.3beb3e65@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=a.hindborg@kernel$(echo .)org \
--cc=aliceryhl@google$(echo .)com \
--cc=benno.lossin@proton$(echo .)me \
--cc=helpdesk@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tamird@gmail$(echo .)com \
--cc=tj@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