From: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: Re: [PATCH net-next] net: Use __u32 in uapi net_stamp.h
Date: Mon, 9 Jul 2018 16:20:28 -0700 [thread overview]
Message-ID: <f5371949-9c27-8c38-bfe5-c05456244168@intel.com> (raw)
In-Reply-To: <93e9a7b8-4d6b-5772-9a7c-27c766fee50c@gmail.com>
On 07/09/2018 04:18 PM, Eric Dumazet wrote:
>
>
> On 07/09/2018 04:08 PM, Jesus Sanchez-Palencia wrote:
>> We are not supposed to use u32 in uapi, so change the flags member of
>> struct sock_txtime from u32 to __u32 instead.
>>
>> Fixes: 80b14dee2bea ("net: Add a new socket option for a future transmit time")
>> Signed-off-by: Jesus Sanchez-Palencia <jesus.sanchez-palencia@intel.com>
>
> Could you use this patch as an opportunity to tab-align the fields names ?
>
> Also you can credit the reporter, as in :
>
> Reported-by: Eric Dumazet <edumazet@google.com>
>
Sure
> Thanks !
>
prev parent reply other threads:[~2018-07-09 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 23:08 [PATCH net-next] net: Use __u32 in uapi net_stamp.h Jesus Sanchez-Palencia
2018-07-09 23:18 ` Eric Dumazet
2018-07-09 23:20 ` Jesus Sanchez-Palencia [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=f5371949-9c27-8c38-bfe5-c05456244168@intel.com \
--to=jesus.sanchez-palencia@intel.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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).