From: David Miller <davem@davemloft.net>
To: bvanassche@acm.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/7] net/core patches for kernel v5.2
Date: Sat, 23 Mar 2019 20:47:29 -0400 (EDT) [thread overview]
Message-ID: <20190323.204729.1480728626422978875.davem@davemloft.net> (raw)
In-Reply-To: <20190321221946.163803-1-bvanassche@acm.org>
From: Bart Van Assche <bvanassche@acm.org>
Date: Thu, 21 Mar 2019 15:19:39 -0700
> While inspecting the code of inet6_pton() I found an open-coded strlcpy()
> implementation in that function. The last patch in this series simplifies
> inet6_pton() and the first six patches address the compiler warnings reported
> when building the code in net/core with W=1. Please consider this patch
> series for kernel v5.2.
Please drop patch #6 and respond to the feedback for patch #7.
Thanks.
prev parent reply other threads:[~2019-03-24 0:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 22:19 [PATCH 0/7] net/core patches for kernel v5.2 Bart Van Assche
2019-03-21 22:19 ` [PATCH 1/7] net/core: Document reuseport_add_sock() bind_inany argument Bart Van Assche
2019-03-21 22:19 ` [PATCH 2/7] net/core: Document all dev_ioctl() arguments Bart Van Assche
2019-03-21 22:19 ` [PATCH 3/7] net/core: Document __skb_flow_dissect() flags argument Bart Van Assche
2019-03-21 22:19 ` [PATCH 4/7] net/core: Fix rtnetlink kernel-doc headers Bart Van Assche
2019-03-21 22:19 ` [PATCH 5/7] net/core: Allow the compiler to verify declaration and definition consistency Bart Van Assche
2019-03-21 22:19 ` [PATCH 6/7] net/core: Declare a local function 'static' Bart Van Assche
2019-03-21 22:25 ` Sagi Grimberg
2019-03-21 22:19 ` [PATCH 7/7] net/utils: Use strlcpy() instead of open-coding it Bart Van Assche
2019-03-21 22:24 ` Sagi Grimberg
2019-03-22 18:46 ` Rustad, Mark D
2019-03-25 15:55 ` Bart Van Assche
2019-03-24 0: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=20190323.204729.1480728626422978875.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bvanassche@acm.org \
--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).