From: Christoph Hellwig <hch@infradead.org>
To: Ian Kent <raven@themaw.net>
Cc: xfs <linux-xfs@vger.kernel.org>, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [PATCH] xfsprogs: ignore autofs mount table entries
Date: Thu, 15 Oct 2020 09:25:59 +0100 [thread overview]
Message-ID: <20201015082559.GA4450@infradead.org> (raw)
In-Reply-To: <160212194125.16851.17467120219710843339.stgit@mickey.themaw.net>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-10-15 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 1:52 [PATCH] xfsprogs: ignore autofs mount table entries Ian Kent
2020-10-08 1:54 ` Ian Kent
2020-10-08 20:03 ` Eric Sandeen
2020-10-09 0:49 ` Ian Kent
2020-10-15 8:25 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-01 1:06 Ian Kent
2020-10-01 15:19 ` Darrick J. Wong
2020-10-02 2:55 ` Ian Kent
2020-10-01 21:22 ` Eric Sandeen
2020-10-02 2:27 ` Ian Kent
2020-10-02 4:40 ` Ian Kent
2020-10-08 20:02 ` Eric Sandeen
2020-10-09 0:55 ` Ian Kent
2020-10-02 15:15 ` Eric Sandeen
2020-10-07 4:41 ` Ian Kent
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=20201015082559.GA4450@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=raven@themaw.net \
--cc=sandeen@sandeen.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).