From: Greg KH <gregkh@linuxfoundation.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: arnd@arndb.de, dedekind1@gmail.com, y2038@lists.linaro.org,
richard@nod.at, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, tj@kernel.org,
linux-mtd@lists.infradead.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ntfs-dev@lists.sourceforge.net, hch@lst.de,
jlbec@evilplan.org
Subject: Re: [f2fs-dev] [PATCH v8 03/20] timestamp_truncate: Replace users of timespec64_trunc
Date: Sun, 18 Aug 2019 20:34:46 +0200 [thread overview]
Message-ID: <20190818183446.GA2791@kroah.com> (raw)
In-Reply-To: <20190818165817.32634-4-deepa.kernel@gmail.com>
On Sun, Aug 18, 2019 at 09:58:00AM -0700, Deepa Dinamani wrote:
> Update the inode timestamp updates to use timestamp_truncate()
> instead of timespec64_trunc().
>
> The change was mostly generated by the following coccinelle
> script.
>
> virtual context
> virtual patch
>
> @r1 depends on patch forall@
> struct inode *inode;
> identifier i_xtime =~ "^i_[acm]time$";
> expression e;
> @@
>
> inode->i_xtime =
> - timespec64_trunc(
> + timestamp_truncate(
> ...,
> - e);
> + inode);
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Cc: adrian.hunter@intel.com
> Cc: dedekind1@gmail.com
> Cc: gregkh@linuxfoundation.org
> Cc: hch@lst.de
> Cc: jaegeuk@kernel.org
> Cc: jlbec@evilplan.org
> Cc: richard@nod.at
> Cc: tj@kernel.org
> Cc: yuchao0@huawei.com
> Cc: linux-f2fs-devel@lists.sourceforge.net
> Cc: linux-ntfs-dev@lists.sourceforge.net
> Cc: linux-mtd@lists.infradead.org
> ---
> fs/attr.c | 21 ++++++++++++---------
> fs/configfs/inode.c | 12 ++++++------
> fs/f2fs/file.c | 21 ++++++++++++---------
> fs/kernfs/inode.c | 7 +++----
> fs/ntfs/inode.c | 21 ++++++++++++---------
> fs/ubifs/file.c | 21 ++++++++++++---------
> 6 files changed, 57 insertions(+), 46 deletions(-)
For kernfs:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: arnd@arndb.de, dedekind1@gmail.com, y2038@lists.linaro.org,
richard@nod.at, yuchao0@huawei.com, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, tj@kernel.org,
linux-mtd@lists.infradead.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ntfs-dev@lists.sourceforge.net, hch@lst.de,
jlbec@evilplan.org
Subject: Re: [PATCH v8 03/20] timestamp_truncate: Replace users of timespec64_trunc
Date: Sun, 18 Aug 2019 20:34:46 +0200 [thread overview]
Message-ID: <20190818183446.GA2791@kroah.com> (raw)
In-Reply-To: <20190818165817.32634-4-deepa.kernel@gmail.com>
On Sun, Aug 18, 2019 at 09:58:00AM -0700, Deepa Dinamani wrote:
> Update the inode timestamp updates to use timestamp_truncate()
> instead of timespec64_trunc().
>
> The change was mostly generated by the following coccinelle
> script.
>
> virtual context
> virtual patch
>
> @r1 depends on patch forall@
> struct inode *inode;
> identifier i_xtime =~ "^i_[acm]time$";
> expression e;
> @@
>
> inode->i_xtime =
> - timespec64_trunc(
> + timestamp_truncate(
> ...,
> - e);
> + inode);
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Cc: adrian.hunter@intel.com
> Cc: dedekind1@gmail.com
> Cc: gregkh@linuxfoundation.org
> Cc: hch@lst.de
> Cc: jaegeuk@kernel.org
> Cc: jlbec@evilplan.org
> Cc: richard@nod.at
> Cc: tj@kernel.org
> Cc: yuchao0@huawei.com
> Cc: linux-f2fs-devel@lists.sourceforge.net
> Cc: linux-ntfs-dev@lists.sourceforge.net
> Cc: linux-mtd@lists.infradead.org
> ---
> fs/attr.c | 21 ++++++++++++---------
> fs/configfs/inode.c | 12 ++++++------
> fs/f2fs/file.c | 21 ++++++++++++---------
> fs/kernfs/inode.c | 7 +++----
> fs/ntfs/inode.c | 21 ++++++++++++---------
> fs/ubifs/file.c | 21 ++++++++++++---------
> 6 files changed, 57 insertions(+), 46 deletions(-)
For kernfs:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, y2038@lists.linaro.org,
arnd@arndb.de, adrian.hunter@intel.com, dedekind1@gmail.com,
hch@lst.de, jaegeuk@kernel.org, jlbec@evilplan.org,
richard@nod.at, tj@kernel.org, yuchao0@huawei.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-ntfs-dev@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v8 03/20] timestamp_truncate: Replace users of timespec64_trunc
Date: Sun, 18 Aug 2019 20:34:46 +0200 [thread overview]
Message-ID: <20190818183446.GA2791@kroah.com> (raw)
In-Reply-To: <20190818165817.32634-4-deepa.kernel@gmail.com>
On Sun, Aug 18, 2019 at 09:58:00AM -0700, Deepa Dinamani wrote:
> Update the inode timestamp updates to use timestamp_truncate()
> instead of timespec64_trunc().
>
> The change was mostly generated by the following coccinelle
> script.
>
> virtual context
> virtual patch
>
> @r1 depends on patch forall@
> struct inode *inode;
> identifier i_xtime =~ "^i_[acm]time$";
> expression e;
> @@
>
> inode->i_xtime =
> - timespec64_trunc(
> + timestamp_truncate(
> ...,
> - e);
> + inode);
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Cc: adrian.hunter@intel.com
> Cc: dedekind1@gmail.com
> Cc: gregkh@linuxfoundation.org
> Cc: hch@lst.de
> Cc: jaegeuk@kernel.org
> Cc: jlbec@evilplan.org
> Cc: richard@nod.at
> Cc: tj@kernel.org
> Cc: yuchao0@huawei.com
> Cc: linux-f2fs-devel@lists.sourceforge.net
> Cc: linux-ntfs-dev@lists.sourceforge.net
> Cc: linux-mtd@lists.infradead.org
> ---
> fs/attr.c | 21 ++++++++++++---------
> fs/configfs/inode.c | 12 ++++++------
> fs/f2fs/file.c | 21 ++++++++++++---------
> fs/kernfs/inode.c | 7 +++----
> fs/ntfs/inode.c | 21 ++++++++++++---------
> fs/ubifs/file.c | 21 ++++++++++++---------
> 6 files changed, 57 insertions(+), 46 deletions(-)
For kernfs:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-08-18 18:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 16:57 [PATCH v8 00/20] vfs: Add support for timestamp limits Deepa Dinamani
2019-08-18 16:57 ` Deepa Dinamani
2019-08-18 16:57 ` [f2fs-dev] " Deepa Dinamani
2019-08-18 16:57 ` Deepa Dinamani
2019-08-18 16:57 ` [PATCH v8 01/20] vfs: Add file timestamp range support Deepa Dinamani
2019-08-18 16:57 ` [PATCH v8 02/20] vfs: Add timestamp_truncate() api Deepa Dinamani
2019-08-18 16:58 ` [f2fs-dev] [PATCH v8 03/20] timestamp_truncate: Replace users of timespec64_trunc Deepa Dinamani
2019-08-18 16:58 ` Deepa Dinamani
2019-08-18 16:58 ` Deepa Dinamani
2019-08-18 18:34 ` Greg KH [this message]
2019-08-18 18:34 ` Greg KH
2019-08-18 18:34 ` Greg KH
2019-08-18 16:58 ` [PATCH v8 04/20] mount: Add mount warning for impending timestamp expiry Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 05/20] utimes: Clamp the timestamps before update Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 06/20] fs: Fill in max and min timestamps in superblock Deepa Dinamani
2019-08-18 16:58 ` Deepa Dinamani
2019-08-20 11:28 ` Anders Larsen
2019-08-20 11:28 ` Anders Larsen
2019-08-20 11:28 ` Anders Larsen
2019-08-20 12:22 ` Tigran Aivazian
2019-08-20 12:28 ` Tigran Aivazian
2019-08-20 12:28 ` Tigran Aivazian
2019-08-18 16:58 ` [PATCH v8 07/20] 9p: Fill min and max timestamps in sb Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 08/20] adfs: Fill in max and min " Deepa Dinamani
2019-08-20 16:28 ` Matthew Wilcox
2019-08-20 23:55 ` Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 09/20] ext4: Initialize timestamps limits Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 10/20] fs: nfs: Initialize filesystem timestamp ranges Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 11/20] fs: cifs: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 12/20] fs: fat: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 13/20] fs: affs: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 14/20] fs: sysv: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 15/20] fs: ceph: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 16/20] fs: orangefs: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 17/20] fs: hpfs: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 18/20] fs: omfs: " Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 19/20] pstore: fs superblock limits Deepa Dinamani
2019-08-20 7:20 ` Kees Cook
2019-08-21 0:03 ` Deepa Dinamani
2019-08-18 16:58 ` [PATCH v8 20/20] isofs: Initialize filesystem timestamp ranges Deepa Dinamani
2019-08-20 11:05 ` [PATCH v8 00/20] vfs: Add support for timestamp limits Jeff Layton
2019-08-20 11:05 ` Jeff Layton
2019-08-20 11:05 ` [f2fs-dev] " Jeff Layton
2019-08-20 11:05 ` Jeff Layton
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=20190818183446.GA2791@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=dedekind1@gmail.com \
--cc=deepa.kernel@gmail.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=jlbec@evilplan.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=richard@nod.at \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.