From: Roman Gushchin <guro@fb•com>
To: Alexei Starovoitov <ast@kernel•org>
Cc: Daniel Borkmann <daniel@iogearbox•net>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Networking <netdev@vger•kernel.org>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the bpf tree
Date: Wed, 26 Jun 2019 22:13:51 +0000 [thread overview]
Message-ID: <20190626221347.GA17762@tower.DHCP.thefacebook.com> (raw)
In-Reply-To: <20190627080521.5df8ccfc@canb.auug.org.au>
On Thu, Jun 27, 2019 at 08:05:21AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 12771345a467 ("bpf: fix cgroup bpf release synchronization")
>
> Fixes tag
>
> Fixes: 4bfc0bb2c60e ("bpf: decouple the lifetime of cgroup_bpf from
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please don't split Fixes tags across more than one line.
Oops, sorry.
Alexei, can you fix this in place?
Or should I send an updated version?
Thanks.
next prev parent reply other threads:[~2019-06-26 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 22:05 linux-next: Fixes tag needs some work in the bpf tree Stephen Rothwell
2019-06-26 22:13 ` Roman Gushchin [this message]
2019-06-26 23:36 ` Alexei Starovoitov
2019-06-26 23:43 ` Roman Gushchin
2019-06-27 1:45 ` Stephen Rothwell
2019-06-27 22:25 ` Daniel Borkmann
2019-06-27 22:43 ` Roman Gushchin
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 22:08 Stephen Rothwell
2019-06-11 10:05 Stephen Rothwell
2019-06-12 14:58 ` Daniel Borkmann
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=20190626221347.GA17762@tower.DHCP.thefacebook.com \
--to=guro@fb$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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