From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] resource: add CONFIG_DEBUG_RESOURCES option
Date: Wed, 24 Jul 2024 10:14:59 +0200 [thread overview]
Message-ID: <172180889900.2024147.804588991586173266.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240722170641.3868698-1-a.fatoum@pengutronix.de>
On Mon, 22 Jul 2024 19:06:41 +0200, Ahmad Fatoum wrote:
> Whether a resource conflict is indeed a problem depends on how the user
> handles it. Most users will propagate an -EBUSY error, but some will
> gracefully handle it and move on.
>
> We thus can't just warn unconditionally about conflicts in __request_region.
> It's still useful to enable warnings there though while debugging, so
> let's add a Kconfig option that enables these debugging prints.
>
> [...]
Applied, thanks!
[1/1] resource: add CONFIG_DEBUG_RESOURCES option
https://git.pengutronix.de/cgit/barebox/commit/?id=aafcfb061c98 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-07-24 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 17:06 Ahmad Fatoum
2024-07-24 8:14 ` 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=172180889900.2024147.804588991586173266.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