netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: brouer@redhat.com
Cc: alexei.starovoitov@gmail.com, borkmann@iogearbox.net,
	netdev@vger.kernel.org
Subject: Re: When is net fixes getting merged into net-next and bpf-next
Date: Thu, 01 Mar 2018 13:06:08 -0500 (EST)	[thread overview]
Message-ID: <20180301.130608.1315053433159226013.davem@davemloft.net> (raw)
In-Reply-To: <20180301184557.439bbb7b@redhat.com>

From: Jesper Dangaard Brouer <brouer@redhat.com>
Date: Thu, 1 Mar 2018 18:45:57 +0100

> Hi Maintainers,
> 
> I'm working on a patchset based on bpf-next, but I'm starting to
> conflict with my own fixes patches that are only in the net git tree...

net got merged into net-next just last weekend

I only merge net into net-next when I send a pull request to Linus, he
takes it, and I can fast forward net.

      reply	other threads:[~2018-03-01 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 17:45 When is net fixes getting merged into net-next and bpf-next Jesper Dangaard Brouer
2018-03-01 18:06 ` 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=20180301.130608.1315053433159226013.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=borkmann@iogearbox.net \
    --cc=brouer@redhat.com \
    --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).