linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Asmaa Mnebhi <asmaa@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Sebastian Reichel <sre@kernel.org>
Cc: 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 battery tree
Date: Fri, 24 Jun 2022 12:44:32 +0000	[thread overview]
Message-ID: <CH2PR12MB38951BF631A307CD350B47A9D7B49@CH2PR12MB3895.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220624124730.3516928c@canb.auug.org.au>

I sent a patch on Tuesday and added you as a reviewer. Could you please take a look?
The name of the email/patch: "[PATCH v1 1/1] linux-next: Fix build failure in pwr-mlxbf.c"

Thanks.
Asmaa

-----Original Message-----
From: Stephen Rothwell <sfr@canb.auug.org.au> 
Sent: Thursday, June 23, 2022 10:48 PM
To: Sebastian Reichel <sre@kernel.org>
Cc: Asmaa Mnebhi <asmaa@nvidia.com>; 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 battery tree

Hi all,

On Mon, 20 Jun 2022 10:45:03 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> After merging the battery tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/power/reset/pwr-mlxbf.c: In function 'pwr_mlxbf_probe':
> drivers/power/reset/pwr-mlxbf.c:67:15: error: implicit declaration of function 'devm_work_autocancel' [-Werror=implicit-function-declaration]
>    67 |         err = devm_work_autocancel(dev, &priv->send_work, pwr_mlxbf_send_work);
>       |               ^~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   a4c0094fcf76 ("power: reset: pwr-mlxbf: add BlueField SoC power control driver")
> 
> I have used the battery tree from next-20220617 for today.

I am still seeing this failure.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2022-06-24 12:44 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  0:45 linux-next: build failure after merge of the battery tree Stephen Rothwell
2022-06-21 12:30 ` Asmaa Mnebhi
2022-06-24  2:47 ` Stephen Rothwell
2022-06-24 12:44   ` Asmaa Mnebhi [this message]
2022-06-28  2:30   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-08-21  2:57 Stephen Rothwell
2023-08-21  7:07 ` Lee Jones
2023-08-21  7:13   ` Lee Jones
2023-08-21 12:41     ` Rob Herring
2023-08-21 12:46       ` Lee Jones
2022-05-04  2:35 Stephen Rothwell
2019-12-19  0:01 Stephen Rothwell
2019-12-19  1:35 ` Sebastian Reichel
2019-06-28  4:03 Stephen Rothwell
2019-06-28 15:31 ` Sebastian Reichel
2019-06-28 16:56   ` Enric Balletbo i Serra
2019-06-29  0:33     ` Stephen Rothwell
2019-07-01 13:22       ` Enric Balletbo i Serra
2015-09-29  1:45 Stephen Rothwell
2015-10-02  1:49 ` Stephen Rothwell
2015-10-08  1:04   ` Stephen Rothwell
2015-10-08  6:12     ` Belisko Marek
2015-10-08 10:21       ` Stephen Rothwell
2015-10-15 14:26     ` Stephen Rothwell
2015-10-20 22:32       ` Stephen Rothwell
2015-10-21  6:12         ` Belisko Marek
2015-07-27  1:40 Stephen Rothwell
2012-07-16  4:09 Stephen Rothwell
2012-07-16  4:57 ` Chanwoo Choi
2012-03-15  2:56 Stephen Rothwell
2012-03-20  4:39 ` Stephen Rothwell
2012-03-26  2:13   ` Stephen Rothwell
2012-03-26  2:31     ` Arun MURTHY
2012-03-26  6:55       ` Linus Walleij
2012-03-26  8:36         ` Anton Vorontsov
2012-03-26  9:00         ` Samuel Ortiz
2012-03-26 16:11 ` Anton Vorontsov
2012-03-26 21:44   ` Stephen Rothwell
2012-03-26 21:47     ` Stephen Rothwell
2012-03-27 13:03     ` Anton Vorontsov
2012-03-28 11:38       ` Mark Brown
2012-01-09  2:11 Stephen Rothwell
2012-01-05  3:40 Stephen Rothwell
2012-01-05 15:25 ` Anton Vorontsov
2012-01-05 15:53   ` Greg KH
2012-01-07  9:00   ` Jeremy Fitzhardinge

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=CH2PR12MB38951BF631A307CD350B47A9D7B49@CH2PR12MB3895.namprd12.prod.outlook.com \
    --to=asmaa@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).