linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guo Ren <ren_guo@c-sky.com>, Christoph Hellwig <hch@lst.de>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: manual merge of the csky tree with the dma-mapping tree
Date: Fri, 30 Aug 2019 10:16:34 +1000	[thread overview]
Message-ID: <20190830101634.21dca185@canb.auug.org.au> (raw)

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

Hi all,

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

  arch/csky/mm/dma-mapping.c

between commit:

  8e3a68fb55e0 ("dma-mapping: make dma_atomic_pool_init self-contained")

from the dma-mapping tree and commit:

  4af9027d3f40 ("csky/dma: Fixup cache_op failed when cross memory ZONEs")

from the csky 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 arch/csky/mm/dma-mapping.c
index 602a60d47a94,106ef02a8f89..000000000000
--- a/arch/csky/mm/dma-mapping.c
+++ b/arch/csky/mm/dma-mapping.c
@@@ -14,33 -14,12 +14,6 @@@
  #include <linux/version.h>
  #include <asm/cache.h>
  
- void arch_dma_prep_coherent(struct page *page, size_t size)
 -static int __init atomic_pool_init(void)
--{
- 	if (PageHighMem(page)) {
- 		unsigned int count = PAGE_ALIGN(size) >> PAGE_SHIFT;
- 
- 		do {
- 			void *ptr = kmap_atomic(page);
- 			size_t _size = (size < PAGE_SIZE) ? size : PAGE_SIZE;
- 
- 			memset(ptr, 0, _size);
- 			dma_wbinv_range((unsigned long)ptr,
- 					(unsigned long)ptr + _size);
- 
- 			kunmap_atomic(ptr);
- 
- 			page++;
- 			size -= PAGE_SIZE;
- 			count--;
- 		} while (count);
- 	} else {
- 		void *ptr = page_address(page);
- 
- 		memset(ptr, 0, size);
- 		dma_wbinv_range((unsigned long)ptr, (unsigned long)ptr + size);
- 	}
 -	return dma_atomic_pool_init(GFP_KERNEL, pgprot_noncached(PAGE_KERNEL));
--}
 -postcore_initcall(atomic_pool_init);
--
  static inline void cache_op(phys_addr_t paddr, size_t size,
  			    void (*fn)(unsigned long start, unsigned long end))
  {

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

                 reply	other threads:[~2019-08-30  0:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190830101634.21dca185@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ren_guo@c-sky.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;
as well as URLs for NNTP newsgroup(s).