Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Fuxin Zhang <zhangfx@lemote.com>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <james.hogan@imgtec.com>,
	linux-mips@linux-mips.org,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V9 2/4] MIPS: Implement dma_map_ops::get_cache_alignment()
Date: Mon, 6 Nov 2017 19:21:48 +0100	[thread overview]
Message-ID: <20171106182148.GA29657@lst.de> (raw)
In-Reply-To: <1508742767-28366-2-git-send-email-chenhc@lemote.com>

This doesn't apply to the current dma mapping tree:

	http://git.infradead.org/users/hch/dma-mapping.git/shortlog/refs/heads/for-next

so even if I were to get the proper ACKs it would need a resend.

  parent reply	other threads:[~2017-11-06 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171023071025epcas4p3e9b9c0af7c0a34561f0d57a20a4f9946@epcas4p3.samsung.com>
     [not found] ` <1508742767-28366-1-git-send-email-chenhc@lemote.com>
2017-10-24 13:30   ` [PATCH V9 1/4] dma-mapping: Rework dma_get_cache_alignment() Marek Szyprowski
     [not found]     ` <tencent_06493D0500CE277740BDF088@qq.com>
2017-10-25  7:21       ` Marek Szyprowski
     [not found]         ` <tencent_6576ECDE049EE8921F2D13BB@qq.com>
     [not found]           ` <tencent_56D97C65293D16191A2D88C9@qq.com>
2017-11-03  5:14             ` Christoph Hellwig
2017-10-24 19:11   ` Mark Greer
2017-11-06 18:18   ` Christoph Hellwig
     [not found]   ` <1508742767-28366-2-git-send-email-chenhc@lemote.com>
2017-11-06 18:21     ` Christoph Hellwig [this message]
2017-11-10 12:30   ` 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=20171106182148.GA29657@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=chenhc@lemote.com \
    --cc=james.hogan@imgtec.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=martin.petersen@oracle.com \
    --cc=ralf@linux-mips.org \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=zhangfx@lemote.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox