From: David Miller <davem@davemloft.net>
To: valentin.longchamp@keymile.com
Cc: leoli@freescale.com, netdev@vger.kernel.org,
christophe.leroy@c-s.fr, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] net/ethernet/freescale: fix warning for ucc_geth
Date: Mon, 18 Sep 2017 14:56:47 -0700 (PDT) [thread overview]
Message-ID: <20170918.145647.945477632021094854.davem@davemloft.net> (raw)
In-Reply-To: <20170915055847.29716-1-valentin.longchamp@keymile.com>
From: Valentin Longchamp <valentin.longchamp@keymile.com>
Date: Fri, 15 Sep 2017 07:58:47 +0200
> uf_info.regs is resource_size_t i.e. phys_addr_t that can be either u32
> or u64 according to CONFIG_PHYS_ADDR_T_64BIT.
>
> The printk format is thus adaptet to u64 and the regs value cast to u64
> to take both u32 and u64 into account.
>
> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
Applied to net-next, thanks.
prev parent reply other threads:[~2017-09-18 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 5:58 [PATCH v2] net/ethernet/freescale: fix warning for ucc_geth Valentin Longchamp
2017-09-18 21:56 ` David Miller [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=20170918.145647.945477632021094854.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christophe.leroy@c-s.fr \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=valentin.longchamp@keymile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).