mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master 1/2] list: fix CONFIG_DEBUG_LIST link failure in PBL
Date: Fri, 17 May 2024 08:02:04 +0200	[thread overview]
Message-ID: <4bd8c696-762a-46ed-9835-db41b96dda1f@pengutronix.de> (raw)
In-Reply-To: <ZkWy30HxMC9dNAgB@pengutronix.de>

On 16.05.24 09:16, Sascha Hauer wrote:
> On Wed, May 15, 2024 at 08:07:57AM +0200, Ahmad Fatoum wrote:
>> With the addition of PBL handoff data, we now use <linux/list.h> in PBL.
>> This works fine with CONFIG_DEBUG_LIST disabled, because all functions are
>> inlined, but when building with the option enabled, references to the
>> out-of-line sanity checking functions breaks the build.
>>
>> Fix this by omitting these references when building for PBL.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>>  include/linux/list.h | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/list.h b/include/linux/list.h
>> index 2b3a39ea81e8..e47a8188e807 100644
>> --- a/include/linux/list.h
>> +++ b/include/linux/list.h
>> @@ -36,7 +36,7 @@ static inline void INIT_LIST_HEAD(struct list_head *list)
>>  	list->prev = list;
>>  }
>>  
>> -#ifdef CONFIG_DEBUG_LIST
>> +#if defined(CONFIG_DEBUG_LIST) && !defined(__PBL__)
>>  extern bool __list_add_valid_or_report(struct list_head *new,
>>  				       struct list_head *prev,
>>  				       struct list_head *next);
> 
> What about compiling list_debug.o for PBL as well?

I'd prefer we use singly linked lists instead, but I want to fix the
build error first.

Thanks,
Ahmad

> 
> Sascha
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2024-05-17  6:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  6:07 Ahmad Fatoum
2024-05-15  6:07 ` [PATCH master 2/2] pblimage: ls1028a: fix handling of short reads on Ahmad Fatoum
2024-05-16  7:16 ` [PATCH master 1/2] list: fix CONFIG_DEBUG_LIST link failure in PBL Sascha Hauer
2024-05-17  6:02   ` Ahmad Fatoum [this message]
2024-05-21 11:04 ` Sascha Hauer

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=4bd8c696-762a-46ed-9835-db41b96dda1f@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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