From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Hildenbrand Date: Tue, 29 Nov 2022 08:48:33 +0000 Subject: Re: [PATCH mm-unstable v1 16/20] mm/frame-vector: remove FOLL_FORCE usage Message-Id: <22b1107b-0acc-5772-a883-8f3c4682eb1b@redhat.com> List-Id: References: <20221116102659.70287-1-david@redhat.com> <20221116102659.70287-17-david@redhat.com> <81fb0fa3-2e06-b765-56ac-a7d981194e59@redhat.com> <08b65ac6-6786-1080-18f8-d2be109c85fc@xs4all.nl> <9d0bf98a-3d6a-1082-e992-1338e1525935@redhat.com> <20221128145927.df895bf1966cfa125cae9668@linux-foundation.org> In-Reply-To: <20221128145927.df895bf1966cfa125cae9668@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrew Morton Cc: linux-ia64@vger.kernel.org, Greg Kroah-Hartman , dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org, Hans Verkuil , linux-mm@kvack.org, Nadav Amit , linux-kselftest@vger.kernel.org, sparclinux@vger.kernel.org, Shuah Khan , Marek Szyprowski , Andrea Arcangeli , linux-samsung-soc@vger.kernel.org, linux-rdma@vger.kernel.org, x86@kernel.org, Hugh Dickins , Matthew Wilcox , Christoph Hellwig , Jason Gunthorpe , Vlastimil Babka , linux-media@vger.kernel.org, Arnd Bergmann , John Hubbard , linux-um@lists.infradead.org, etnaviv@lists.freedesktop.org, Alex Williamson , Peter Xu , Muchun Song , Mauro Carvalho Chehab , linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, Oded Gabbay , linux-kernel@vger.kernel.org, Tomasz Figa , linux-perf-users@vger.kernel.org, linux-security-module@vger.kernel.org, linux-alpha@vger.kernel.org, linux-fsdevel@vger.kernel.org, Linus Torvalds , Mike Kravetz On 28.11.22 23:59, Andrew Morton wrote: > On Mon, 28 Nov 2022 09:18:47 +0100 David Hildenbrand wrote: > >>> Less chances of things going wrong that way. >>> >>> Just mention in the v2 cover letter that the first patch was added to >>> make it easy to backport that fix without being hampered by merge >>> conflicts if it was added after your frame_vector.c patch. >> >> Yes, that's the way I would naturally do, it, however, Andrew prefers >> delta updates for minor changes. >> >> @Andrew, whatever you prefer! > > I'm inclined to let things sit as they are. Cross-tree conflicts > happen, and Linus handles them. I'll flag this (very simple) conflict > in the pull request, if MM merges second. If v4l merges second then > hopefully they will do the same. But this one is so simple that Linus > hardly needs our help. > > But Linus won't be editing changelogs so that the changelog makes more > sense after both trees are joined. I'm inclined to let the changelog > sit as it is as well. Works for me. Thanks Andrew! -- Thanks, David / dhildenb