From: David Miller <davem@davemloft.net>
To: bkenward@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
kbuild-all@01.org, fengguang.wu@intel.com
Subject: Re: [PATCH net-next] sfc: add suffix to large constant in ptp
Date: Fri, 26 Jan 2018 10:47:22 -0500 (EST) [thread overview]
Message-ID: <20180126.104722.491351950116967372.davem@davemloft.net> (raw)
In-Reply-To: <37eafd9c-01de-5cd2-63f8-f3339e5b5fd7@solarflare.com>
From: Bert Kenward <bkenward@solarflare.com>
Date: Fri, 26 Jan 2018 08:51:47 +0000
> Fixes: 1280c0f8aafc ("sfc: support second + quarter ns time format for receive datapath")
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Bert Kenward <bkenward@solarflare.com>
Applied.
prev parent reply other threads:[~2018-01-26 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 22:33 [net-next:master 1917/1931] drivers/net/ethernet/sfc/ptp.c:646:3: warning: this decimal constant is unsigned only in ISO C90 kbuild test robot
2018-01-26 8:51 ` [PATCH net-next] sfc: add suffix to large constant in ptp Bert Kenward
2018-01-26 15:47 ` 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=20180126.104722.491351950116967372.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bkenward@solarflare.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
/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).