All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jian Zhang <zhangjian.3032@bytedance.com>,
	Corey Minyard <corey@minyard.net>
Cc: 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 ipmi tree
Date: Fri, 3 Apr 2026 15:01:18 +0100	[thread overview]
Message-ID: <ac_ILgraQZ1KcNDF@sirena.org.uk> (raw)

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

Hi all,

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

/tmp/next/build/drivers/char/ipmi/ssif_bmc.c: In function 'ssif_bmc_remove': 
/tmp/next/build/drivers/char/ipmi/ssif_bmc.c:865:9: error: implicit declaration of function 'del_timer_sync' [-Wimplicit-function-declaration]
  865 |         del_timer_sync(&ssif_bmc->response_timer);
      |         ^~~~~~~~~~~~~~

Caused by commit

  e1748349a14d3 (ipmi: ssif_bmc: cancel response timer on remove)

I have used the version from next-20260402 instead.

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

             reply	other threads:[~2026-04-03 14:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 14:01 Mark Brown [this message]
2026-04-03 15:41 ` linux-next: build failure after merge of the ipmi tree Corey Minyard
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04  1:48 Stephen Rothwell
2022-11-04  2:14 ` Corey Minyard
2021-10-01  2:52 Stephen Rothwell
2021-10-01 12:15 ` Corey Minyard
2020-04-20  3:09 Stephen Rothwell
2020-04-20  3:51 ` Feng Tang
2019-04-03  3:33 Stephen Rothwell
2019-04-03 20:27 ` Corey Minyard
2019-04-03 21:12   ` Corey Minyard
2019-04-04  0:14     ` Paul E. McKenney
2017-09-28  4:45 Stephen Rothwell
2017-09-28 17:34 ` Corey Minyard
2014-12-17  3:03 Stephen Rothwell
2014-12-17  4:22 ` Corey Minyard
2014-11-17  8:20 Stephen Rothwell
2014-11-17  8:14 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=ac_ILgraQZ1KcNDF@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=corey@minyard.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=zhangjian.3032@bytedance.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.