From: Francis Laniel <laniel_francis@privacyrequired.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH v5 0/3] Fix inefficiences and rename nla_strlcpy
Date: Mon, 16 Nov 2020 18:06:33 +0100 [thread overview]
Message-ID: <3291815.yzSIL3OBH5@machine> (raw)
In-Reply-To: <20201116080652.5eae929c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Le lundi 16 novembre 2020, 17:06:52 CET Jakub Kicinski a écrit :
> On Sun, 15 Nov 2020 18:05:39 +0100 Francis Laniel wrote:
> > Le dimanche 15 novembre 2020, 01:18:37 CET Jakub Kicinski a écrit :
> > > On Fri, 13 Nov 2020 10:56:26 -0800 Kees Cook wrote:
> > > > Thanks! This looks good to me.
> > > >
> > > > Jakub, does this look ready to you?
> > >
> > > Yup, looks good, sorry!
> > >
> > > But it didn't get into patchwork cleanly :/
> > >
> > > One more resend please? (assuming we're expected to take this
> > > into net-next)
> >
> > I will send it again and tag it for net-next.
> >
> > Just to know, is patchwork this:
> > https://patchwork.kernel.org/project/netdevbpf/list/
>
> Yes, that's the one.
OK! The tool seems cool.
So normally I resend the patches, but I do not see them in patchwork.
Is there something am I supposed to do so they can be visible through
patchwork?
next prev parent reply other threads:[~2020-11-16 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 11:11 [PATCH v5 0/3] Fix inefficiences and rename nla_strlcpy laniel_francis
2020-11-13 11:11 ` [PATCH v5 1/3] Fix unefficient call to memset before memcpu in nla_strlcpy laniel_francis
2020-11-13 11:11 ` [PATCH v5 2/3] Modify return value of nla_strlcpy to match that of strscpy laniel_francis
2020-11-13 11:11 ` [PATCH v5 3/3] treewide: rename nla_strlcpy to nla_strscpy laniel_francis
2020-11-13 18:56 ` [PATCH v5 0/3] Fix inefficiences and rename nla_strlcpy Kees Cook
2020-11-15 0:18 ` Jakub Kicinski
2020-11-15 17:05 ` Francis Laniel
2020-11-16 16:06 ` Jakub Kicinski
2020-11-16 17:06 ` Francis Laniel [this message]
2020-11-16 17:32 ` Jakub Kicinski
2020-11-16 18:18 ` Francis Laniel
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=3291815.yzSIL3OBH5@machine \
--to=laniel_francis@privacyrequired.com \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.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).