linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the rdma tree with the arm-soc tree
@ 2020-11-25  1:33 Stephen Rothwell
  2020-11-25  8:36 ` Christoph Hellwig
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2020-11-25  1:33 UTC (permalink / raw)
  To: Doug Ledford, Jason Gunthorpe, Olof Johansson, Arnd Bergmann, ARM
  Cc: Maxime Ripard, Christoph Hellwig, Jason Gunthorpe,
	Jason Gunthorpe, Linux Kernel Mailing List,
	Linux Next Mailing List

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

Hi all,

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

  include/linux/dma-mapping.h

between commit:

  16fee29b0735 ("dma-mapping: remove the dma_direct_set_offset export")

from the arm-soc tree and commit:

  172292be01db ("dma-mapping: remove dma_virt_ops")

from the rdma 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-mapping.h
index 199d85285246,2aaed35b556d..000000000000
--- a/include/linux/dma-mapping.h
+++ b/include/linux/dma-mapping.h
@@@ -558,6 -558,11 +558,4 @@@ static inline int dma_mmap_wc(struct de
  #define dma_unmap_len_set(PTR, LEN_NAME, VAL)    do { } while (0)
  #endif
  
- extern const struct dma_map_ops dma_virt_ops;
 -/*
 - * Legacy interface to set up the dma offset map.  Drivers really should not
 - * actually use it, but we have a few legacy cases left.
 - */
 -int dma_direct_set_offset(struct device *dev, phys_addr_t cpu_start,
 -		dma_addr_t dma_start, u64 size);
--
  #endif /* _LINUX_DMA_MAPPING_H */

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

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

* Re: linux-next: manual merge of the rdma tree with the arm-soc tree
  2020-11-25  1:33 linux-next: manual merge of the rdma tree with the arm-soc tree Stephen Rothwell
@ 2020-11-25  8:36 ` Christoph Hellwig
  0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2020-11-25  8:36 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Doug Ledford, Jason Gunthorpe, Olof Johansson, Arnd Bergmann,
	ARM, Maxime Ripard, Christoph Hellwig, Jason Gunthorpe,
	Jason Gunthorpe, Linux Kernel Mailing List,
	Linux Next Mailing List

On Wed, Nov 25, 2020 at 12:33:51PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the rdma tree got a conflict in:
> 
>   include/linux/dma-mapping.h
> 
> between commit:
> 
>   16fee29b0735 ("dma-mapping: remove the dma_direct_set_offset export")
> 
> from the arm-soc tree and commit:
> 
>   172292be01db ("dma-mapping: remove dma_virt_ops")
> 
> from the rdma 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.

Thanks, the trivial fixup looks obviously good.

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

end of thread, other threads:[~2020-11-25  8:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-25  1:33 linux-next: manual merge of the rdma tree with the arm-soc tree Stephen Rothwell
2020-11-25  8:36 ` Christoph Hellwig

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).