All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mmc: tmio: Pass full address to tmio_sd_addr_is_dmaable()
Date: Tue, 9 Oct 2018 18:17:18 +0200	[thread overview]
Message-ID: <767dcaca-bd42-86f7-3b06-441caf1d93ea@gmail.com> (raw)
In-Reply-To: <CAK7LNASKBWA7Gq2V05W=ACMGh7KiZ5DJ3UXZzyMW2BOk5Xsydg@mail.gmail.com>

On 10/09/2018 05:35 PM, Masahiro Yamada wrote:
> On Tue, Oct 9, 2018 at 11:55 PM Marek Vasut <marek.vasut@gmail.com> wrote:
>>
>> On 10/09/2018 02:24 PM, Masahiro Yamada wrote:
>>> Hi Marek,
>>
>> Hi,
>>
>>> On Tue, Oct 9, 2018 at 8:26 PM Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>
>>>> Pass the entire source data pointer to tmio_sd_addr_is_dmaable()
>>>
>>>
>>> This statement sounds like
>>> the current code is passing the pointer address only partially.
>>> Is it right?
>>
>> With this change it is.
> 
> 
> Is anything wrong with my code?

Don't think so.

> How about your patch title
> "mmc: tmio: Pass full address to tmio_sd_addr_is_dmaable()" ?
> 
> Does it mean my code is not passing full address?

Could use a rephrasing, yeah

>>>> so we don't have to apply casts throughout the code.
>>>
>>> I do not understand this either
>>> since I see a cast in your code too.
>>
>> There is a cast, but it's isolated to this function.
>>
>>> In the previous code, the caller casts src->address
>>> when it passes it to tmio_sd_addr_is_dmaable().
>>>
>>> In the new code, 'src' is casted
>>> in tmio_sd_addr_is_dmaable().
>>>
>>> To me, you just moved the location of casting.
>>> What is the difference (i.e. benefit)?
>>
>> I moved the cast from the code into the function, which I think is cleaner.
> 
> I do not think so.

So would you prefer to see stuff like

function foo(long bar)
{...}

foo((cast)baz);

...

foo((cast)quux);

In the code  :)

> If you like this patch, just go for it.
> 
> But, I believe you need to update the patch title and description
> since this is just a matter of personal preference.
> 
> 


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2018-10-09 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 11:23 [U-Boot] [PATCH 1/2] mmc: tmio: Pass full address to tmio_sd_addr_is_dmaable() Marek Vasut
2018-10-09 11:23 ` [U-Boot] [PATCH 2/2] mmc: tmio: Limit DMA to 32bit on R-Car Gen3 Marek Vasut
2018-10-09 12:24 ` [U-Boot] [PATCH 1/2] mmc: tmio: Pass full address to tmio_sd_addr_is_dmaable() Masahiro Yamada
2018-10-09 14:55   ` Marek Vasut
2018-10-09 15:35     ` Masahiro Yamada
2018-10-09 16:17       ` Marek Vasut [this message]
2018-10-10  2:49         ` Masahiro Yamada
  -- strict thread matches above, loose matches on Subject: below --
2018-10-02 22:54 Marek Vasut
2018-10-03  2:17 ` Masahiro Yamada
2018-10-03  7:05   ` Marek Vasut

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=767dcaca-bd42-86f7-3b06-441caf1d93ea@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.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 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.