From: Dominique Martinet <asmadeus@codewreck.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Stefano Stabellini <stefano@aporeto.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] net/p9: load default transports
Date: Tue, 9 Nov 2021 07:31:52 +0900 [thread overview]
Message-ID: <YYmlWC9k9jU/JXri@codewreck.org> (raw)
In-Reply-To: <c2a33fa1-30b0-4f19-808f-3bd0316a4ed8@t-8ch.de>
Hi,
Thomas Weißschuh wrote on Mon, Nov 08, 2021 at 07:50:34PM +0100:
> I did not notice that you already had applied "net/9p: autoload transport modules"
> to your tree when sending this series.
>
> Please note that in this series I modified patch 1 a bit, from the ony you
> applied, to prevent warnings in patch 4.
> Concretely I modified the prototypes of `v9fs_get_trans_by_name()` and
> `_p9_get_trans_by_name()` to take const parameters.
>
> Feel free to roll those changes into this patch when applying or I can resend
> the patch/series.
Thanks for the heads up, it's ok -- I'll move the constification of
these functions to patch 4 myself.
I've just sent my pull request to Linus so will take your patches to
my for-next branch when that's merged.
--
Dominique
prev parent reply other threads:[~2021-11-08 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 19:38 [PATCH v2 0/4] net/9p: optimize transport module loading Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 1/4] net/9p: autoload transport modules Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 2/4] 9p/trans_fd: split into dedicated module Thomas Weißschuh
2022-01-10 0:57 ` Dominique Martinet
2022-01-10 6:42 ` Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 3/4] 9p/xen: autoload when xenbus service is available Thomas Weißschuh
2021-11-03 19:38 ` [PATCH v2 4/4] net/p9: load default transports Thomas Weißschuh
2021-11-08 18:50 ` Thomas Weißschuh
2021-11-08 22:31 ` Dominique Martinet [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=YYmlWC9k9jU/JXri@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=stefano@aporeto.com \
--cc=v9fs-developer@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).