From: Christian Brauner <brauner@kernel.org>
To: Ian Kent <raven@themaw.net>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
autofs mailing list <autofs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bill O'Donnell <billodo@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 0/8] autofs - convert to to use mount api
Date: Thu, 21 Sep 2023 11:13:38 +0200 [thread overview]
Message-ID: <20230921-altpapier-knien-1dd29cd78a2f@brauner> (raw)
In-Reply-To: <169527971702.27328.16272807830250040704.stgit@donald.themaw.net>
On Thu, Sep 21, 2023 at 03:03:26PM +0800, Ian Kent wrote:
> There was a patch from David Howells to convert autofs to use the mount
> api but it was never merged.
>
> I have taken David's patch and refactored it to make the change easier
> to review in the hope of having it merged.
>
> Signed-off-by: Ian Kent <raven@themaw.net>
> ---
>
> Ian Kent (8):
> autofs: refactor autofs_prepare_pipe()
> autofs: add autofs_parse_fd()
> autofs - refactor super block info init
> autofs: reformat 0pt enum declaration
> autofs: refactor parse_options()
> autofs: validate protocol version
> autofs: convert autofs to use the new mount api
> autofs: fix protocol sub version setting
>
Yeah sure, but I only see 4 patches on the list? Is my setup broken or
did you accidently forget to send some patches?
next prev parent reply other threads:[~2023-09-21 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 7:03 Ian Kent
2023-09-21 7:03 ` [PATCH 1/8] autofs: refactor autofs_prepare_pipe() Ian Kent
2023-09-21 7:03 ` [PATCH 2/8] autofs: add autofs_parse_fd() Ian Kent
2023-09-21 7:03 ` [PATCH 3/8] autofs - refactor super block info init Ian Kent
2023-09-21 7:03 ` [PATCH 4/8] autofs: reformat 0pt enum declaration Ian Kent
2023-09-21 9:13 ` Christian Brauner [this message]
2023-09-21 12:35 ` [PATCH 0/8] autofs - convert to to use mount api Ian Kent
2023-09-22 4:12 Ian Kent
2023-09-22 12:11 ` Christian Brauner
2023-09-22 13:25 ` Bill O'Donnell
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=20230921-altpapier-knien-1dd29cd78a2f@brauner \
--to=brauner@kernel.org \
--cc=autofs@vger.kernel.org \
--cc=billodo@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®