From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6211E428E3; Fri, 7 Apr 2023 09:27:02 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0936340E03; Fri, 7 Apr 2023 09:27:02 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id A9DCF40150 for ; Fri, 7 Apr 2023 09:27:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680852419; 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=ASsWEZM5YwO4C32RbOT+y4RL0jlgo7UUyqn09JqCcIA=; b=Wi8Df2GfrbwyyDaQaXLVxUG60DqCHJ1Xd4TItoLQadCvrHqqqhzKbHM35Xvfgk0KcTj6j0 LPfB2pyK0cikUPzOj2jd4C3ncQ7xXnAfIerUiXCZ40CkSNSZclLoEF4vkjSdl7r0FfxIy4 s4HIOvoC0otLIgLCddnCym+Hp8KLJ2o= Received: from mail-pj1-f69.google.com (mail-pj1-f69.google.com [209.85.216.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-247-mPETnwKqPa6X4fK6ekQGhg-1; Fri, 07 Apr 2023 03:26:50 -0400 X-MC-Unique: mPETnwKqPa6X4fK6ekQGhg-1 Received: by mail-pj1-f69.google.com with SMTP id 98e67ed59e1d1-23f5e9b81d5so99289a91.2 for ; Fri, 07 Apr 2023 00:26:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680852410; x=1683444410; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ASsWEZM5YwO4C32RbOT+y4RL0jlgo7UUyqn09JqCcIA=; b=5/hQr8F1ZPlkqG7RQBS7j5wmlih2TroWgy62w72pXuHXxHX4TurRZbmcE4zpMIBEGH n83dXkXrMGRDduFCSWpVLw3bf5ZKCG1AJxpofk8w+9mydqBdCMaDAYSADAa0/K9L/YJk Lg41Jjrg2RAmhXB+jjqwZ3TjKu4CntaAIbVs/+kaQ9BrVZQaOTMEqXimUNW+eV2JH6fE G0XX4PS3AiRa25rKjp2esemzwCU1u19eTJ9Y1AKut/NCH2jR1Gtc/RsqNvw3MZRZrnfS 82Ke+91h+0mgH6YZxWfvzP8/GCHhwXglqdbwNOzlsVWDI2daSbEJ0LAXpLCkCKDr+0VV ANsg== X-Gm-Message-State: AAQBX9c5xMQDLxCbIqr2XFLITqVeHXJM5KXcJ1thBJJ4x7OL68sAl1rg Qt2qZ39NF9zYu3/ALWnya8cJM1S0eXQ+Uaha/s8S62Gj4pmN3j0ZCOPRylTjtk0BPcWMxYbhhO+ uxESV+3U3CGSjaoBN1o0= X-Received: by 2002:a05:6a00:2ea3:b0:625:ccea:1627 with SMTP id fd35-20020a056a002ea300b00625ccea1627mr829161pfb.5.1680852409813; Fri, 07 Apr 2023 00:26:49 -0700 (PDT) X-Google-Smtp-Source: AKy350aoQaCmx72m2+p+d7JZ+gjrGuvVwYyjXUpJINm2mbVnuYhydy3+uYcy+GcHh8otZSxYIUZg1+EERDBwb3R4e2Y= X-Received: by 2002:a05:6a00:2ea3:b0:625:ccea:1627 with SMTP id fd35-20020a056a002ea300b00625ccea1627mr829144pfb.5.1680852409399; Fri, 07 Apr 2023 00:26:49 -0700 (PDT) MIME-Version: 1.0 References: <20221230095853.1323616-1-nipun.gupta@amd.com> <20230104051936.2456411-1-nipun.gupta@amd.com> <0d356823-b198-ebd1-7a28-b678ae9edaf9@intel.com> <0fa0e21a-3c41-6a51-4b9e-3421b63c0369@amd.com> In-Reply-To: <0fa0e21a-3c41-6a51-4b9e-3421b63c0369@amd.com> From: David Marchand Date: Fri, 7 Apr 2023 09:26:38 +0200 Message-ID: Subject: Re: [PATCH v2] vfio: do not coalesce DMA mappings To: Nipun Gupta , "Burakov, Anatoly" Cc: "dev@dpdk.org" , "thomas@monjalon.net" , "Yigit, Ferruh" , "Agarwal, Nikhil" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello Nipun, Anatoly, On Fri, Apr 7, 2023 at 8:13=E2=80=AFAM Nipun Gupta wr= ote: > > The patch probably shouldn't include the mailmap changes :) Mailmap changes can be done by the submitter. So Nipun did nothing wrong. > > I see in "git log" that all the mailmap changes are with the patch > submitted, probably as it shows checkpatch warning, so it seems this > should be fine? If a submitter includes the mailmap change in his patches, it is fine. Otherwise, the maintainer that merges the first patch of a new contributor will fix the mailmap at the same time. --=20 David Marchand