public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
	"Gautham R. Shenoy"	 <gautham.shenoy@amd.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>,
	Oliver Sang	 <oliver.sang@intel.com>,
	Swapnil Sapkal <swapnil.sapkal@amd.com>,
	WangYuli	 <wangyuli@uniontech.com>,
	linux-fsdevel@vger.kernel.org, 	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] pipe: don't update {a,c,m}time for anonymous pipes
Date: Thu, 06 Feb 2025 07:33:49 -0500	[thread overview]
Message-ID: <0babce16eeaf3bc7fb5ff28f7a769e2ce8f22abe.camel@kernel.org> (raw)
In-Reply-To: <20250205181716.GA13817@redhat.com>

On Wed, 2025-02-05 at 19:17 +0100, Oleg Nesterov wrote:
> OK, let me send v3 right now...
> 
> Changes: make pipeanon_fops static.
> 
> Link to v1: https://lore.kernel.org/all/20250204132153.GA20921@redhat.com/
> Link to v2: https://lore.kernel.org/all/20250205161636.GA1001@redhat.com/
> 
> Oleg.
> ---
> 
>  fs/pipe.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++---------------
>  1 file changed, 47 insertions(+), 15 deletions(-)
> 

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2025-02-06 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 18:17 [PATCH v3 0/2] pipe: don't update {a,c,m}time for anonymous pipes Oleg Nesterov
2025-02-05 18:17 ` [PATCH v3 1/2] pipe: introduce struct file_operations pipeanon_fops Oleg Nesterov
2025-02-05 18:18 ` [PATCH v3 2/2] pipe: don't update {a,c,m}time for anonymous pipes Oleg Nesterov
2025-02-06  3:12 ` [PATCH v3 0/2] " K Prateek Nayak
2025-02-06  9:55 ` Christian Brauner
2025-02-06 12:33 ` Jeff Layton [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=0babce16eeaf3bc7fb5ff28f7a769e2ce8f22abe.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=gautham.shenoy@amd.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=oleg@redhat.com \
    --cc=oliver.sang@intel.com \
    --cc=swapnil.sapkal@amd.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wangyuli@uniontech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox