Re: [PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Mike Rapoport
Hi Greg, On Wed, Jul 04, 2018 at 02:39:05PM +1000, Greg Ungerer wrote: > Hi Mike, > > On 04/07/18 14:22, Mike Rapoport wrote: > >On Wed, Jul 04, 2018 at 12:02:52PM +1000, Greg Ungerer wrote: > >>On 04/07/18 11:39, Greg Ungerer wrote: > >>>On 03/07/18 20:29, Mike Rapoport wrote: > In m68k the

Re: [PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Greg Ungerer
Hi Mike, On 04/07/18 14:22, Mike Rapoport wrote: On Wed, Jul 04, 2018 at 12:02:52PM +1000, Greg Ungerer wrote: On 04/07/18 11:39, Greg Ungerer wrote: On 03/07/18 20:29, Mike Rapoport wrote: In m68k the physical memory is described by [memory_start, memory_end] for !MMU variant and by

Re: [PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Mike Rapoport
On Wed, Jul 04, 2018 at 12:02:52PM +1000, Greg Ungerer wrote: > Hi Mike, > > On 04/07/18 11:39, Greg Ungerer wrote: > >On 03/07/18 20:29, Mike Rapoport wrote: > >>In m68k the physical memory is described by [memory_start, memory_end] for > >>!MMU variant and by m68k_memory array of memory ranges

Re: [PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Greg Ungerer
Hi Mike, On 04/07/18 11:39, Greg Ungerer wrote: On 03/07/18 20:29, Mike Rapoport wrote: In m68k the physical memory is described by [memory_start, memory_end] for !MMU variant and by m68k_memory array of memory ranges for the MMU version. This information is directly used to register the

Re: [PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Greg Ungerer
Hi Mike, On 03/07/18 20:29, Mike Rapoport wrote: In m68k the physical memory is described by [memory_start, memory_end] for !MMU variant and by m68k_memory array of memory ranges for the MMU version. This information is directly used to register the physical memory with memblock. The

[PATCH v3] block: fix Amiga partition support for disks >= 1 TB

2018-07-03 Thread Michael Schmitz
The Amiga partition parser module uses signed int for partition sector address and count, which will overflow for disks larger than 1 TB. Use u64 as type for sector address and size to allow using disks up to 2 TB without LBD support, and disks larger than 2 TB with LBD. The RBD format allows to

24/7 LOAN OFFER AT 3% INTEREST RATE

2018-07-03 Thread Harel Insurance Investments and Financial Services Ltd
Hello Are you desperately in need of a loan? Have you been denied of a loan from your bank or any institution? Do you need financial assistance? Do you need a loan to pay off your bills or buy a home? Do you want to have a business of your own and you need a Loan for your financial demands? if

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Michal Hocko
On Tue 03-07-18 18:47:51, Mike Rapoport wrote: > On Tue, Jul 03, 2018 at 05:14:01PM +0200, Michal Hocko wrote: > > On Tue 03-07-18 08:05:35, Matthew Wilcox wrote: > > > On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > > > > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Mike Rapoport
On Tue, Jul 03, 2018 at 05:14:01PM +0200, Michal Hocko wrote: > On Tue 03-07-18 08:05:35, Matthew Wilcox wrote: > > On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > > > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > > > > On Tue 03-07-18 13:29:54, Mike Rapoport

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Mike Rapoport
On Tue, Jul 03, 2018 at 05:14:01PM +0200, Michal Hocko wrote: > On Tue 03-07-18 08:05:35, Matthew Wilcox wrote: > > On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > > > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > > > > On Tue 03-07-18 13:29:54, Mike Rapoport

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Mike Rapoport
On Tue, Jul 03, 2018 at 08:05:35AM -0700, Matthew Wilcox wrote: > On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > > > On Tue 03-07-18 13:29:54, Mike Rapoport wrote: > > > > Add explicit casting to unsigned long to

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Michal Hocko
On Tue 03-07-18 08:05:35, Matthew Wilcox wrote: > On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > > > On Tue 03-07-18 13:29:54, Mike Rapoport wrote: > > > > Add explicit casting to unsigned long to the __va()

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Matthew Wilcox
On Tue, Jul 03, 2018 at 06:03:16PM +0300, Mike Rapoport wrote: > On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > > On Tue 03-07-18 13:29:54, Mike Rapoport wrote: > > > Add explicit casting to unsigned long to the __va() parameter > > > > Why is this needed? > > To make it

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Mike Rapoport
On Tue, Jul 03, 2018 at 04:20:54PM +0200, Michal Hocko wrote: > On Tue 03-07-18 13:29:54, Mike Rapoport wrote: > > Add explicit casting to unsigned long to the __va() parameter > > Why is this needed? To make it consitent with other architecures and asm-generic :) But more importantly,

Re: [PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Michal Hocko
On Tue 03-07-18 13:29:54, Mike Rapoport wrote: > Add explicit casting to unsigned long to the __va() parameter Why is this needed? > Signed-off-by: Mike Rapoport > --- > arch/m68k/include/asm/page_no.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [PATCH v7 1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)

2018-07-03 Thread Angelo Dureghello
Hi Vinod, On Tue, Jul 03, 2018 at 06:00:14PM +0530, Vinod wrote: > On 03-07-18, 12:37, Angelo Dureghello wrote: > > This patch adds a new fsl-edma-common module to allow new > > mcf-edma module code to use most of the fsl-edma code. > > > > Due to some differences between ColdFire edma (64

Re: [PATCH] block: fix Amiga partition support for disks >= 1 TB

2018-07-03 Thread jdow
On 20180703 00:22, Geert Uytterhoeven wrote: Hi Michael, On Tue, Jul 3, 2018 at 1:58 AM Michael Schmitz wrote: On Mon, Jul 2, 2018 at 8:29 PM, Geert Uytterhoeven wrote: + + /* Warn user if start_sect or nr_sects overflow u32 */ + if ((nr_sects > UINT_

Re: [PATCH v7 1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)

2018-07-03 Thread Vinod
On 03-07-18, 12:37, Angelo Dureghello wrote: > This patch adds a new fsl-edma-common module to allow new > mcf-edma module code to use most of the fsl-edma code. > > Due to some differences between ColdFire edma (64 channels) and > fsl-edma (32 channels), as register set offsets and some other >

[PATCH v7 2/2] dmaengine: fsl-edma: add ColdFire mcf5441x edma support

2018-07-03 Thread Angelo Dureghello
This patch adds support for ColdFire mcf5441x-family edma module. The ColdFire edma module is slightly different from fsl-edma, so a new driver is added. But most of the code is common between fsl-edma and mcf-edma so it has been collected into a separate common module fsl-edma-common (patch

[PATCH v7 1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)

2018-07-03 Thread Angelo Dureghello
This patch adds a new fsl-edma-common module to allow new mcf-edma module code to use most of the fsl-edma code. Due to some differences between ColdFire edma (64 channels) and fsl-edma (32 channels), as register set offsets and some other points as the different interrupt organization and other

[PATCH 3/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Mike Rapoport
In m68k the physical memory is described by [memory_start, memory_end] for !MMU variant and by m68k_memory array of memory ranges for the MMU version. This information is directly used to register the physical memory with memblock. The reserve_bootmem() calls are replaced with memblock_reserve()

[PATCH 1/3] m68k/bitops: convert __ffs to match generic declaration

2018-07-03 Thread Mike Rapoport
The generic bitops declare __ffs as static inline unsigned long __ffs(unsigned long word); Convert the m68k version to match the generic declaration. Signed-off-by: Mike Rapoport --- arch/m68k/include/asm/bitops.h | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff

[PATCH 0/3] m68k: switch to MEMBLOCK + NO_BOOTMEM

2018-07-03 Thread Mike Rapoport
Hi, These patches switch m68k boot time memory allocators from bootmem to memblock + no_bootmem. The first two patches update __ffs() and __va() definitions to be inline with other arches and asm-generic. This is required to avoid compilation warnings in mm/memblock.c and mm/nobootmem.c. The

[PATCH 2/3] m68k/page_no.h: force __va argument to be unsigned long

2018-07-03 Thread Mike Rapoport
Add explicit casting to unsigned long to the __va() parameter Signed-off-by: Mike Rapoport --- arch/m68k/include/asm/page_no.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/m68k/include/asm/page_no.h b/arch/m68k/include/asm/page_no.h index e644c4d..6bbe520 100644 ---

Re: [PATCH v6 1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)

2018-07-03 Thread Vinod
On 03-07-18, 10:52, Angelo Dureghello wrote: > On Tue, Jul 03, 2018 at 11:19:25AM +0530, Vinod wrote: > > On 01-07-18, 18:33, Angelo Dureghello wrote: > > > This patch adds a new fsl-edma-common module to allow new > > > mcf-edma module code to use most of the fsl-edma code. > > > > > > Due to

Re: [PATCH v6 1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)

2018-07-03 Thread Angelo Dureghello
Hi Vinod, many thanks ! On Tue, Jul 03, 2018 at 11:19:25AM +0530, Vinod wrote: > On 01-07-18, 18:33, Angelo Dureghello wrote: > > This patch adds a new fsl-edma-common module to allow new > > mcf-edma module code to use most of the fsl-edma code. > > > > Due to some differences between ColdFire

Re: [PATCH] block: fix Amiga partition support for disks >= 1 TB

2018-07-03 Thread Michael Schmitz
Hi Geert, Am 03.07.2018 um 19:22 schrieb Geert Uytterhoeven: Hi Michael, On Tue, Jul 3, 2018 at 1:58 AM Michael Schmitz wrote: On Mon, Jul 2, 2018 at 8:29 PM, Geert Uytterhoeven wrote: + + /* Warn user if start_sect or nr_sects overflow u32 */ + if ((nr_sects >

Re: [PATCH 1/5] m68k/io: Add missing ioremap define guards, fix typo

2018-07-03 Thread Geert Uytterhoeven
Hi Greg, On Tue, Jul 3, 2018 at 4:13 AM Greg Ungerer wrote: > On 02/07/18 23:35, Geert Uytterhoeven wrote: > >- Add missing define guard for ioremap_wt(), > >- Fix typo s/ioremap_fillcache/ioremap_fullcache/, > >- Add define guard for iounmap() for consistency with other > >

Re: [PATCH] block: fix Amiga partition support for disks >= 1 TB

2018-07-03 Thread Geert Uytterhoeven
Hi Michael, On Tue, Jul 3, 2018 at 1:58 AM Michael Schmitz wrote: > On Mon, Jul 2, 2018 at 8:29 PM, Geert Uytterhoeven > wrote: > >> + > >> + /* Warn user if start_sect or nr_sects overflow u32 */ > >> + if ((nr_sects > UINT_MAX || start_sect > UINT_MAX || > >> +

[PATCH v2] block: fix Amiga partition support for disks >= 1 TB

2018-07-03 Thread Michael Schmitz
The Amiga partition parser module uses signed int for partition sector address and count, which will overflow for disks larger than 1 TB. Use u64 as type for sector address and size to allow using disks up to 2 TB without LBD support, and disks larger than 2 TB with LBD. The RBD format allows to