From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C690AC4321E for ; Tue, 29 Nov 2022 13:36:53 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 55D936B007E; Tue, 29 Nov 2022 08:36:53 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 50D496B0080; Tue, 29 Nov 2022 08:36:53 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 388356B0081; Tue, 29 Nov 2022 08:36:53 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 2B2626B007E for ; Tue, 29 Nov 2022 08:36:53 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 2A33FC0EF1 for ; Tue, 29 Nov 2022 08:48:43 +0000 (UTC) X-FDA: 80185854126.02.7FFB076 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf12.hostedemail.com (Postfix) with ESMTP id 3D4874000E for ; Tue, 29 Nov 2022 08:48:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669711721; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+9/SG262uJs5aEn47977HgvoOkAGZaXesrmlGYL/QQU=; b=Pr15GyKpSnrqBVWsKNCx5qDo8hFah0EZIOB3tYZUpJ4Gbq/QiFdhu1ARAfQnqW7JaC7UH8 boW3Mc5wCWICm0078A2VhWhea0v6GihYqwJcbHnIiNgKm7K4QZOQcAYPAG7VQQ8MzShV4z npJyvFyoBcSlp8ZJoMNobPe+3PmZeMU= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-84-wCUyvj-mNv6KSJSRmCCxSw-1; Tue, 29 Nov 2022 03:48:37 -0500 X-MC-Unique: wCUyvj-mNv6KSJSRmCCxSw-1 Received: by mail-wm1-f69.google.com with SMTP id 1-20020a05600c028100b003cf7833293cso9871816wmk.3 for ; Tue, 29 Nov 2022 00:48:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:organization:from:references :cc:to:content-language:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+9/SG262uJs5aEn47977HgvoOkAGZaXesrmlGYL/QQU=; b=iaZZqGR1ZOYnHwsN0Oil/gAI8nNcgAvBCCMKcTQ5S004L8sATvW5ijTdTrl374zUQS Wyyte3Wco9kThu3LAJafE33mLKYpYag7hgT7jLTNdlwMSc1FuKM/noX2Z/EMXnbRRqmV w/FefY4saAKUvkjwAztDmkvlx5MRFMm7n/Xn9y941NJl6bV7XpdQw0hwxC4pM/BHCb5r vOc5ZGXSfCgKEFrv3EQMuwsWPseXGLTNSIQGWb/qUJCHw8/yNpGDQMAga3bd9mKnY4wq zoygBnjgQs9huO01e9K7cQtTzBXWq0fCkEn2CWXvwXwEV+9Ghog606x/09GcnXplqEHb 5eLA== X-Gm-Message-State: ANoB5pm/o3mPtUv7pBWV8mGhe68rPUIjGpXmJPzsYIAbyp/dINQXVgoZ 4guUJnmZoG+kwsK16vUfn0fbnVfyn2AZZ4ALrBn/4koQyFHpMphUUm5bYxUVMa8cT2ZBIxujq0Q dnZAdYWNl02U= X-Received: by 2002:adf:ed86:0:b0:236:4930:2468 with SMTP id c6-20020adfed86000000b0023649302468mr27266652wro.221.1669711716557; Tue, 29 Nov 2022 00:48:36 -0800 (PST) X-Google-Smtp-Source: AA0mqf5WObKFiHoIvjAvSDGoBWk7nZS9J8pydo8v+yQ7WbXm3jibFRxv0v14chgZsAxfMxQqYFXPxw== X-Received: by 2002:adf:ed86:0:b0:236:4930:2468 with SMTP id c6-20020adfed86000000b0023649302468mr27266600wro.221.1669711716176; Tue, 29 Nov 2022 00:48:36 -0800 (PST) Received: from ?IPV6:2003:cb:c705:ca00:3fb8:c253:3bf7:b60e? (p200300cbc705ca003fb8c2533bf7b60e.dip0.t-ipconnect.de. [2003:cb:c705:ca00:3fb8:c253:3bf7:b60e]) by smtp.gmail.com with ESMTPSA id j5-20020a5d5645000000b00225307f43fbsm13057331wrw.44.2022.11.29.00.48.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Nov 2022 00:48:35 -0800 (PST) Message-ID: <22b1107b-0acc-5772-a883-8f3c4682eb1b@redhat.com> Date: Tue, 29 Nov 2022 09:48:33 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: [PATCH mm-unstable v1 16/20] mm/frame-vector: remove FOLL_FORCE usage To: Andrew Morton Cc: Hans Verkuil , linux-kernel@vger.kernel.org, x86@kernel.org, linux-alpha@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org, etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-samsung-soc@vger.kernel.org, linux-rdma@vger.kernel.org, linux-media@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-perf-users@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kselftest@vger.kernel.org, Linus Torvalds , Jason Gunthorpe , John Hubbard , Peter Xu , Greg Kroah-Hartman , Andrea Arcangeli , Hugh Dickins , Nadav Amit , Vlastimil Babka , Matthew Wilcox , Mike Kravetz , Muchun Song , Shuah Khan , Lucas Stach , David Airlie , Oded Gabbay , Arnd Bergmann , Christoph Hellwig , Alex Williamson , Marek Szyprowski , Tomasz Figa , Mauro Carvalho Chehab 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> From: David Hildenbrand Organization: Red Hat In-Reply-To: <20221128145927.df895bf1966cfa125cae9668@linux-foundation.org> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669711722; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=+9/SG262uJs5aEn47977HgvoOkAGZaXesrmlGYL/QQU=; b=y/J1p1mW3OQr/NoMlefEC2wrPHnRXCx5ogXNrih/pjb4YKdyN1Bhe0m48v16Lgb9MQ8NCR HGadZT49E5DYkWZuYKdU4sXLXMBYwuk7yGTqmxXLg3rQ5AgcUHgGu8boYPMfu9BQ8TEW8t 0UF09HF6iM0yCnEJdq5/wIQRghtianE= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=Pr15GyKp; spf=pass (imf12.hostedemail.com: domain of david@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=david@redhat.com; dmarc=pass (policy=none) header.from=redhat.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669711722; a=rsa-sha256; cv=none; b=679rI8xg2WIokDbfhOuKao8orCO8exiN/llQilwjMNpfzOgx5WOKtz8jkuEdCOxaqU9YFj BIN7cleu9h31hqPxd4yexIdBoeOMvrNmnyrxe4bpSTkxW69w7QHB5+VxJ5mVW829YxGkeN Le7d4NeKEfN9I7Ic7fxHp40OBzLLSI0= X-Stat-Signature: 1rfzoo17nxxaaukurfsxipcdxqtgwzuj X-Rspam-User: X-Rspamd-Queue-Id: 3D4874000E X-Rspamd-Server: rspam11 Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=Pr15GyKp; spf=pass (imf12.hostedemail.com: domain of david@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=david@redhat.com; dmarc=pass (policy=none) header.from=redhat.com X-HE-Tag: 1669711722-692762 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: 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