linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Ian Kent <raven@themaw.net>
Cc: David Howells <dhowells@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bill O'Donnell <bodonnel@redhat.com>
Subject: Re: [GIT PULL for v6.7] autofs updates
Date: Mon, 6 Nov 2023 15:50:46 +0100	[thread overview]
Message-ID: <20231106-aufleben-umfeld-25a2cd86e521@brauner> (raw)
In-Reply-To: <83a889bd-3f9e-edce-78ff-0afa01990197@themaw.net>

> Christian, David's original conversion patch for devpts looks like it's
> 
> still relevant, it also looks fairly small to the point that I'm wondering
> 
> if it's worth breaking it down into smaller patches.

I vaguely remember that patch and no, for simple fses like devpts
breaking this into smaller chunks is probably not worth it.

These conversions patches often aren't easy to split nicely anyway.

> Would you be ok with me just doing a straight patch apply, detailed review
> 
> and some testing before posting it?

Sure.

  reply	other threads:[~2023-11-06 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 14:33 [GIT PULL for v6.7] autofs updates Christian Brauner
2023-10-29  7:54 ` Ian Kent
2023-10-30 10:24   ` Christian Brauner
2023-10-31  2:04     ` Ian Kent
2023-10-30 14:28   ` Bill O'Donnell
2023-10-31  2:12     ` Ian Kent
2023-11-06  6:22       ` Ian Kent
2023-11-06 14:50         ` Christian Brauner [this message]
2023-11-06 14:40       ` David Howells
2023-10-30 20:05 ` pr-tracker-bot

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=20231106-aufleben-umfeld-25a2cd86e521@brauner \
    --to=brauner@kernel.org \
    --cc=bodonnel@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    --cc=torvalds@linux-foundation.org \
    /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).