Received: by 2002:a05:7412:bbc7:b0:fc:a2b0:25d7 with SMTP id kh7csp2662038rdb; Mon, 5 Feb 2024 13:35:03 -0800 (PST) X-Google-Smtp-Source: AGHT+IF0QuP/T3wKwpVf8fcr8/nBme5fbuctQJvgplOx32BtWkzmNfnORDbZmy8JGTlpZLTsO1GN X-Received: by 2002:a05:6214:d6d:b0:686:a20c:faf with SMTP id 13-20020a0562140d6d00b00686a20c0fafmr1070053qvs.12.1707168903308; Mon, 05 Feb 2024 13:35:03 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCX+NCEdJjG6DVnFWO4H070Qq1g712xeXWWTX0TC9va00QjmmOn9xq7d3onuZmWG0gW3+PMNktTFqeiGdrHHhLntpZOHHu6KJz+YPsR8aw== Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id a13-20020a0ccdcd000000b0067f2c23a115si863676qvn.163.2024.02.05.13.35.03 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 05 Feb 2024 13:35:03 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-53874-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@redhat.com header.s=mimecast20190719 header.b=EyOISEu9; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-53874-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-53874-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 1458F1C2714F for ; Mon, 5 Feb 2024 21:35:03 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id CADE384A30; Mon, 5 Feb 2024 19:53:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="EyOISEu9" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 929AB82D7A for ; Mon, 5 Feb 2024 19:53:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707162801; cv=none; b=IZ2WEWcE+sEDKFIQZoL+cN3I4uTFSrSHVt87tlAEp2C3twSRmBuN0JLfc0cAoc9F0fCMdhyZxsYYYv8uAVIcNrhSOQ8IJUKCErF+qbtb3N9V+W6NaQvsKVLY3X4A53slDrt23PQcXS2s2ih4/gmL2pKTwcW5YMR2dZwQZe1i/w4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707162801; c=relaxed/simple; bh=u/VKs/3EPpWVrRldc29EujFjC9yGn/bWji2MkiRM3Sw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=iZn7q9vmHkMY0QWWE9n5OI8fYi5L9SFOT/+E4WgTu0jDLZiTRK/9jS2Bb5ZFMgN0KvvZVr56QAIYNRTCUCr+4PH71MdNL4h1DNN5I7K4w9HU6EnSGAEZND2Mo2FGvmTgvwyA97eLmsudcrngthlP2tpuhDrXb06yRQWMUzJfCCs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=EyOISEu9; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1707162798; 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: in-reply-to:in-reply-to:references:references; bh=VNtm/2qBOdXruRpXqj+cGjGSujDgnFJiILWoI+l5br8=; b=EyOISEu9NR4+o5RyddqvwE99BvCJlXLks5sZ6u9Yof7tQGjt3pSrhxNDqmiSb848ilPc4t bhnnoIS202hQrjGzmWDDiD7Y3OFsHUeQdoZVsf+nLIQVhaMJqSW7z/xyRQMk9uuYC+t+Lt gqD7i+2QtzNuaORaqeFTpySGSN1CXoA= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-508-CxRN5HyxPny_tbrKO0hGEg-1; Mon, 05 Feb 2024 14:53:14 -0500 X-MC-Unique: CxRN5HyxPny_tbrKO0hGEg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 940E21C04338; Mon, 5 Feb 2024 19:53:13 +0000 (UTC) Received: from rhel-developer-toolbox-latest (unknown [10.2.16.180]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 639DA1C060AF; Mon, 5 Feb 2024 19:53:12 +0000 (UTC) Date: Mon, 5 Feb 2024 11:53:10 -0800 From: Chris Leech To: Simon Horman Cc: Greg Kroah-Hartman , Nilesh Javali , Christoph Hellwig , John Meneghini , Lee Duncan , Mike Christie , Hannes Reinecke , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, GR-QLogic-Storage-Upstream@marvell.com Subject: Re: [PATCH v5 4/4] uio_dmem_genirq: UIO_MEM_DMA_COHERENT conversion Message-ID: References: <20240201233400.3394996-1-cleech@redhat.com> <20240201233400.3394996-5-cleech@redhat.com> <20240204101903.GA916983@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240204101903.GA916983@kernel.org> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.7 On Sun, Feb 04, 2024 at 10:19:03AM +0000, Simon Horman wrote: > On Thu, Feb 01, 2024 at 03:34:00PM -0800, Chris Leech wrote: .. > > @@ -264,7 +257,8 @@ static int uio_dmem_genirq_probe(struct platform_device *pdev) > > " dynamic and fixed memory regions.\n"); > > break; > > } > > - uiomem->memtype = UIO_MEM_PHYS; > > + uiomem->memtype = UIO_MEM_DMA_COHERENT; > > + uiomem->dma_device = &pdev->dev, > > Hi Chris, > > a nit from my side. > > Probably the ',' would be better written as a ';' here. > I don't think this is a bug, but using comma like this is > somewhat unexpected and confusing. > > Flagged by clang-17 with -Wcomma That's an embarrassing typo to slip through. I'll fix this,and add the kdoc comments for the API additions. Thanks, - Chris