From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PATCH RFC 00/10] mptcp: refactor token code
Date: Tue, 27 Aug 2019 20:06:45 +0200 [thread overview]
Message-ID: <20190827180645.GC20113@breakpoint.cc> (raw)
In-Reply-To: cbd96f1d-056b-200c-105b-6c7cd746902c@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> For the 'mptcp_' prefix, we made sure to add them to all functions
> exposed outside net/mptcp and Peter got the excellent idea to move all
> functions only needed in net/mptcp into net/mptcp/protocol.h. We didn't
> add 'mptcp_' prefix for all these "internal" functions but it certainly
> makes sense to do that. I guess it is useful when debugging if you see
> these functions in a call trace or in the list of functions available
> for tracing.
>
> Do you think we should do the same for "crypto" and "subflow" and "pm"?
> I guess "pm" and "subflow" are keywords mainly used in "mptcp" but it is
> maybe not clear for everybody.
Yes. Subflow is maybe fine though.
pm is 'power mangement', so I think it makes sense to prefix mptcp_
there.
> The patches look very good to me, just a few questions and one or two
> typos, nothing important. I guess other people will also have a look at
> them :)
Thanks a lot for the review, I will respin a new version later this
week.
next reply other threads:[~2019-08-27 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 18:06 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 13:37 [MPTCP] [PATCH RFC 00/10] mptcp: refactor token code Matthieu Baerts
2019-08-28 10:02 Florian Westphal
2019-08-28 0:18 Peter Krystad
2019-08-28 0:13 Peter Krystad
2019-08-27 16:59 Matthieu Baerts
2019-08-25 18:59 Florian Westphal
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=20190827180645.GC20113@breakpoint.cc \
--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.