All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: add ro_after_init for tcp{,v6}_prot_override
Date: Thu, 23 Feb 2023 21:35:58 +0800	[thread overview]
Message-ID: <20230223133558.GA2878@bogon> (raw)
In-Reply-To: <db64d10e-3887-fc95-a91c-33408e3670f9@tessares.net>

On Thu, Feb 23, 2023 at 10:10:25AM +0100, Matthieu Baerts wrote:
> Hi Geliang,
> 
> Thank you for this patch!
> 
> On 23/02/2023 04:37, Geliang Tang wrote:
> > Add __ro_after_init labels for the variables tcp_prot_override and
> > tcpv6_prot_override, just like other variables adjacent to them, to
> > indicate that they are initialised from the init hoos and no writes
> 
> (Do you mean s/hoos/hook/?)

Yes, it should be 'hooks'. Please fix this for me.

> 
> > occur afterwards.
> 
> Good catch!
> 
> Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> 
> Do you mind if I change the target to mptcp-net and add a Fixes tag when
> applying this patch?
> 
> Fixes: b19bc2945b40 ("mptcp: implement delegated actions")

Fixes: 51fa7f8ebf0e2 ("mptcp: mark ops structures as ro_after_init")
Maybe this fixes tag is better, WDYT?

Thanks,
-Geliang

> 
> Cheers,
> Matt
> -- 
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net

  reply	other threads:[~2023-02-23 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  3:37 [PATCH mptcp-next] mptcp: add ro_after_init for tcp{,v6}_prot_override Geliang Tang
2023-02-23  5:13 ` mptcp: add ro_after_init for tcp{,v6}_prot_override: Tests Results MPTCP CI
2023-02-23  9:10 ` [PATCH mptcp-next] mptcp: add ro_after_init for tcp{,v6}_prot_override Matthieu Baerts
2023-02-23 13:35   ` Geliang Tang [this message]
2023-02-23 13:49     ` Matthieu Baerts
2023-02-23 13:55     ` Matthieu Baerts
2023-02-23 13:57 ` Matthieu Baerts
2023-02-24  1:29   ` Geliang Tang
2023-02-24  9:36     ` Matthieu Baerts

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=20230223133558.GA2878@bogon \
    --to=geliang.tang@suse.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    /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.