Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: manual merge of the arm64 tree with the dma-mapping tree
@ 2019-11-07 21:11 Stephen Rothwell
  2019-11-08 10:25 ` Catalin Marinas
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2019-11-07 21:11 UTC (permalink / raw)
  To: Catalin Marinas, Will Deacon, Christoph Hellwig
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Nicolas Saenz Julienne

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Hi all,

Today's linux-next merge of the arm64 tree got a conflict in:

  include/linux/dma-direct.h

between commit:

  b0817901ba21 ("dma-direct: check for overflows on 32 bit DMA addresses")

from the dma-mapping tree and commit:

  8b5369ea5809 ("dma/direct: turn ARCH_ZONE_DMA_BITS into a variable")

from the arm64 tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc include/linux/dma-direct.h
index 6db863c3eb93,d03af3605460..000000000000
--- a/include/linux/dma-direct.h
+++ b/include/linux/dma-direct.h
@@@ -3,11 -3,10 +3,13 @@@
  #define _LINUX_DMA_DIRECT_H 1
  
  #include <linux/dma-mapping.h>
 +#include <linux/memblock.h> /* for min_low_pfn */
  #include <linux/mem_encrypt.h>
  
+ extern unsigned int zone_dma_bits;
+ 
 +static inline dma_addr_t phys_to_dma(struct device *dev, phys_addr_t paddr);
 +
  #ifdef CONFIG_ARCH_HAS_PHYS_TO_DMA
  #include <asm/dma-direct.h>
  #else

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the arm64 tree with the dma-mapping tree
  2019-11-07 21:11 linux-next: manual merge of the arm64 tree with the dma-mapping tree Stephen Rothwell
@ 2019-11-08 10:25 ` Catalin Marinas
  0 siblings, 0 replies; 4+ messages in thread
From: Catalin Marinas @ 2019-11-08 10:25 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Will Deacon, Christoph Hellwig, Linux Next Mailing List,
	Linux Kernel Mailing List, Nicolas Saenz Julienne

On Fri, Nov 08, 2019 at 08:11:09AM +1100, Stephen Rothwell wrote:
> diff --cc include/linux/dma-direct.h
> index 6db863c3eb93,d03af3605460..000000000000
> --- a/include/linux/dma-direct.h
> +++ b/include/linux/dma-direct.h
> @@@ -3,11 -3,10 +3,13 @@@
>   #define _LINUX_DMA_DIRECT_H 1
>   
>   #include <linux/dma-mapping.h>
>  +#include <linux/memblock.h> /* for min_low_pfn */
>   #include <linux/mem_encrypt.h>
>   
> + extern unsigned int zone_dma_bits;
> + 
>  +static inline dma_addr_t phys_to_dma(struct device *dev, phys_addr_t paddr);
>  +
>   #ifdef CONFIG_ARCH_HAS_PHYS_TO_DMA
>   #include <asm/dma-direct.h>
>   #else

The resolution is fine. Thanks Stephen.

-- 
Catalin

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the arm64 tree with the dma-mapping tree
  2019-09-12 11:55 Stephen Rothwell
@ 2019-09-12 12:31 ` Will Deacon
  0 siblings, 0 replies; 4+ messages in thread
From: Will Deacon @ 2019-09-12 12:31 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Catalin Marinas, Christoph Hellwig, Linux Next Mailing List,
	Linux Kernel Mailing List, Mark Rutland

Hi Stephen,

On Thu, Sep 12, 2019 at 09:55:58PM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the arm64 tree got a conflict in:
> 
>   arch/arm64/include/asm/dma-mapping.h
> 
> between commit:
> 
>   5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h")
> 
> from the dma-mapping tree and commit:
> 
>   b907b80d7ae7 ("arm64: remove pointless __KERNEL__ guards")
> 
> from the arm64 tree.
> 
> I fixed it up (I just removed the file) and can carry the fix as
> necessary. This is now fixed as far as linux-next is concerned, but any
> non trivial conflicts should be mentioned to your upstream maintainer
> when your tree is submitted for merging.  You may also want to consider
> cooperating with the maintainer of the conflicting tree to minimise any
> particularly complex conflicts.

Thanks. Killing the file is the right thing to do.

Will


^ permalink raw reply	[flat|nested] 4+ messages in thread

* linux-next: manual merge of the arm64 tree with the dma-mapping tree
@ 2019-09-12 11:55 Stephen Rothwell
  2019-09-12 12:31 ` Will Deacon
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2019-09-12 11:55 UTC (permalink / raw)
  To: Catalin Marinas, Will Deacon, Christoph Hellwig
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Mark Rutland

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

Hi all,

Today's linux-next merge of the arm64 tree got a conflict in:

  arch/arm64/include/asm/dma-mapping.h

between commit:

  5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h")

from the dma-mapping tree and commit:

  b907b80d7ae7 ("arm64: remove pointless __KERNEL__ guards")

from the arm64 tree.

I fixed it up (I just removed the file) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-07 21:11 linux-next: manual merge of the arm64 tree with the dma-mapping tree Stephen Rothwell
2019-11-08 10:25 ` Catalin Marinas
  -- strict thread matches above, loose matches on Subject: below --
2019-09-12 11:55 Stephen Rothwell
2019-09-12 12:31 ` Will Deacon

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git