All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v2 5/6] mptcp: Export low-level routines for IPv6
Date: Wed, 06 Nov 2019 11:09:26 +0100	[thread overview]
Message-ID: <4845aa6c240b819fca29f52ac82ad3b1a2a681e5.camel@redhat.com> (raw)
In-Reply-To: 6c2c57ca-b1de-a8c7-54bc-eeddba222f0f@tessares.net

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

On Wed, 2019-11-06 at 10:37 +0100, Matthieu Baerts wrote:
> Hi Paolo,
> 
> On 06/11/2019 10:03, Paolo Abeni wrote:
> > On Tue, 2019-11-05 at 20:41 -0800, Peter Krystad wrote:
> > > @@ -1111,7 +1111,8 @@ static void tcp_v6_restore_cb(struct sk_buff *skb)
> > >   		sizeof(struct inet6_skb_parm));
> > >   }
> > >   
> > > -static struct sock *tcp_v6_syn_recv_sock(const struct sock *sk, struct sk_buff *skb,
> > > +static struct sock *tcp_v6_syn_recv_sock(const struct sock *sk,
> > > +					 struct sk_buff *skb,
> > >   					 struct request_sock *req,
> > >   					 struct dst_entry *dst,
> > >   					 struct request_sock *req_unhash,
> > 
> > Minor nit: it looks like this chunk is not needed[1].
> 
> Peter replied this in the previous version of the patch:
> 
>  > It seemed like since I was in the neighborhood I would fix this
>  > over-80 char line. If that's not appropriate we can drop this chunk.

whoops, I missed that, sorry! And thank you for the head-up!

> I guess we should not modify the style of non MPTCP code. Then better to 
> drop this change, right?

Yes, exactly. The above change should be in a separate, non mptcp-
related patch.

Cheers,

Paolo

             reply	other threads:[~2019-11-06 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 10:09 Paolo Abeni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-06 15:18 [MPTCP] Re: [PATCH v2 5/6] mptcp: Export low-level routines for IPv6 Matthieu Baerts
2019-11-06  9:37 Matthieu Baerts
2019-11-06  9:03 Paolo Abeni

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=4845aa6c240b819fca29f52ac82ad3b1a2a681e5.camel@redhat.com \
    --to=unknown@example.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.