All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshul Dalal <anshuld@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, <u-boot@lists.denx.de>
Cc: <vigneshr@ti.com>, <trini@konsulko.com>
Subject: Re: [PATCH v1 1/2] dma: ti: k3-udma: fix dma_addr_t typecasts
Date: Thu, 28 Aug 2025 16:11:21 +0530	[thread overview]
Message-ID: <DCDZXBPHC0F2.1ZW2GO55LT7X9@ti.com> (raw)
In-Reply-To: <a20eaf48-6ff9-4b83-bd10-a8a99c9ace14@ti.com>

On Thu Aug 28, 2025 at 2:20 PM IST, Udit Kumar wrote:
>
> On 8/25/2025 7:02 PM, Anshul Dalal wrote:
>> With the change to dma_addr_t from u32 to u64 for the R5 SPL, the
>> existing typecasts from void* to int or vice-versa cause the compiler to
>> throw a "cast from pointer to integer of different size".
>
> is this some compiler specific ?. Please mention that
>
> I don't see this warning 
> https://gist.github.com/uditkumarti/1c4238a7101d97cdc57b7a40d10147d2
>
> I am on  gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)
>

Sorry for the confusing language in the commit description, this was a
preventative fix, it fixes the warnings that would've been emitted if
you had applied the second patch of the series by itself.

GCC 11 would still emit the warning if you apply only the second patch.

Regards,
Anshul

  reply	other threads:[~2025-08-28 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 13:32 [PATCH v1 0/2] Fix dma_addr_t for R5 SPL Anshul Dalal
2025-08-25 13:32 ` [PATCH v1 1/2] dma: ti: k3-udma: fix dma_addr_t typecasts Anshul Dalal
2025-08-27 16:14   ` Prasanth Mantena
2025-08-28  5:01     ` Anshul Dalal
2025-08-28  8:13       ` Anshul Dalal
2025-08-28  8:50   ` Kumar, Udit
2025-08-28 10:41     ` Anshul Dalal [this message]
2025-08-25 13:32 ` [PATCH v1 2/2] config: arch: k3: enable DMA_ADDR_T_64BIT Anshul Dalal

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=DCDZXBPHC0F2.1ZW2GO55LT7X9@ti.com \
    --to=anshuld@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.