The pull request you sent on Sat, 24 Oct 2020 16:19:35 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.10-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1b307ac87075c3207c345822ea276fe4f28481d7
Thank you!
--
Deet-doot-dot, I am a bot.
rs/hch/dma-mapping.git tags/dma-mapping-5.10-1
for you to fetch changes up to 6857a5ebaabc5b9d989872700b4b71dd2a6d6453:
dma-mapping: document dma_{alloc,free}_pages (2020-10-23 12:07:46 +0200)
--------
dma-mapping fixes for 5.10:
- docume
The pull request you sent on Thu, 20 Aug 2020 18:41:58 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.9-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d271b51c60ebe71e0435a9059b315a3d8bb8a099
Thank you!
--
Deet-doot-dot, I am a bot.
to fetch changes up to d7e673ec2c8e0ea39c4c70fc490d67d7fbda869d:
dma-pool: Only allocate from CMA when in same memory zone (2020-08-14
16:27:05 +0200)
dma-mapping fixes for 5.9
- fix out more fallout from the dma-pool changes
The pull request you sent on Sun, 19 Jul 2020 09:39:27 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8c18fc6344568bdc131436be0345d82da512bfef
Thank you!
--
Deet-doot-dot, I am a bot.
apping.git tags/dma-mapping-5.8-6
for you to fetch changes up to d9765e41d8e9ea2251bf73735a2895c8bad546fc:
dma-pool: do not allocate pool memory from CMA (2020-07-14 15:46:32 +0200)
--------
dma-mapping fixes for 5.8:
- ensure we always
The pull request you sent on Fri, 10 Jul 2020 17:45:06 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1bfde037425d91d1d615d30ec362f5f5c1ca0dd2
Thank you!
--
Deet-doot-dot, I am a bot.
68d237056e007c88031d80900cdba0945121a287:
scatterlist: protect parameters of the sg_table related macros (2020-07-06
16:07:25 +0200)
dma-mapping fixes for 5.8
- add a warning when the atomic pool is depleted (David Rientjes)
- protect the parameters of
The pull request you sent on Sat, 27 Jun 2020 09:49:02 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f05baa066d0f6a38f0624c28008fb2f53cd00e17
Thank you!
--
Deet-doot-dot, I am a bot.
changes up to 8e36baf97b252cdcafa53589e8227cbb1e85f0b0:
dma-remap: align the size in dma_common_*_remap() (2020-06-23 14:14:41 +0200)
dma-mapping fixes for 5.8:
- fix dma coherent mmap in nommu (me)
- more AMD SEV fallout (David
The pull request you sent on Wed, 17 Jun 2020 09:27:16 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1b5044021070efa3259f3e9548dc35d1eb6aa844
Thank you!
--
Deet-doot-dot, I am a bot.
apping.git tags/dma-mapping-5.8-3
for you to fetch changes up to dbed452a078d56bc7f1abecc3edd6a75e8e4484e:
dma-pool: decouple DMA_REMAP from DMA_COHERENT_POOL (2020-06-15 08:35:30
+0200)
--------
dma-mapping fixes for 5.8
- fixes for the
The pull request you sent on Wed, 14 Aug 2019 16:12:17 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.3-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e83b009c5c366b678c7986fa6c1d38fed06c954c
Thank you!
--
Deet-doot-dot, I am a bot.
rs/hch/dma-mapping.git tags/dma-mapping-5.3-4
for you to fetch changes up to 33dcb37cef741294b481f4d889a465b8091f11bf:
dma-mapping: fix page attributes for dma_mmap_* (2019-08-10 19:52:45 +0200)
--------
dma-mapping fixes for 5.3-rc
Hi Christoph,
On Thu, 8 Aug 2019 00:37:22 +0200 Christoph Hellwig wrote:
>
> That commit should not have been in that tree at all, let me check what
> went wrong.
I was wondering about that. Now it has caused build problems further
along, so I have reverted the merge of the branch (along with m
On Thu, Aug 08, 2019 at 08:29:48AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the dma-mapping-fixes tree, today's linux-next build
> (x86_64 allmodconfig) failed like this:
>
> /home/sfr/next/next/mm/migrate.c: In function 'migrate_vma_collect':
&
Hi all,
After merging the dma-mapping-fixes tree, today's linux-next build
(x86_64 allmodconfig) failed like this:
/home/sfr/next/next/mm/migrate.c: In function 'migrate_vma_collect':
/home/sfr/next/next/mm/migrate.c:2350:61: error: 'mm_walk' undeclared (fi
Hi Christoph,
Commit
e31614683919 ("Revert "arm64/xen: fix xen-swiotlb cache flushing"")
is missing a Signed-off-by from its author and committer.
Reverts are commits too. Also, it can be useful to have an explanation
for the revert in the commit message.
--
Cheers,
Stephen Rothwell
pgpB
Hi Christoph,
On Wed, 23 Jan 2019 23:09:15 +1100 Stephen Rothwell
wrote:
>
> On Wed, 23 Jan 2019 08:19:33 +0100 Christoph Hellwig wrote:
> >
> > On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> > > - SHA1 should be at least 12 digits long
> >
> > When did we decide o
> > This later patch appears to already be in Linus' tree as commit
> > fe76fc6aaf53 (also with an incorrect Fixes tag :-()
>
> That commit is not from the dma-mapping tree..
This is in my linux-next tree today:
$ git log --oneline origin/master..dma-mapping-fixes/for-linus
On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> Hi Christoph,
>
> In commit
>
> 702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")
Hi Christoph,
I'm not subscribed to any of the mailing list that the above patch was
reviewed on, so I'm replying here because it is t
On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> Hi Christoph,
>
> In commit
>
> 702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")
>
> Fixes tag
>
> Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")
>
> has these problem(s):
>
> - SHA1 s
Hi Christoph,
In commit
702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")
Fixes tag
Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
8218a55b6b91 ("sbitmap: Protect swap_lock fro
The pull request you sent on Sun, 6 Jan 2019 19:28:46 +0100:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.21-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e2b745f469ec0f3165ba5ffaee3ce40f98d77878
Thank you!
--
Deet-doot-dot, I am a bot.
8:29 +0100)
--------
dma-mapping fixes for Linux 4.21-rc1
Fix various regressions introduced in this cycles:
- fix dma-debug tracking for the map_page / map_single consolidatation
- properly stub out DMA mapping symbols for !HAS_DMA builds to avoid
link failures
- fix AMD Gart direct mappings
-
The pull request you sent on Sun, 25 Nov 2018 09:35:52 +0100:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.20-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d6d460b89378b1bc6715574cdafd748ba59d5a27
Thank you!
--
Deet-doot-dot, I am a bot.
Hi Christoph,
Commit
05e13bb57e6f ("swiotlb: silent unwanted warning "buffer is full"")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpRva4c8tOGp.pgp
Description: OpenPGP digital signature
On Tue, 24 Apr 2018, Christoph Hellwig wrote:
> On Tue, Apr 24, 2018 at 11:54:26PM -0700, David Rientjes wrote:
> > Shouldn't that test for dev->coherent_dma_mask < DMA_BIT_MASK(32) be more
> > accurately <=?
>
> No, it should really be <. The exactly 32-bit case is already covered
> with GFP_
On Tue, Apr 24, 2018 at 11:54:26PM -0700, David Rientjes wrote:
> Shouldn't that test for dev->coherent_dma_mask < DMA_BIT_MASK(32) be more
> accurately <=?
No, it should really be <. The exactly 32-bit case is already covered
with GFP_DMA32. Eventualy it should be < 24-bit with a separate
GFP
.git tags/dma-mapping-4.17-3
>
> for you to fetch changes up to 60695be2bb6b0623f8e53bd9949d582a83c6d44a:
>
> dma-mapping: postpone cpu addr translation on mmap (2018-04-23 14:44:24
> +0200)
>
> ------------
> A f
60695be2bb6b0623f8e53bd9949d582a83c6d44a:
dma-mapping: postpone cpu addr translation on mmap (2018-04-23 14:44:24 +0200)
A few small dma-mapping fixes for Linux 4.17-rc3:
- don't loop to try GFP_DMA allocations if ZONE_DMA is not actually
en
This set of patches fixes the coding style issues in rtsx_transport.c, and
dds a missing call dma_mapping_error() after dma_map_single().
Changes since v2
* Incorporated Joshua Clayton's suggestions regarding the block comments
This set of patches fixes the coding style issues in rtsx_transport.c, and
dds a missing call dma_mapping_error() after dma_map_single().
This set of patches fixes the coding style issues in rtsx_transport.c, and adds
a missing dma_mapping_error check.
On Sun, 2015-11-22 at 17:25 +0100, Christoph Hellwig wrote:
> Hi Andew,
>
> below are a couple of fixes for the dma mapping series for architectures
> now covered by the automatic build bot. Thanks to Dan and Guenter for
> finding these!
>
Thanks for doing this, Christoph.
For the c6x bits:
Ac
Reported-by: Guenter Roeck
Signed-off-by: Christoph Hellwig http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Reported-by: Guenter Roeck
Signed-off-by: Christoph Hellwig
---
arch/arc/mm/dma.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arc/mm/dma.c b/arch/arc/mm/dma.c
index da289cb..695029f 100644
--- a/arch/arc/mm/dma.c
+++ b/arch/arc/mm/dma.c
@@ -46,7 +46,7 @@ stat
Reported-by: Guenter Roeck
Signed-off-by: Christoph Hellwig
---
arch/c6x/include/asm/dma-mapping.h | 6 ++
arch/c6x/kernel/dma.c | 2 ++
arch/c6x/mm/dma-coherent.c | 10 --
3 files changed, 12 insertions(+), 6 deletions(-)
diff --git a/arch/c6x/include/asm/dma
Hi Andew,
below are a couple of fixes for the dma mapping series for architectures
now covered by the automatic build bot. Thanks to Dan and Guenter for
finding these!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Hi Linus,
I would like to ask You for pulling a few fixes for dma-mapping and CMA
subsystems for v3.16.
The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:
Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)
are available in the git repository at:
git://git.linaro.org/peopl
Hi Linus,
I would like to ask You for pulling fixes for dma-mapping subsystem for
ARM and x86 architecture for v3.14.
The following changes since commit b28a960c42fcd9cfc987441fa6d1c1a471f0f9ed:
Linux 3.14-rc2 (2014-02-09 18:15:47 -0800)
are available in the git repository at:
git://git.li
Hi Linus,
I would like to ask for pulling some minor fixes for both CMA
(Contiguous Memory Allocator) and DMA-mapping framework for v3.7-rc3.
The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
Linux 3.7
Hi Linus,
I would like to ask for pulling another set of fixes for ARM dma-mapping
subsystem. Commit e9da6e9905e6 replaced custom consistent buffer
remapping code with generic vmalloc areas. It however introduced some
regressions caused by limited support for allocations in atomic context.
This se
Hi Linus,
I woukd like to ask you again for pulling another set of minor fixups
for recently merged Contiguous Memory Allocator and ARM DMA-mapping
changes. Those patches fix mysterious crashes on systems with CMA and
Himem enabled as well as some corner cases caused by typical off-by-one
bug. I'm
44 matches
Mail list logo
