netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Networking <netdev@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Roman Gushchin <guro@fb.com>
Subject: linux-next: Fixes tag needs some work in the bpf tree
Date: Thu, 27 Jun 2019 08:05:21 +1000	[thread overview]
Message-ID: <20190627080521.5df8ccfc@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-06-26 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 22:05 Stephen Rothwell [this message]
2019-06-26 22:13 ` linux-next: Fixes tag needs some work in the bpf tree Roman Gushchin
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=20190627080521.5df8ccfc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=guro@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).