This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Mon Apr 29 12:15:28 2024 >From mailfetcher Sat Aug 17 04:36:27 2019 Envelope-to: lkml@grols.ch Delivery-date: Sat, 17 Aug 2019 04:36:26 +0200 Received: from stout.grols.ch [195.201.141.146] by 72459556e3a9 with IMAP (fetchmail-6.3.26) for (single-drop); Sat, 17 Aug 2019 04:36:27 +0200 (CEST) Received: from vger.kernel.org ([209.132.180.67]) by stout.grols.ch with esmtp (Exim 4.89) (envelope-from ) id 1hyoZu-0007Ii-8z for lkml@grols.ch; Sat, 17 Aug 2019 04:36:26 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726032AbfHQCgC (ORCPT ); Fri, 16 Aug 2019 22:36:02 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:8949 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725938AbfHQCgC (ORCPT ); Fri, 16 Aug 2019 22:36:02 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Fri, 16 Aug 2019 19:36:04 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Fri, 16 Aug 2019 19:36:01 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Fri, 16 Aug 2019 19:36:01 -0700 Received: from [10.110.48.28] (172.20.13.39) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 17 Aug 2019 02:36:01 +0000 Subject: Re: [RFC PATCH v2 2/3] mm/gup: introduce FOLL_PIN flag for get_user_pages() To: Andrew Morton Cc: Christoph Hellwig , Dan Williams , Dave Chinner , Ira Weiny , Jan Kara , Jason Gunthorpe , =?UTF-8?B References: <20190817022419.23304-1-jhubbard@nvidia.com> <20190817022419.23304-3-jhubbard@nvidia.com> X-NVConfidentiality: public From: John Hubbard Message-Id: <5a95d15b-f54c-e663-7031-c2bf9b19899e@nvidia.com> Date: Fri, 16 Aug 2019 19:36:00 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 Mime-Version: 1.0 In-Reply-To: <20190817022419.23304-3-jhubbard@nvidia.com> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1566009364; bh=sE67K9fwIddpKrmhvFzA734CgzzbX9SZq+iv3kZAz2w=; h=X-PGP-Universal:Subject:To:CC:References:X-Nvconfidentiality:From: Message-ID:Date:User-Agent:MIME-Version:In Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org Received-SPF: none client-ip=209.132.180.67; envelope-from=linux-kernel-owner@vger.kernel.org; helo=vger.kernel.org X-Spam-Score: 0.5 X-Spam-Score-Bar: / X-Spam-Action: no action X-Spam-Report: Action: no action Symbol: ARC_NA(0.00) Symbol: BAYES_SPAM(1.37) Symbol: R_DKIM_ALLOW(-0.20) Symbol: HAS_XOIP(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: TO_DN_SOME(0.00) Symbol: PRECEDENCE_BULK(0.00) Symbol: MIME_GOOD(-0.10) Symbol: RECEIVED_SPAMHAUS_FAIL(0. On 8/16/19 7:24 PM, jhubbard@nvidia.com wrote: > From: John Hubbard > DKIM-Signature: v=01 a a-sha256; c=0Elaxed/relaxed; d idia.com; s=01; > t=1566008674; bh=05Mai0va6k/z2enpQJ4Nfvbj5WByFxGAO1JwdIBbXio h PGP-Unive= rsal:From:To:CC:Subject:Date:Message-ID:X-Mailer: > In-Reply-To:References:MIME-Version:X-NVConfidentiality: > Content-Transfer-Encoding:Content-Type; > b=C3=96UDSde9XF/IsNteBaYOBWeKiHhWmeU9ekUJNvCviHssBDCtw0T+M/2TlEPEzomIT > fGXzIQNlGN6MXFbaBoyBmF/zjCu02TmTNExbVJ3/5N6PTyOuJFCx9ZN1/5gXsB11m1 > xAHIWE+VOZs4qqDeHDBqKZq+FaxQHNvGz0j6lyVBA70TfseNoZqZZrSil8uvaKJwKd > TQ1ht+AGWbw9p610JmaPb4u6o/eV6Ns8Sl3EVnjWWu94T6ISNIaWCiC6wQQF6L1YCH > G5Pjn+0rEjhk6XG4TyLudi5lWp3IVBHd8+WlWlnl+bvLCC55RUAjPJLn7LaVyVdh0F > nLHwm3bN2Jotg I cannot readily explain the above email glitch, but I did just now switch back to mailgw.nvidia.com for this patchset, in order to get the nice behav= ior of having "From:" really be my native NVIDIA email address. That's very nic= e, but if the glitches happen again, I'll switch back to using gmail for=20 git-send-email. Sorry about the weirdness. It does still let you apply the patch, I just now checked on that. thanks, --=20 John Hubbard NVIDIA