mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@ieee.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	broonie@kernel.org,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Alex Elder <elder@kernel.org>
Subject: Re: linux-next: Tree for Feb 23 (drivers/net/ipa/ipa_power.o)
Date: Thu, 24 Feb 2022 08:03:59 -0600	[thread overview]
Message-ID: <2c768b0f-316f-7227-6d87-2d1e875fcaaf@ieee.org> (raw)
In-Reply-To: <23f9d46a-4b33-6918-9c62-f417c624585c@infradead.org>

On 2/24/22 12:28 AM, Randy Dunlap wrote:
> 
> 
> On 2/23/22 17:44, broonie@kernel.org wrote:
>> Hi all,
>>
>> Note that today's -next again does not include the akpm tree since it's
>> been a long day and the conflicts especially with the mm code seemed
>> more than it was wise for me to attempt.  I'll have another go tomorrow
>> but no guarantees, I got further today.
>>
>> Changes since 20220222

Thanks, I'll investigate.	-Alex

> 
> on i386:
> 
> ld: drivers/net/ipa/ipa_power.o: in function `ipa_power_retention':
> ipa_power.c:(.text+0x57d): undefined reference to `qmp_send'
> ld: ipa_power.c:(.text+0x5d1): undefined reference to `qmp_send'
> ld: drivers/net/ipa/ipa_power.o: in function `ipa_power_init':
> ipa_power.c:(.text+0x823): undefined reference to `qmp_get'
> ld: drivers/net/ipa/ipa_power.o: in function `ipa_power_exit':
> ipa_power.c:(.text+0x954): undefined reference to `qmp_put'
> 
> 
> Full randconfig file is attached.
> 


      reply	other threads:[~2022-02-24 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  1:44 linux-next: Tree for Feb 23 broonie
2022-02-24  6:28 ` linux-next: Tree for Feb 23 (drivers/net/ipa/ipa_power.o) Randy Dunlap
2022-02-24 14:03   ` Alex Elder [this message]

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=2c768b0f-316f-7227-6d87-2d1e875fcaaf@ieee.org \
    --to=elder@ieee.org \
    --cc=broonie@kernel.org \
    --cc=elder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®