All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] rxrpc: More fixes and adjustments
Date: Tue, 04 Oct 2016 20:10:51 -0400 (EDT)	[thread overview]
Message-ID: <20161004.201051.821616397135404483.davem@davemloft.net> (raw)
In-Reply-To: <10083.1475596890@warthog.procyon.org.uk>

From: David Howells <dhowells@redhat.com>
Date: Tue, 04 Oct 2016 17:01:30 +0100

> What's the procedure for sending more fixes at this point?  Do I send them
> against net-next, since net doesn't contain the things to be fixed yet, or do
> I wait for net to catch up?

I'm sending Linus a pull request later today for the stuff in net-next,
and once he takes that all the trees will be synced up and you can start
sending fixes.

Thanks.

      reply	other threads:[~2016-10-05  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 21:40 [PATCH net-next 0/7] rxrpc: More fixes and adjustments David Howells
2016-09-30 21:40 ` [PATCH net-next 1/7] rxrpc: Actually display the tx_data trace retransmission note David Howells
2016-09-30 21:40 ` [PATCH net-next 2/7] rxrpc: Switch to Congestion Avoidance mode at cwnd==ssthresh David Howells
2016-09-30 21:40 ` [PATCH net-next 3/7] rxrpc: Reduce ssthresh to peer's receive window David Howells
2016-09-30 21:40 ` [PATCH net-next 4/7] rxrpc: The offset field in struct rxrpc_skb_priv is unnecessary David Howells
2016-09-30 21:40 ` [PATCH net-next 5/7] rxrpc: Remove error from struct rxrpc_skb_priv as it is unused David Howells
2016-09-30 21:40 ` [PATCH net-next 6/7] rxrpc: Keep the call timeouts as ktimes rather than jiffies David Howells
2016-09-30 21:41 ` [PATCH net-next 7/7] rxrpc: Fix the call timer handling David Howells
2016-10-03  6:02 ` [PATCH net-next 0/7] rxrpc: More fixes and adjustments David Miller
2016-10-04 16:01 ` David Howells
2016-10-05  0:10   ` 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=20161004.201051.821616397135404483.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.