mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 1/2] include: kconfig.h: move __is_defined definition into new header
Date: Mon, 22 Apr 2024 14:16:44 +0200	[thread overview]
Message-ID: <171378820477.1550876.15192664380936086812.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240403072332.2694292-1-a.fatoum@pengutronix.de>


On Wed, 03 Apr 2024 09:23:31 +0200, Ahmad Fatoum wrote:
> While we run the preprocessor over device trees before compiling them,
> we don't define the Kconfig symbols and including <generated/autoconf.h>
> would fail.
> 
> The file defines __is_defined however, which can be useful for other
> macros that are either defined to 1 or undefined like the macros we
> define for device tree fragments to indicate which file they are being
> appended to. To make it possible to use __is_defined from fragments,
> move the kconfig-independent part out of <linux/kconfig.h> into
> <linux/is_defined.h>.
> 
> [...]

Applied, thanks!

[1/2] include: kconfig.h: move __is_defined definition into new header
      https://git.pengutronix.de/cgit/barebox/commit/?id=71b94b24f462 (link may not be stable)
[2/2] include: is_defined: implement __if_defined helper
      https://git.pengutronix.de/cgit/barebox/commit/?id=1674da1f95ce (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-04-22 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  7:23 Ahmad Fatoum
2024-04-03  7:23 ` [PATCH 2/2] include: is_defined: implement __if_defined helper Ahmad Fatoum
2024-04-22 12:16 ` Sascha Hauer [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=171378820477.1550876.15192664380936086812.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.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