mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kuehling, Felix" <felix.kuehling@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Cc: "Christian König" <christian.koenig@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>
Subject: Re: [PATCH v1 1/1] drm/amdkfd: Do not use internal implementation of tolower()
Date: Wed, 21 Oct 2026 11:43:10 -0400	[thread overview]
Message-ID: <b44fb51c-11f7-4332-8ac6-d260f6904dfc@amd.com> (raw)
In-Reply-To: <20261021084639.251366-1-andriy.shevchenko@linux.intel.com>

On 2026-10-21 04:46, Andy Shevchenko wrote:
> ctype.h provides tolower() macro specifically for the cases
> that might be architecture-optimised. Using __tolower(),
> which is internal implementation, needs a good justification,
> as this driver is the only user of that and there is no evidence
> it's required.
>
> Note, currently it's no difference as the macro always defined
> to the internal implementation, but it might change in the future.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Thanks. I'm applying the patch to amd-staging-drm-next.

Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>


> ---
>   drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> index 35b3abe57b80..1ef4d26a0ac6 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
> @@ -2091,7 +2091,7 @@ int kfd_topology_add_device(struct kfd_node *gpu)
>   	 * needed for the topology
>   	 */
>   	for (i = 0; i < KFD_TOPOLOGY_PUBLIC_NAME_SIZE-1; i++) {
> -		dev->node_props.name[i] = __tolower(asic_name[i]);
> +		dev->node_props.name[i] = tolower(asic_name[i]);
>   		if (asic_name[i] == '\0')
>   			break;
>   	}

      reply	other threads:[~2026-10-21 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  8:46 Andy Shevchenko
2026-10-21 15:43 ` Kuehling, Felix [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=b44fb51c-11f7-4332-8ac6-d260f6904dfc@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simona@ffwll.ch \
    /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®