All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Christoph Hellwig <hch@lst.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH 2/2] dma-mapping: remove dma_max_pfn
Date: Fri, 28 Jun 2019 08:00:24 +0200	[thread overview]
Message-ID: <20190628060024.GA27433@lst.de> (raw)
In-Reply-To: <2cf24650-512e-688d-fe24-119d36ed92f5@free.fr>

On Tue, Jun 25, 2019 at 01:45:38PM +0200, Marc Gonzalez wrote:
> Hello Christoph,
> 
> There are some typos in the commit message that make it harder
> (for me) to parse.

The fixes looks good to me.  Ulf, do you want me to resend?

  reply	other threads:[~2019-06-28  6:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25  9:20 get rid of dma_max_pfn Christoph Hellwig
2019-06-25  9:20 ` Christoph Hellwig
2019-06-25  9:20 ` Christoph Hellwig
2019-06-25  9:20 ` Christoph Hellwig
2019-06-25  9:20 ` [PATCH 1/2] mmc: let the dma map ops handle bouncing Christoph Hellwig
2019-06-25  9:20   ` Christoph Hellwig
2019-06-25  9:20   ` Christoph Hellwig
2019-07-08 11:55   ` Ulf Hansson
2019-07-08 11:55     ` Ulf Hansson
2019-07-08 11:55     ` Ulf Hansson
2019-07-08 11:55     ` Ulf Hansson
2019-06-25  9:20 ` [PATCH 2/2] dma-mapping: remove dma_max_pfn Christoph Hellwig
2019-06-25  9:20   ` Christoph Hellwig
2019-06-25  9:20   ` Christoph Hellwig
2019-06-25 11:45   ` Marc Gonzalez
2019-06-28  6:00     ` Christoph Hellwig [this message]
2019-07-08 11:55   ` Ulf Hansson
2019-07-08 11:55     ` Ulf Hansson
2019-07-08 11:55     ` Ulf Hansson
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11  7:09 get rid of dma_max_pfn Christoph Hellwig
2019-04-11  7:09 ` [PATCH 2/2] dma-mapping: remove dma_max_pfn Christoph Hellwig
2019-04-11  7:09   ` Christoph Hellwig
2019-04-11  7:09   ` Christoph Hellwig

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=20190628060024.GA27433@lst.de \
    --to=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    --cc=ulf.hansson@linaro.org \
    /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.