From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Daniel Gomez <daniel@qtec.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: designware: Add base addr info
Date: Sat, 27 Mar 2021 21:03:48 +0200 [thread overview]
Message-ID: <CAHp75Vf=kL7sKrRG4HCD9AT0zzsOEHHT4=CpZV7Z7B8mX64ubw@mail.gmail.com> (raw)
In-Reply-To: <CAH1Ww+Q8-YD_jc5Pkk3PG4M5vCiisnbpmd2zx0GQsaa_=si0ig@mail.gmail.com>
On Sat, Mar 27, 2021 at 8:18 PM Daniel Gomez <daniel@qtec.com> wrote:
> On Fri, 26 Mar 2021 at 13:28, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Fri, Mar 26, 2021 at 11:35:08AM +0100, Daniel Gomez wrote:
...
> > It's a good question. On one hand we know that resource_size_t is a simple
> > redefinition of phys_addr_t, but it might be changed in the future. OTOH,
> > struct resource has types of resource_size_t. In any case it's a type that is
> > platform dependent (like long, size_t). Hence, the special specifier is needed.
>
> This 'issue' occurs in other subsystems like iio but I can see the
> patches are quite old in comparison with the i2c-tegra one.
> Also, the same happens when they print the variable (wrong specifier).
Now since you have better understanding you may clean those up!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-03-27 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:12 [PATCH] i2c: designware: Add base addr info Daniel Gomez
2021-03-25 15:43 ` Andy Shevchenko
2021-03-26 10:35 ` Daniel Gomez
2021-03-26 12:28 ` Andy Shevchenko
2021-03-27 18:15 ` Daniel Gomez
2021-03-27 19:03 ` Andy Shevchenko [this message]
2021-03-26 1:50 ` kernel test robot
2021-03-26 1:50 ` kernel test robot
2021-03-29 15:59 ` kernel test robot
2021-03-29 15:59 ` kernel test robot
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='CAHp75Vf=kL7sKrRG4HCD9AT0zzsOEHHT4=CpZV7Z7B8mX64ubw@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@qtec.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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.