All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	yuehaibing@huawei.com
Subject: Re: [PATCHv2 RFC net-next 0/7] net: dst_confirm replacement
Date: Tue, 31 Jan 2017 23:53:17 +0200 (EET)	[thread overview]
Message-ID: <alpine.LFD.2.11.1701312350110.2064@ja.home.ssi.bg> (raw)
In-Reply-To: <20170130.101339.2050288140097606206.davem@davemloft.net>


	Hello,

On Mon, 30 Jan 2017, David Miller wrote:

> From: Julian Anastasov <ja@ssi.bg>
> > 
> > 	So, the following solution is to avoid using
> > dst->pending_confirm.
> 
> For the most part this series looks good to me, nice work.

	OK, I'm posting v3 after removing the RFC tag from v2,
I just added the Acked-by tags.

Regards

WARNING: multiple messages have this Message-ID (diff)
From: Julian Anastasov <ja@ssi.bg>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	yuehaibing@huawei.com
Subject: Re: [PATCHv2 RFC net-next 0/7] net: dst_confirm replacement
Date: Tue, 31 Jan 2017 21:53:17 +0000	[thread overview]
Message-ID: <alpine.LFD.2.11.1701312350110.2064@ja.home.ssi.bg> (raw)
In-Reply-To: <20170130.101339.2050288140097606206.davem@davemloft.net>


	Hello,

On Mon, 30 Jan 2017, David Miller wrote:

> From: Julian Anastasov <ja@ssi.bg>
> > 
> > 	So, the following solution is to avoid using
> > dst->pending_confirm.
> 
> For the most part this series looks good to me, nice work.

	OK, I'm posting v3 after removing the RFC tag from v2,
I just added the Acked-by tags.

Regards

--
Julian Anastasov <ja@ssi.bg>

  reply	other threads:[~2017-01-31 21:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 14:26 [PATCHv2 RFC net-next 0/7] net: dst_confirm replacement Julian Anastasov
2017-01-28 14:26 ` Julian Anastasov
2017-01-28 14:26 ` [PATCHv2 RFC net-next 1/7] sock: add sk_dst_pending_confirm flag Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-28 14:26 ` [PATCHv2 RFC net-next 2/7] net: add dst_pending_confirm flag to skbuff Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-28 14:26 ` [PATCHv2 RFC net-next 3/7] sctp: add dst_pending_confirm flag Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-30 14:45   ` Neil Horman
2017-01-30 14:45     ` Neil Horman
2017-01-28 14:26 ` [PATCHv2 RFC net-next 4/7] tcp: replace dst_confirm with sk_dst_confirm Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-29 19:27   ` Eric Dumazet
2017-01-29 19:27     ` Eric Dumazet
2017-01-28 14:26 ` [PATCHv2 RFC net-next 5/7] net: add confirm_neigh method to dst_ops Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-28 14:26 ` [PATCHv2 RFC net-next 6/7] net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-28 14:26 ` [PATCHv2 RFC net-next 7/7] net: pending_confirm is not used anymore Julian Anastasov
2017-01-28 14:26   ` Julian Anastasov
2017-01-30 15:13 ` [PATCHv2 RFC net-next 0/7] net: dst_confirm replacement David Miller
2017-01-30 15:13   ` David Miller
2017-01-31 21:53   ` Julian Anastasov [this message]
2017-01-31 21:53     ` Julian Anastasov

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=alpine.LFD.2.11.1701312350110.2064@ja.home.ssi.bg \
    --to=ja@ssi.bg \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yuehaibing@huawei.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 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.