All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chris Leech <cleech@redhat.com>,
	Nilesh Javali <njavali@marvell.com>,
	John Meneghini <jmeneghi@redhat.com>,
	Lee Duncan <lduncan@suse.com>,
	Mike Christie <michael.christie@oracle.com>,
	Hannes Reinecke <hare@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	GR-QLogic-Storage-Upstream@marvell.com
Subject: Re: [PATCH 1/2] uio: introduce UIO_MEM_DMA_COHERENT type
Date: Thu, 1 Feb 2024 07:03:58 -0800	[thread overview]
Message-ID: <2024020125-bunt-nearest-242b@gregkh> (raw)
In-Reply-To: <20240201044637.GC14176@lst.de>

On Thu, Feb 01, 2024 at 05:46:37AM +0100, Christoph Hellwig wrote:
> As the least horrible way out this looks ok:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> Bt maybe you can add some commentary why this mem mode exists and
> why no one should be using it in new code?
> 

Good idea, and perhaps a kernel log warning when this is used as well
just to prevent anyone new from ever considering it.

thanks,

greg k-h

  reply	other threads:[~2024-02-01 15:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 19:17 [PATCH 0/2] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x Chris Leech
2024-01-31 19:17 ` [PATCH 1/2] uio: introduce UIO_MEM_DMA_COHERENT type Chris Leech
2024-01-31 21:28   ` Greg Kroah-Hartman
2024-01-31 21:44     ` Chris Leech
2024-02-01  4:44       ` Christoph Hellwig
2024-02-01  4:46   ` Christoph Hellwig
2024-02-01 15:03     ` Greg Kroah-Hartman [this message]
2024-03-12  8:40   ` Thomas Weißschuh
2024-01-31 19:17 ` [PATCH 2/2] cnic,bnx2,bnx2x: use UIO_MEM_DMA_COHERENT Chris Leech
2024-01-31 21:29   ` Greg Kroah-Hartman
2024-01-31 21:46     ` Chris Leech
2024-02-01  4:45     ` Christoph Hellwig
2024-01-31 21:27 ` [PATCH 0/2] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024020125-bunt-nearest-242b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=cleech@redhat.com \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=jmeneghi@redhat.com \
    --cc=lduncan@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michael.christie@oracle.com \
    --cc=netdev@vger.kernel.org \
    --cc=njavali@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.