From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
Hugh Dickins <hughd@google.com>,
linux-afs@lists.infradead.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, cluster-devel@redhat.com,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-nilfs@vger.kernel.org
Subject: Re: return an ERR_PTR from __filemap_get_folio v2
Date: Sun, 22 Jan 2023 08:20:06 +0100 [thread overview]
Message-ID: <20230122072006.GA3654@lst.de> (raw)
In-Reply-To: <20230121170641.121f4224a0e8304765bb4738@linux-foundation.org>
On Sat, Jan 21, 2023 at 05:06:41PM -0800, Andrew Morton wrote:
> This patchset doesn't apply to fs/btrfs/ because linux-next contains
> this 6+ month-old commit:
Hmm. It was literally written against linux-next as of last morning,
which does not have that commit.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] return an ERR_PTR from __filemap_get_folio v2
Date: Sun, 22 Jan 2023 08:20:06 +0100 [thread overview]
Message-ID: <20230122072006.GA3654@lst.de> (raw)
In-Reply-To: <20230121170641.121f4224a0e8304765bb4738@linux-foundation.org>
On Sat, Jan 21, 2023 at 05:06:41PM -0800, Andrew Morton wrote:
> This patchset doesn't apply to fs/btrfs/ because linux-next contains
> this 6+ month-old commit:
Hmm. It was literally written against linux-next as of last morning,
which does not have that commit.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Matthew Wilcox <willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Hugh Dickins <hughd-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-afs-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cluster-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: return an ERR_PTR from __filemap_get_folio v2
Date: Sun, 22 Jan 2023 08:20:06 +0100 [thread overview]
Message-ID: <20230122072006.GA3654@lst.de> (raw)
In-Reply-To: <20230121170641.121f4224a0e8304765bb4738-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
On Sat, Jan 21, 2023 at 05:06:41PM -0800, Andrew Morton wrote:
> This patchset doesn't apply to fs/btrfs/ because linux-next contains
> this 6+ month-old commit:
Hmm. It was literally written against linux-next as of last morning,
which does not have that commit.
next prev parent reply other threads:[~2023-01-22 7:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 6:57 return an ERR_PTR from __filemap_get_folio v2 Christoph Hellwig
2023-01-21 6:57 ` Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 1/7] mm: don't look at xarray value entries in split_huge_pages_in_file Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 2/7] mm: make mapping_get_entry available outside of filemap.c Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 3/7] mm: use filemap_get_entry in filemap_get_incore_folio Christoph Hellwig
2023-01-21 6:57 ` Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 4/7] shmem: remove shmem_get_partial_folio Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 5/7] shmem: open code the page cache lookup in shmem_get_folio_gfp Christoph Hellwig
2023-01-21 6:57 ` Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 6/7] mm: remove FGP_ENTRY Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 6:57 ` [PATCH 7/7] mm: return an ERR_PTR from __filemap_get_folio Christoph Hellwig
2023-01-21 6:57 ` [Cluster-devel] " Christoph Hellwig
2023-01-21 11:52 ` kernel test robot
2023-01-21 11:52 ` kernel test robot
2023-01-21 11:52 ` [Cluster-devel] " kernel test robot
2023-01-21 14:28 ` Christoph Hellwig
2023-01-21 14:28 ` [Cluster-devel] " Christoph Hellwig
2023-01-23 15:44 ` David Sterba
2023-01-23 15:44 ` [Cluster-devel] " David Sterba
2023-01-26 17:24 ` Ryusuke Konishi
2023-01-26 17:24 ` Ryusuke Konishi
2023-01-26 17:24 ` [Cluster-devel] " Ryusuke Konishi
2023-03-10 4:31 ` Naoya Horiguchi
2023-03-10 4:31 ` [Cluster-devel] " Naoya Horiguchi
2023-03-10 7:00 ` Christoph Hellwig
2023-03-10 7:00 ` Christoph Hellwig
2023-03-10 7:00 ` [Cluster-devel] " Christoph Hellwig
2023-03-10 8:02 ` Naoya Horiguchi
2023-03-10 8:02 ` [Cluster-devel] " Naoya Horiguchi
2023-01-22 1:06 ` return an ERR_PTR from __filemap_get_folio v2 Andrew Morton
2023-01-22 1:06 ` Andrew Morton
2023-01-22 1:06 ` [Cluster-devel] " Andrew Morton
2023-01-22 7:20 ` Christoph Hellwig [this message]
2023-01-22 7:20 ` Christoph Hellwig
2023-01-22 7:20 ` [Cluster-devel] " Christoph Hellwig
2023-01-23 18:59 ` Andrew Morton
2023-01-23 18:59 ` Andrew Morton
2023-01-23 18:59 ` [Cluster-devel] " Andrew Morton
2023-01-23 19:18 ` Christoph Hellwig
2023-01-23 19:18 ` Christoph Hellwig
2023-01-23 19:18 ` [Cluster-devel] " Christoph Hellwig
2023-03-28 23:04 ` Andrew Morton
2023-03-28 23:04 ` [Cluster-devel] " Andrew Morton
2023-03-29 23:56 ` Christoph Hellwig
2023-03-29 23:56 ` Christoph Hellwig
2023-03-29 23:56 ` [Cluster-devel] " Christoph Hellwig
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=20230122072006.GA3654@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=cluster-devel@redhat.com \
--cc=hughd@google.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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.