From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2839172 for ; Sat, 28 Aug 2021 17:13:31 +0000 (UTC) Received: by mail-lf1-f41.google.com with SMTP id o10so21382141lfr.11 for ; Sat, 28 Aug 2021 10:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PG8z+XIonuWGdu3czEMXRzaWItNuzacbk0dZJgvuswY=; b=daw0rvbIk5V4Zm8DIXbqAHGUuI91vkfb3EyX9zrL+a+hl26XvDgDL8r9dYETKE/Ae6 NVz34RW6KNXXaquZKrMsm4y3n1D2vXOf6KLPgIF3dO3k1XtDxSAoVKVtq5UPuEzZOwXY C+6YEcQF+K1cqgH+D2AtQjtQx4cGEZE99d2fs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PG8z+XIonuWGdu3czEMXRzaWItNuzacbk0dZJgvuswY=; b=rbtb+Bmjd0hqykBsD8MbxTE87EPs0rySxX9MtdSaQwIAH79smPIcWXQxg4y3VRYAd0 ak3E9WvAwmZuuEDsuu0IE6kWTjOgrdqcjVHpcEuzAHFdG5RNrITNVv4W8MajFexRaZRt CuYCDMP3rRWuxGx3Xjk9eYvbLyVcvL7kV5MpvBe2DDMomaIF4mu4HCb8nl4LlLM3SwSK 9kYvwWNgnDj9xWYdqWT/7Mso7U4PjJaMI2/qpxVEW7D28S8yO5t12iKFm14BTayIBHw5 h1yR2xpA4rsLYHhMPkV2r/tjm/YFgWp2TL4e8cMz56gaCp5UesPOXUBZ2wRJIlDegyfC aM9g== X-Gm-Message-State: AOAM533yuDYb+qXCWYYCaFkVUew4Ni9sxAie1BA4OHYnT/fwicOlIxmT jK4vaB9heaUZSAygLlcq/Dd+0aeP5xUTFWpm X-Google-Smtp-Source: ABdhPJx/6QItbMdm3cE9zyo1LYe3hFqYGLiRQ7QAAGfAe4ZX9JzIz6UpI94U5gTopBpamjGb3yM9Dw== X-Received: by 2002:a19:c197:: with SMTP id r145mr10002757lff.276.1630170808605; Sat, 28 Aug 2021 10:13:28 -0700 (PDT) Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com. [209.85.208.171]) by smtp.gmail.com with ESMTPSA id j18sm816599lfe.301.2021.08.28.10.13.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Aug 2021 10:13:27 -0700 (PDT) Received: by mail-lj1-f171.google.com with SMTP id l18so17401449lji.12 for ; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) X-Received: by 2002:a2e:7d0e:: with SMTP id y14mr12752568ljc.251.1630170807239; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) Precedence: bulk X-Mailing-List: ntfs3@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20210827164926.1726765-1-agruenba@redhat.com> <20210827164926.1726765-5-agruenba@redhat.com> <20210827205644.lkihrypv27er5km3@kari-VirtualBox> In-Reply-To: <20210827205644.lkihrypv27er5km3@kari-VirtualBox> From: Linus Torvalds Date: Sat, 28 Aug 2021 10:13:11 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 04/19] iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable To: Kari Argillander Cc: Andreas Gruenbacher , Konstantin Komarov , Alexander Viro , Christoph Hellwig , "Darrick J. Wong" , Jan Kara , Matthew Wilcox , cluster-devel , linux-fsdevel , Linux Kernel Mailing List , ocfs2-devel@oss.oracle.com, ntfs3@lists.linux.dev Content-Type: text/plain; charset="UTF-8" On Fri, Aug 27, 2021 at 1:56 PM Kari Argillander wrote: > > At least this patch will break ntfs3 which is in next. It has been there > just couple weeks so I understand. I added Konstantin and ntfs3 list so > that we know what is going on. Can you please info if and when do we > need rebase. No need to rebase. It just makes it harder for me to pick one pull over another, since it would mix the two things together. I'll notice the semantic conflict as I do my merge build test, and it's easy for me to fix as part of the merge - whichever one I merge later. It's good if both sides remind me about the issue, but these kinds of conflicts are not a problem. And yes, it does happen that I miss conflicts like this if I merge while on the road and don't do my full build tests, or if it's some architecture-specific thing or a problem that doesn't happen on my usual allmodconfig testing. But neither of those cases should be present in this situation. Linus 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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A503FC4320E for ; Sat, 28 Aug 2021 17:13:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6BA2360EAF for ; Sat, 28 Aug 2021 17:13:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234625AbhH1ROY (ORCPT ); Sat, 28 Aug 2021 13:14:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39134 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229822AbhH1ROV (ORCPT ); Sat, 28 Aug 2021 13:14:21 -0400 Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A7151C061756 for ; Sat, 28 Aug 2021 10:13:29 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id w4so17398149ljh.13 for ; Sat, 28 Aug 2021 10:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PG8z+XIonuWGdu3czEMXRzaWItNuzacbk0dZJgvuswY=; b=daw0rvbIk5V4Zm8DIXbqAHGUuI91vkfb3EyX9zrL+a+hl26XvDgDL8r9dYETKE/Ae6 NVz34RW6KNXXaquZKrMsm4y3n1D2vXOf6KLPgIF3dO3k1XtDxSAoVKVtq5UPuEzZOwXY C+6YEcQF+K1cqgH+D2AtQjtQx4cGEZE99d2fs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PG8z+XIonuWGdu3czEMXRzaWItNuzacbk0dZJgvuswY=; b=ii25bu5up2LtFMbNc/x4lLcAHU6hsUuMTxS70L17wkjVmxwHNXzGbFf6MeO969yEWn +y/sgV6B/SHNCGqgMKGRGi4564a1uSkDZscWgUgJzaeOjqi/nuTfZmHN5y7Qg/jYZWIM j+Mpg1F0kiBuWpMRXw/tP3y+pSepXkhQ2rylpK2ELv9MAUvGxy9hv0CJNe7pRcwB/V72 /xZlW2mbLObdjacFaxwtep5a4gALRwvgi05ehXgTDrUuCUpsSlqPctuP7Dj61bQs1AXI D21UK6vbtoFzpJjgn8v7NApZQcK58Z1hXWm1QcjFYqwYtJlvKUdGyb8bGfD9H9ruYrmu z/qQ== X-Gm-Message-State: AOAM533FW2/fjyyrPnDeKNfblLHiOprdOPO/hIwEiGIL16wrUrvadNt2 C+Eg+2i9HwPzWWYzp70cZ4CQBwWNLkpVBZnS X-Google-Smtp-Source: ABdhPJzEEZYumkA8EJFYVpgY9bt3yxmK5AvIebY0820zd9nmzIQoiJxa3dOssaVkA2iQaFS0h8l0AA== X-Received: by 2002:a2e:b613:: with SMTP id r19mr3043709ljn.136.1630170807953; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com. [209.85.208.178]) by smtp.gmail.com with ESMTPSA id r199sm585979lff.266.2021.08.28.10.13.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Aug 2021 10:13:27 -0700 (PDT) Received: by mail-lj1-f178.google.com with SMTP id y6so17494042lje.2 for ; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) X-Received: by 2002:a2e:7d0e:: with SMTP id y14mr12752568ljc.251.1630170807239; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) MIME-Version: 1.0 References: <20210827164926.1726765-1-agruenba@redhat.com> <20210827164926.1726765-5-agruenba@redhat.com> <20210827205644.lkihrypv27er5km3@kari-VirtualBox> In-Reply-To: <20210827205644.lkihrypv27er5km3@kari-VirtualBox> From: Linus Torvalds Date: Sat, 28 Aug 2021 10:13:11 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 04/19] iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable To: Kari Argillander Cc: Andreas Gruenbacher , Konstantin Komarov , Alexander Viro , Christoph Hellwig , "Darrick J. Wong" , Jan Kara , Matthew Wilcox , cluster-devel , linux-fsdevel , Linux Kernel Mailing List , ocfs2-devel@oss.oracle.com, ntfs3@lists.linux.dev Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 27, 2021 at 1:56 PM Kari Argillander wrote: > > At least this patch will break ntfs3 which is in next. It has been there > just couple weeks so I understand. I added Konstantin and ntfs3 list so > that we know what is going on. Can you please info if and when do we > need rebase. No need to rebase. It just makes it harder for me to pick one pull over another, since it would mix the two things together. I'll notice the semantic conflict as I do my merge build test, and it's easy for me to fix as part of the merge - whichever one I merge later. It's good if both sides remind me about the issue, but these kinds of conflicts are not a problem. And yes, it does happen that I miss conflicts like this if I merge while on the road and don't do my full build tests, or if it's some architecture-specific thing or a problem that doesn't happen on my usual allmodconfig testing. But neither of those cases should be present in this situation. Linus 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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5F709C432BE for ; Sat, 28 Aug 2021 17:17:17 +0000 (UTC) Received: from mx0b-00069f02.pphosted.com (mx0b-00069f02.pphosted.com [205.220.177.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E6B6D60C41 for ; Sat, 28 Aug 2021 17:17:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org E6B6D60C41 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=oss.oracle.com Received: from pps.filterd (m0246631.ppops.net [127.0.0.1]) by mx0b-00069f02.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 17SCnQql032040; Sat, 28 Aug 2021 17:17:16 GMT Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by mx0b-00069f02.pphosted.com with ESMTP id 3aqbx20rgy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 28 Aug 2021 17:17:15 +0000 Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 17SHFr7F012441; Sat, 28 Aug 2021 17:17:14 GMT Received: from oss.oracle.com (oss-old-reserved.oracle.com [137.254.22.2]) by userp3030.oracle.com with ESMTP id 3aqa8uga0x-1 (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Sat, 28 Aug 2021 17:17:14 +0000 Received: from localhost ([127.0.0.1] helo=lb-oss.oracle.com) by oss.oracle.com with esmtp (Exim 4.63) (envelope-from ) id 1mK1u8-0006Ac-L9; Sat, 28 Aug 2021 10:14:04 -0700 Received: from userp3030.oracle.com ([156.151.31.80]) by oss.oracle.com with esmtp (Exim 4.63) (envelope-from ) id 1mK1tf-00069h-As for ocfs2-devel@oss.oracle.com; Sat, 28 Aug 2021 10:13:35 -0700 Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 17SH5s8D186443 for ; Sat, 28 Aug 2021 17:13:35 GMT Received: from mx0a-00069f01.pphosted.com (mx0a-00069f01.pphosted.com [205.220.165.26]) by userp3030.oracle.com with ESMTP id 3aqa8ug72s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 28 Aug 2021 17:13:34 +0000 Received: from pps.filterd (m0246575.ppops.net [127.0.0.1]) by mx0b-00069f01.pphosted.com (8.16.1.2/8.16.0.43) with SMTP id 17SGfOsk029452 for ; Sat, 28 Aug 2021 17:13:33 GMT Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) by mx0b-00069f01.pphosted.com with ESMTP id 3aqrvp06bs-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Sat, 28 Aug 2021 17:13:32 +0000 Received: by mail-lj1-f177.google.com with SMTP id i28so17451710ljm.7 for ; Sat, 28 Aug 2021 10:13:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PG8z+XIonuWGdu3czEMXRzaWItNuzacbk0dZJgvuswY=; b=BHPn5mv/52Iw5AwgpEpwoRgX1fyPpGSuTdFL6amFhuNRA0Onj4OX9v7Nh7vfXl4oDZ W3addY8QDvpJanRYJ29wLxPtVpJLQyZHF/AG1JIB/nGxow54aayoOips//ugNKZpgNyv fZqEz17kw9SgvCWFyPRcdcwPmIEa53VMXOIYWDBHDdl5Lkmxcvgz56TK0XdDvRMWFbd3 vvyxN9yiuDXj93pjU8P9Ma83OJqXeR8Oqfei6gRXqWtJrPywMY7UdkmvPuM9NhSYUI5e DgtTbDp6GhzCv78mk/iV4N8JmAmjxB0n9P785p/UH1hB0VjHkYZ1fRmxLQuyIQ2HRWuK G3xA== X-Gm-Message-State: AOAM532HQdMQKR9Wu6dBG22HeYCLq3VL00b2RDT5wNXb3ZkCpjKlClaH qsIzB08Aj5MkcIXq7MtD1KheqD1b4CCZ+QRC X-Google-Smtp-Source: ABdhPJwEhj08hGiVm3PmFGgJ1JTP/qIF6zlS0VBbmhTk6fB/tsaDtvQLNY1f94/q6npDjKPh1oHxlw== X-Received: by 2002:a2e:9881:: with SMTP id b1mr12824627ljj.53.1630170809320; Sat, 28 Aug 2021 10:13:29 -0700 (PDT) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com. [209.85.208.175]) by smtp.gmail.com with ESMTPSA id p3sm918214lfg.33.2021.08.28.10.13.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Aug 2021 10:13:27 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id h1so17426087ljl.9 for ; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) X-Received: by 2002:a2e:7d0e:: with SMTP id y14mr12752568ljc.251.1630170807239; Sat, 28 Aug 2021 10:13:27 -0700 (PDT) MIME-Version: 1.0 References: <20210827164926.1726765-1-agruenba@redhat.com> <20210827164926.1726765-5-agruenba@redhat.com> <20210827205644.lkihrypv27er5km3@kari-VirtualBox> In-Reply-To: <20210827205644.lkihrypv27er5km3@kari-VirtualBox> From: Linus Torvalds Date: Sat, 28 Aug 2021 10:13:11 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Kari Argillander X-Source-IP: 209.85.208.177 X-ServerName: mail-lj1-f177.google.com X-Proofpoint-SPF-Result: pass X-Proofpoint-SPF-Record: v=spf1 ip4:198.145.29.98/31 ip4:72.55.140.81 include:_spf.google.com include:amazonses.com include:_spf.salesforce.com ~all X-Proofpoint-Virus-Version: vendor=nai engine=6300 definitions=10090 signatures=668682 X-Proofpoint-Spam-Details: rule=tap_notspam policy=tap score=0 mlxlogscore=999 impostorscore=0 lowpriorityscore=0 malwarescore=0 bulkscore=0 adultscore=0 phishscore=0 spamscore=0 clxscore=384 mlxscore=0 suspectscore=0 priorityscore=30 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108280113 domainage_hfrom=5366 X-Spam: Clean X-Proofpoint-Virus-Version: vendor=nai engine=6300 definitions=10090 signatures=668682 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 bulkscore=0 spamscore=0 adultscore=0 malwarescore=0 mlxlogscore=999 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108280112 Cc: Christoph Hellwig , cluster-devel , Jan Kara , Andreas Gruenbacher , Linux Kernel Mailing List , Konstantin Komarov , Alexander Viro , linux-fsdevel , ntfs3@lists.linux.dev, ocfs2-devel@oss.oracle.com Subject: Re: [Ocfs2-devel] [PATCH v7 04/19] iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable X-BeenThere: ocfs2-devel@oss.oracle.com X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ocfs2-devel-bounces@oss.oracle.com Errors-To: ocfs2-devel-bounces@oss.oracle.com X-Proofpoint-Virus-Version: vendor=nai engine=6300 definitions=10090 signatures=668682 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 bulkscore=0 spamscore=0 adultscore=0 malwarescore=0 mlxlogscore=999 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2107140000 definitions=main-2108280113 X-Proofpoint-GUID: W9IDDkrKu_miF-4tu7AWFCFAM0cgil9n X-Proofpoint-ORIG-GUID: W9IDDkrKu_miF-4tu7AWFCFAM0cgil9n On Fri, Aug 27, 2021 at 1:56 PM Kari Argillander wrote: > > At least this patch will break ntfs3 which is in next. It has been there > just couple weeks so I understand. I added Konstantin and ntfs3 list so > that we know what is going on. Can you please info if and when do we > need rebase. No need to rebase. It just makes it harder for me to pick one pull over another, since it would mix the two things together. I'll notice the semantic conflict as I do my merge build test, and it's easy for me to fix as part of the merge - whichever one I merge later. It's good if both sides remind me about the issue, but these kinds of conflicts are not a problem. And yes, it does happen that I miss conflicts like this if I merge while on the road and don't do my full build tests, or if it's some architecture-specific thing or a problem that doesn't happen on my usual allmodconfig testing. But neither of those cases should be present in this situation. Linus _______________________________________________ Ocfs2-devel mailing list Ocfs2-devel@oss.oracle.com https://oss.oracle.com/mailman/listinfo/ocfs2-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Date: Sat, 28 Aug 2021 10:13:11 -0700 Subject: [Cluster-devel] [PATCH v7 04/19] iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable In-Reply-To: <20210827205644.lkihrypv27er5km3@kari-VirtualBox> References: <20210827164926.1726765-1-agruenba@redhat.com> <20210827164926.1726765-5-agruenba@redhat.com> <20210827205644.lkihrypv27er5km3@kari-VirtualBox> Message-ID: List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Fri, Aug 27, 2021 at 1:56 PM Kari Argillander wrote: > > At least this patch will break ntfs3 which is in next. It has been there > just couple weeks so I understand. I added Konstantin and ntfs3 list so > that we know what is going on. Can you please info if and when do we > need rebase. No need to rebase. It just makes it harder for me to pick one pull over another, since it would mix the two things together. I'll notice the semantic conflict as I do my merge build test, and it's easy for me to fix as part of the merge - whichever one I merge later. It's good if both sides remind me about the issue, but these kinds of conflicts are not a problem. And yes, it does happen that I miss conflicts like this if I merge while on the road and don't do my full build tests, or if it's some architecture-specific thing or a problem that doesn't happen on my usual allmodconfig testing. But neither of those cases should be present in this situation. Linus