From: Ole Schuerks <ole0811sch@gmail.com>
To: mcgrof@kernel.org
Cc: deltaone@debian.org, jan.sollmann@rub.de, jude.gyimah@rub.de,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
masahiroy@kernel.org, nathan@kernel.org, nicolas@fjasle.eu,
ole0811sch@gmail.com, thorsten.berger@rub.de
Subject: Re: [PATCH v6 02/11] kbuild: Add list_size, list_at_index, list_for_each_from
Date: Mon, 9 Dec 2024 02:00:19 +0100 [thread overview]
Message-ID: <20241209010019.52601-1-ole0811sch@gmail.com> (raw)
In-Reply-To: <Z1DjikoDzwIAID5T@bombadil.infradead.org>
> What's wrong with list_count_nodes()?
> list_for_each_entry_from() exists on my tree on linux-next added
> through commit e229c2fb3370a ("[LIST]: Introduce
> list_for_each_entry_from") since v2.6.17, so since 2006.
These macros only exist in include/linux/list.h, not in
scripts/include/list.h. My assumption was that the build system should only
use scripts/include/list.h.
> I'd just keep thsi internal to your code for now, and later if we really
> want we can add this as a generic helper.
Alright, the additions will be internals in v7.
Best regards,
Ole Schuerks
next prev parent reply other threads:[~2024-12-09 1:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 3:49 [PATCH v6 00/11] kbuild, kconfig: Add support for conflict resolution Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 01/11] kconfig: Add PicoSAT interface Ole Schuerks
2024-12-04 23:07 ` Luis Chamberlain
2024-12-09 0:57 ` Ole Schuerks
2024-12-11 3:48 ` Luis Chamberlain
2024-10-28 3:49 ` [PATCH v6 02/11] kbuild: Add list_size, list_at_index, list_for_each_from Ole Schuerks
2024-12-04 23:19 ` Luis Chamberlain
2024-12-09 1:00 ` Ole Schuerks [this message]
2024-12-11 3:49 ` Luis Chamberlain
2024-10-28 3:49 ` [PATCH v6 03/11] kconfig: Add definitions Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 04/11] kconfig: Add files for building constraints Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 05/11] kconfig: Add files for handling expressions Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 06/11] kconfig: Add files for RangeFix Ole Schuerks
2024-12-04 23:23 ` Luis Chamberlain
2024-10-28 3:49 ` [PATCH v6 07/11] kconfig: Add files with utility functions Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 08/11] kconfig: Add tools Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 09/11] kconfig: Add xconfig-modifications Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 10/11] kconfig: Add loader.gif Ole Schuerks
2024-10-28 3:49 ` [PATCH v6 11/11] kconfig: Add documentation for the conflict resolver Ole Schuerks
2024-12-04 22:58 ` [PATCH v6 00/11] kbuild, kconfig: Add support for conflict resolution Luis Chamberlain
2024-12-04 23:26 ` Luis Chamberlain
2025-01-09 13:28 ` [PATCH v6 01/11] kconfig: Add PicoSAT interface Brendan Jackman
2025-01-10 19:15 ` Luis Chamberlain
2025-01-13 16:29 ` Brendan Jackman
2025-02-07 15:43 ` Thorsten Berger
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=20241209010019.52601-1-ole0811sch@gmail.com \
--to=ole0811sch@gmail.com \
--cc=deltaone@debian.org \
--cc=jan.sollmann@rub.de \
--cc=jude.gyimah@rub.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=thorsten.berger@rub.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