netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: peterz@infradead.org,
	Network Development <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH] locking/static_key: always define static_branch_deferred_inc
Date: Wed, 12 Jun 2019 16:25:16 -0400	[thread overview]
Message-ID: <CAF=yD-JAZfEG5JoNEQn60gnucJB1gsrFeT38DieG12NQb9DFnQ@mail.gmail.com> (raw)
In-Reply-To: <20190612125911.509d79f2@cakuba.netronome.com>

On Wed, Jun 12, 2019 at 3:59 PM Jakub Kicinski
<jakub.kicinski@netronome.com> wrote:
>
> On Wed, 12 Jun 2019 15:44:09 -0400, Willem de Bruijn wrote:
> > From: Willem de Bruijn <willemb@google.com>
> >
> > This interface is currently only defined if CONFIG_JUMP_LABEL. Make it
> > available also when jump labels are disabled.
> >
> > Fixes: ad282a8117d50 ("locking/static_key: Add support for deferred static branches")
> > Signed-off-by: Willem de Bruijn <willemb@google.com>
> >
> > ---
> >
> > The original patch went into 5.2-rc1, but this interface is not yet
> > used, so this could target either 5.2 or 5.3.
>
> Can we drop the Fixes tag?  It's an ugly omission but not a bug fix.
>
> Are you planning to switch clean_acked_data_enable() to the helper once
> merged?

Definitely, can do.

Perhaps it's easiest to send both as a single patch set through net-next, then?

  reply	other threads:[~2019-06-12 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 19:44 [PATCH] locking/static_key: always define static_branch_deferred_inc Willem de Bruijn
2019-06-12 19:59 ` Jakub Kicinski
2019-06-12 20:25   ` Willem de Bruijn [this message]
2019-06-12 20:56     ` Jakub Kicinski
2019-06-13  9:33       ` Peter Zijlstra
2019-06-13 15:10         ` Willem de Bruijn

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='CAF=yD-JAZfEG5JoNEQn60gnucJB1gsrFeT38DieG12NQb9DFnQ@mail.gmail.com' \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=willemb@google.com \
    /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).