From: Christoph Hellwig <hch@lst.de>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
robin.murphy@arm.com, hch@lst.de
Subject: Re: [PATCH v3] dma-mapping: set default segment_boundary_mask to ULONG_MAX
Date: Wed, 19 Aug 2020 07:09:22 +0200 [thread overview]
Message-ID: <20200819050922.GA19697@lst.de> (raw)
In-Reply-To: <20200815064726.20459-1-nicoleotsuka@gmail.com>
Applied to the dma-mapping tree. This should give us the whole merge
window to root out any obvious problems with drivers.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dma-mapping: set default segment_boundary_mask to ULONG_MAX
Date: Wed, 19 Aug 2020 07:09:22 +0200 [thread overview]
Message-ID: <20200819050922.GA19697@lst.de> (raw)
In-Reply-To: <20200815064726.20459-1-nicoleotsuka@gmail.com>
Applied to the dma-mapping tree. This should give us the whole merge
window to root out any obvious problems with drivers.
next prev parent reply other threads:[~2020-08-19 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 6:47 [PATCH v3] dma-mapping: set default segment_boundary_mask to ULONG_MAX Nicolin Chen
2020-08-15 6:47 ` Nicolin Chen
2020-08-19 5:09 ` Christoph Hellwig [this message]
2020-08-19 5: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=20200819050922.GA19697@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=robin.murphy@arm.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.