On 7/30/19 10:53 PM, Heiner Kallweit wrote:
> On 31.07.2019 02:12, Tao Ren wrote:
>> On 7/29/19 11:00 PM, Heiner Kallweit wrote:
>>> On 30.07.2019 07:05, Tao Ren wrote:
On 7/29/19 8:35 PM, Andrew Lunn wrote:
> On Mon, Jul 29, 2019 at 05:25:32PM -0700, Tao Ren wrote:
>> BCM54616S
Due to commit 4a6d8cf90017 ("powerpc/mm: don't use pte_alloc_kernel()
until slab is available on PPC32"), pte_alloc_kernel() cannot be used
during early KASAN init.
Fix it by using memblock_alloc() instead.
Reported-by: Erhard F.
Fixes: 2edb16efc899 ("powerpc/32: Add KASAN support")
Darrick,
On 2019/07/30 10:17, Darrick J. Wong wrote:
> On Mon, Jul 22, 2019 at 11:50:12AM +0200, Christoph Hellwig wrote:
>> Hi all,
>>
>> this series cleans up the xfs writepage code and then lifts it to
>> fs/iomap.c so that it could be use by other file system. I've been
>> wanting to this
On 7/30/19 1:51 AM, Alexandre Ghiti wrote:
In order to avoid wasting user address space by using bottom-up mmap
allocation scheme, prefer top-down scheme when possible.
Before:
root@qemuriscv64:~# cat /proc/self/maps
0001-00016000 r-xp fe:00 6389 /bin/cat.coreutils
Hi Suzuki,
On 7/31/2019 11:28 AM, Sai Prakash Ranjan wrote:
Add coresight components found on Qualcomm SDM845 SoC.
Signed-off-by: Sai Prakash Ranjan
Reviewed-by: Mathieu Poirier
Acked-by: Suzuki K Poulose
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 451 +++
1 file
From 31753a44c62c4fdf6e8a72994ae6861dbde49c11 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell
Date: Wed, 31 Jul 2019 16:00:52 +1000
Subject: [PATCH] xilinx_uartps.c: suppress "may be used uninitialised" warning
A powerpc allyesconfig build produces this warning:
In file included from
Sorry for the delayed response.
On (07/24/19 14:27), Petr Mladek wrote:
[..]
> > And this is where the idea of "disconnecting" those CPUs from main
> > logbuf come from.
> >
> > So what we can do:
> > - smp_send_stop()
> > - disconnect all-but-self from logbuf (via printk-safe)
>
> printk_safe
Hi Thomas,
again sorry for jumping in..
On 19-07-30 18:26, Thomas Preston wrote:
> On 30/07/2019 15:58, Mark Brown wrote:
> > On Tue, Jul 30, 2019 at 01:09:36PM +0100, Thomas Preston wrote:
> >
> >> index ..0f82a88bc1a4
> >> --- /dev/null
> >> +++ b/sound/soc/codecs/tda7802.c
> >>
Hi all,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
mm/memcontrol.c: In function 'invalidate_reclaim_iterators':
mm/memcontrol.c:1160:11: warning: suggest parentheses around assignment used as
truth value [-Wparentheses]
}
This builds module objects, so [M] makes sense.
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.modpost | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/Makefile.modpost b/scripts/Makefile.modpost
index 6e328190d609..6c237af41417 100644
---
On Tue, Jul 30, 2019 at 12:42:07PM -0700, Andrew Morton wrote:
> On Mon, 29 Jul 2019 17:20:52 +0900 Minchan Kim wrote:
>
> > > > @@ -1022,7 +1023,16 @@ static unsigned long zap_pte_range(struct
> > > > mmu_gather *tlb,
> > > > flush_tlb_batched_pending(mm);
> > > >
On 22.07.19 09:46, Arnd Bergmann wrote:
Building the privcmd code as a loadable module on ARM, we get
a link error due to the private cache management functions:
ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined!
Move the code into a new that is always built in when Xen is
On 30.07.19 20:34, Souptick Joarder wrote:
'commit df9bde015a72 ("xen/gntdev.c: convert to use vm_map_pages()")'
breaks gntdev driver. If vma->vm_pgoff > 0, vm_map_pages()
will:
- use map->pages starting at vma->vm_pgoff instead of 0
- verify map->count against vma_pages()+vma->vm_pgoff
Hi all,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/ocfs2/xattr.c:1493:13: warning: 'ocfs2_xa_add_entry' defined but not used
[-Wunused-function]
static void ocfs2_xa_add_entry(struct ocfs2_xa_loc *loc, u32 name_hash)
On 07/30/2019 09:04 PM, Vignesh Raghavendra wrote:
>>> + */
>>> +static int spi_nor_exec_op(struct spi_nor *nor, struct spi_mem_op *op,
>>> + u64 *addr, void *buf, size_t len)
>>> +{
>>> + int ret;
>>> + bool usebouncebuf = false;
>> I don't think we need a bounce buffer
[ sorry for a late reply too, somehow I missed this thread before ]
On Tue, Jul 30, 2019 at 10:14:15AM +0200, Michal Hocko wrote:
> [Sorry for a late reply]
>
> On Mon 15-07-19 17:55:07, Hoan Tran OS wrote:
> > Hi,
> >
> > On 7/12/19 10:00 PM, Michal Hocko wrote:
> [...]
> > > Hmm, I thought
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga.git
tags/fpga-for-5.4
for you to fetch changes up to
Joe Perches 於 2019年7月31日週三 下午2:06寫道：
>
> On Wed, 2019-07-31 at 10:45 +0800, Fuqian Huang wrote:
> > In drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c,
> > amdgpu_ih_process calls DRM_DEBUG which calls drm_dbg and
> > finally calls printk.
> > As amdgpu_ih_process is called from an interrupt handler,
> >
On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the akpm-current tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> mm/memcontrol.c: In function 'invalidate_reclaim_iterators':
> mm/memcontrol.c:1160:11: warning: suggest
On 7/30/19, 9:23 PM, "Paul Walmsley" wrote:
On Tue, 30 Jul 2019, Atish Patra wrote:
> From: Anup Patel
>
> This patch adds riscv_isa integer to represent ISA features common
> across all CPUs. The riscv_isa is not same as elf_hwcap because
> elf_hwcap will only
Hi Logan,
Logan Gunthorpe 於 2019年1月10日 週四 上午5:07寫道：
>
> This patch implements sparsemem support for risc-v which helps pave the
> way for memory hotplug and eventually P2P support.
>
> We introduce Kconfig options for virtual and physical address bits which
> are used to calculate the size of
PPC32 also have flush_dcache_range() so it can also support
ARCH_HAS_PMEM_API and ARCH_HAS_UACCESS_FLUSHCACHE without changes.
Signed-off-by: Christophe Leroy
---
v2: moved pmem.o from obj64-y to obj-y
arch/powerpc/Kconfig | 4 ++--
arch/powerpc/lib/Makefile | 4 ++--
2 files changed, 4
Daniel Axtens writes:
> Hi Mark,
>
> Thanks for your email - I'm very new to mm stuff and the feedback is
> very helpful.
>
>>> +#ifndef CONFIG_KASAN_VMALLOC
>>> int kasan_module_alloc(void *addr, size_t size)
>>> {
>>> void *ret;
>>> @@ -603,6 +604,7 @@ void kasan_free_shadow(const struct
Hi all,
Changes since 20190730:
New tree: fpga-fixes
My fixes tree contains:
15b9fc624ba4 ("drivers/macintosh/smu.c: Mark expected switch fall-through")
The fsverity tree gained a conflict against the f2fs tree.
The pm tree gained a build failure for which I applied a patch.
The
* Song Liu [2019-07-30 12:30:59]:
> Currently, uprobe swaps the target page with a anonymous page in both
> install_breakpoint() and remove_breakpoint(). When all uprobes on a page
> are removed, the given mm is still using an anonymous page (not the
> original page).
>
> This patch allows
G'day Stephen,
A comment unrelated to your change.
On 31/07/2019 02:15, Stephen Boyd wrote:
diff --git a/drivers/iio/adc/at91_adc.c b/drivers/iio/adc/at91_adc.c
index 32f1c4a33b20..abe99856c823 100644
--- a/drivers/iio/adc/at91_adc.c
+++ b/drivers/iio/adc/at91_adc.c
@@ -1179,10 +1179,8
On Tue, 2019-07-30 at 17:46 -0300, Fabio Estevam wrote:
> On Tue, Jul 30, 2019 at 11:57 AM Philippe Schenker wrote:
>
> > + /* Atmel maxtouch controller */
> > + atmel_mxt_ts: atmel_mxt_ts@4a {
>
> Generic node names, please:
>
> touchscreen@4a
>
> > + compatible =
On 7/30/19, 9:52 PM, "Paul Walmsley" wrote:
On Tue, 30 Jul 2019, Atish Patra wrote:
> The yaml documentation description of isa strings section doesn't
> specify anything about the case sensitiveness of the isa strings.
> The RISC-V specification clearly specifies it to
On 2019/7/29 14:51, Gao Xiang wrote:
> Keep in line with erofs-outofstaging patchset as well, see
> https://lore.kernel.org/linux-fsdevel/20190725095658.155779-1-gaoxian...@huawei.com/
>
> Signed-off-by: Gao Xiang
Reviewed-by: Chao Yu
Thanks,
Add missing includes and exports.
Signed-off-by: John Ogness
---
In case anyone wants to build/run my test module, this patch needs to
be applied. For my arm64 tests I need to build the module slightly
different, which is why I didn't catch this. Sorry.
Tested on 5.3-rc2.
Hi Olof
On 7/30/19 7:36 PM, Olof Johansson wrote:
Hi Patrice,
If you cc s...@kernel.org on patches you want us to apply, you'll get
them automatically tracked by patchwork.
Does it means that you will take it directly in arm-soc tree ?
I mean, I used to take this kind of patch
On Wed, Jul 31, 2019 at 4:01 AM Jan Sebastian Götte wrote:
>
> On 7/31/19 1:49 AM, Emil Velikov wrote:
> > On 2019/07/31, Jan Sebastian Götte wrote:
> >> Hi Emil,
> >>
> >> thank you for your comments.
> >>
> >> On 7/30/19 11:08 PM, Emil Velikov wrote:
> >>> On 2019/07/30, Jan Sebastian Götte
On Tue, Jul 30, 2019 at 07:06:01PM +0200, Maxime Ripard wrote:
> On Tue, Jul 30, 2019 at 10:09:00AM +0200, Uwe Kleine-König wrote:
> > Hello Rob and Frank,
> >
> > Maxime and Jernej on one side and me on the other cannot agree about a
> > detail in the change to the bindings here. I'm trying to
On 31. 07. 19 8:43, Philippe Schenker wrote:
On Tue, 2019-07-30 at 17:46 -0300, Fabio Estevam wrote:
On Tue, Jul 30, 2019 at 11:57 AM Philippe Schenker wrote:
+ /* Atmel maxtouch controller */
+ atmel_mxt_ts: atmel_mxt_ts@4a {
Generic node names, please:
touchscreen@4a
+
On 31/07/19 03:55, Atish Patra wrote:
> On Tue, 2019-07-30 at 13:26 +0200, Paolo Bonzini wrote:
>> On 29/07/19 13:57, Anup Patel wrote:
>>> + if (delta_ns > VCPU_TIMER_PROGRAM_THRESHOLD_NS) {
>>> + hrtimer_start(>hrt, ktime_add_ns(ktime_get(),
>>> delta_ns),
>>
>> I think the guest
On Tue, Jul 30, 2019 at 11:15:36AM -0700, Stephen Boyd wrote:
> We don't need dev_err() messages when platform_get_irq() fails now that
> platform_get_irq() prints an error message itself when something goes
> wrong. Let's remove these prints with a simple semantic patch.
Looking at v5.3-rc2 it's
On (07/31/19 15:08), Sergey Senozhatsky wrote:
> When you have a chance, mind to take a look at the patch below?
> Doesn't look very difficult (half of it are white-spaces and
> comments, I believe).
I'm very sorry for annoyance.
Updated version:
-- passes !PRINTK build
-- moved
Rob,
On 30/07/2019 12.34, Peter Ujfalusi wrote:
> Changes since v1
> (https://patchwork.kernel.org/project/linux-dmaengine/list/?series=114105=*)
> - Added support for j721e
> - Based on 5.3-rc2
> - dropped ti_sci API patch for RM management as it is already upstream
> - dropped
On 30. 07. 19 16:46, Philippe Schenker wrote:
From: Philippe Schenker
This patch adds some missing pinmuxing that is in the colibri
standard to the dts.
Signed-off-by: Philippe Schenker
---
"ARM: dts: imx6-colibri: " in the subject for consistency.
Same for the Apalis, please.
Michal
Hi all,
In commit
fa04d8c1c150 ("tty: serial: fsl_lpuart: Use appropriate lpuart32_* I/O funcs")
Fixes tag
Fixes: a5fa2660d787 ("tty/serial/fsl_lpuart: Add CONSOLE_POLL support
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no
On Wed, Jul 31, 2019 at 08:58:53AM +0200, Uwe Kleine-König wrote:
> On Tue, Jul 30, 2019 at 11:15:36AM -0700, Stephen Boyd wrote:
> > We don't need dev_err() messages when platform_get_irq() fails now that
> > platform_get_irq() prints an error message itself when something goes
> > wrong. Let's
On 30. 07. 19 16:46, Philippe Schenker wrote:
From: Philippe Schenker
This patch prepares the devicetree for the new Ixora V1.2 where we are
able to turn off the supply of the can transceiver. This implies to use
a sleep state on transmission pins in order to prevent backfeeding.
Like in H3, A64 SID controller doesn't return correct data
when using direct access. It appears that on A64, SID needs
8 bytes of word_size.
Workaround is to enable read by registers.
Signed-off-by: Stefan Mavrodiev
---
drivers/nvmem/sunxi_sid.c | 1 +
1 file changed, 1 insertion(+)
diff
A64 SID controller has some issues when readind data, To exampine the
problem I've done the following steps.
When reading the whole nvmem memory in one chunk the returned bytes
are valid:
dd if=/sys/bus/nvmem/devices/sunxi-sid0/nvmem 2>/dev/null | hexdump -C
ba 00 c0 92 20 46 10 84
Hook into vmalloc and vmap, and dynamically allocate real shadow
memory to back the mappings.
Most mappings in vmalloc space are small, requiring less than a full
page of shadow space. Allocating a full shadow page per mapping would
therefore be wasteful. Furthermore, to ensure that different
Supporting VMAP_STACK with KASAN_VMALLOC is straightforward:
- clear the shadow region of vmapped stacks when swapping them in
- tweak Kconfig to allow VMAP_STACK to be turned on with KASAN
Reviewed-by: Dmitry Vyukov
Signed-off-by: Daniel Axtens
---
arch/Kconfig | 9 +
In the case where KASAN directly allocates memory to back vmalloc
space, don't map the early shadow page over it.
We prepopulate pgds/p4ds for the range that would otherwise be empty.
This is required to get it synced to hardware on boot, allowing the
lower levels of the page tables to be filled
Hi OLof
On 7/30/19 7:36 PM, Olof Johansson wrote:
> Hi Patrice,
>
> If you cc s...@kernel.org on patches you want us to apply, you'll get
> them automatically tracked by patchwork.
Thanks for the information, i will resubmit it.
Patrice
>
>
> -Olof
>
> On Mon, Jul 29, 2019 at 3:55 PM wrote:
Currently, vmalloc space is backed by the early shadow page. This
means that kasan is incompatible with VMAP_STACK, and it also provides
a hurdle for architectures that do not have a dedicated module space
(like powerpc64).
This series provides a mechanism to back vmalloc space with real,
On 30.07.19 21:06, Paolo Bonzini wrote:
> On 30/07/19 16:57, Christian Borntraeger wrote:
>> While this fixes the test (and the migration does work fine), it still
>> means that s390x overindicates the dirty bit for sparsely populated
>> 1M segments. It is just a performance issue, but maybe we
On Wed, Jul 31, 2019 at 12:28 PM Paolo Bonzini wrote:
>
> On 31/07/19 03:55, Atish Patra wrote:
> > On Tue, 2019-07-30 at 13:26 +0200, Paolo Bonzini wrote:
> >> On 29/07/19 13:57, Anup Patel wrote:
> >>> + if (delta_ns > VCPU_TIMER_PROGRAM_THRESHOLD_NS) {
> >>> + hrtimer_start(>hrt,
From: Florian Eckert
On APUx we have also mpcie2/mpcie3 reset pins. To make it possible to reset
the ports from the userspace, add the definition to this platform
device. The gpio can then be exported by the legancy gpio subsystem to
toggle the mpcie reset pin.
Signed-off-by: Florian Eckert
On Wed, Jul 31, 2019 at 05:12:21PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> fa04d8c1c150 ("tty: serial: fsl_lpuart: Use appropriate lpuart32_* I/O
> funcs")
>
> Fixes tag
>
> Fixes: a5fa2660d787 ("tty/serial/fsl_lpuart: Add CONSOLE_POLL support
>
> has these problem(s):
On Wed 31-07-19 14:44:47, Minchan Kim wrote:
> On Tue, Jul 30, 2019 at 02:57:51PM +0200, Michal Hocko wrote:
> > [Cc Nick - the email thread starts
> > http://lkml.kernel.org/r/20190729071037.241581-1-minc...@kernel.org
> > A very brief summary is that mark_page_accessed seems to be quite
> >
From: Patrice Chotard
Enable support for QSPI block on STM32 SoCs.
Signed-off-by: Patrice Chotard
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index
Le 30/07/2019 à 23:10, Chris Packham a écrit :
Hi Christophe,
On Tue, 2019-07-30 at 09:02 +0200, Christophe Leroy wrote:
Le 24/07/2019 à 07:33, Chris Packham a écrit :
Device tree aware platforms can make use of CMDLINE_EXTEND to
extend the
kernel command line provided by the bootloader.
On Tue, Jul 30, 2019 at 4:50 PM Paolo Bonzini wrote:
>
> On 29/07/19 13:57, Anup Patel wrote:
> > +static ulong get_insn(struct kvm_vcpu *vcpu)
> > +{
> > + ulong __sepc = vcpu->arch.guest_context.sepc;
> > + ulong __hstatus, __sstatus, __vsstatus;
> > +#ifdef CONFIG_RISCV_ISA_C
> > +
wt., 30 lip 2019 o 20:16 Stephen Boyd napisał(a):
>
> We don't need dev_err() messages when platform_get_irq() fails now that
> platform_get_irq() prints an error message itself when something goes
> wrong. Let's remove these prints with a simple semantic patch.
>
> //
> @@
> expression ret;
>
On Sun, Jul 28, 2019 at 4:28 PM Morten Borup Petersen wrote:
>
>
>
> On 7/25/19 7:49 AM, Jassi Brar wrote:
> > On Sun, Jul 21, 2019 at 4:58 PM Jassi Brar wrote:
> >>
> >> On Wed, Jul 17, 2019 at 2:26 PM Tushar Khandelwal
> >> wrote:
> >>
> >>> diff --git
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/infiniband/hw/hns/hns_roce_hw_v2.c: In function
hns_roce_v2_cleanup_eq_table:
drivers/infiniband/hw/hns/hns_roce_hw_v2.c:5920:6:
warning: variable irq_num set but not used [-Wunused-but-set-variable]
It is not used since
commit
There is no good reason to use GFP_ATOMIC here. Other memory allocations
are performed with GFP_KERNEL (see other 'dma_alloc_coherent()' below and
'kzalloc()' in 'et131x_rx_dma_memory_alloc()')
Use GFP_KERNEL which should be enough.
Signed-off-by: Christophe JAILLET
---
On 30/07/2019 18:14, Sean Paul wrote:
> On Tue, Jul 30, 2019 at 03:38:23PM +0200, Neil Armstrong wrote:
>> Hi,
>>
>> On 25/07/2019 19:49, Sean Paul wrote:
>>> On Mon, Jul 22, 2019 at 02:02:07PM -0700, Matthias Kaehlcke wrote:
On Mon, Jul 22, 2019 at 04:24:26PM -0400, Sean Paul wrote:
> On
On Wed, Jul 31, 2019 at 09:13:01AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 31, 2019 at 08:58:53AM +0200, Uwe Kleine-König wrote:
> > On Tue, Jul 30, 2019 at 11:15:36AM -0700, Stephen Boyd wrote:
> > > We don't need dev_err() messages when platform_get_irq() fails now that
> > >
From: fengchunguo
88200 and 96000 sampling rate was not enabled on driver, so can't be played.
The error information:
max98373 3-0031：rate 96000 not supported
max98373 3-0031：ASoC: can't set max98373-aif1 hw params: -22
Signed-off-by: fengchunguo
---
sound/soc/codecs/max98373.c | 6 ++
On 2019/7/29 14:51, Gao Xiang wrote:
> - rename erofs_register_super / erofs_unregister_super
> to erofs_shrinker_register / erofs_shrinker_unregister;
> - fold the only erofs_shrink_workstation external call
> to erofs_shrinker_unregister;
> - localize erofs_shrink_workstation;
> - localize
The Mihawk BMC is an ASPEED ast2500 based BMC that is part of an
OpenPower Power9 server.
Signed-off-by: Ben Pai
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/aspeed-bmc-opp-mihawk.dts | 907
2 files changed, 908 insertions(+)
create mode
From: Colin Ian King
There is a spelling mistake in a warning message, fix it.
Signed-off-by: Colin Ian King
---
drivers/infiniband/core/netlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/core/netlink.c
b/drivers/infiniband/core/netlink.c
index
Le 31/07/2019 à 08:01, Christophe Leroy a écrit :
Due to commit 4a6d8cf90017 ("powerpc/mm: don't use pte_alloc_kernel()
until slab is available on PPC32"), pte_alloc_kernel() cannot be used
during early KASAN init.
Fix it by using memblock_alloc() instead.
Reported-by: Erhard F.
Fixes:
On Wed 31-07-19 09:24:21, Mike Rapoport wrote:
> [ sorry for a late reply too, somehow I missed this thread before ]
>
> On Tue, Jul 30, 2019 at 10:14:15AM +0200, Michal Hocko wrote:
> > [Sorry for a late reply]
> >
> > On Mon 15-07-19 17:55:07, Hoan Tran OS wrote:
> > > Hi,
> > >
> > > On
On Tue, Jul 30, 2019 at 05:28:11PM +0100, Thomas Preston wrote:
> On 30/07/2019 16:50, Mark Brown wrote:
> > On Tue, Jul 30, 2019 at 04:25:56PM +0100, Thomas Preston wrote:
> >> On 30/07/2019 15:19, Mark Brown wrote:
> >
> >>> It is unclear what this mutex usefully protects, it only gets taken
Christophe JAILLET (2):
net: ag71xx: Slighly simplify code in 'ag71xx_rings_init()'
net: ag71xx: Use GFP_KERNEL instead of GFP_ATOMIC in
'ag71xx_rings_init()'
drivers/net/ethernet/atheros/ag71xx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.20.1
A few lines above, we have:
tx_size = BIT(tx->order);
So use 'tx_size' directly to be consistent with the way 'rx->descs_cpu' and
'rx->descs_dma' are computed below.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/atheros/ag71xx.c | 2 +-
1 file changed, 1 insertion(+), 1
There is no need to use GFP_ATOMIC here, GFP_KERNEL should be enough.
The 'kcalloc()' just a few lines above, already uses GFP_KERNEL.
Signed-off-by: Christophe JAILLET
---
I've done my best to check if a spinlock can be hold when reaching this
code. Apparently it is never the case.
But double
Thanks for the review Amit!
On 30-07-19, 22:05, Amit Kucheria wrote:
> On Thu, Jul 25, 2019 at 7:23 PM Vinod Koul wrote:
> >
> > The adc nodes have reg property but were missing the unit name, so add
> > that to fix these warnings:
> >
> > arch/arm64/boot/dts/qcom/pms405.dtsi:91.12-94.6:
On Tue 30-07-19 11:05:44, Andrew Morton wrote:
> On Tue, 30 Jul 2019 15:11:27 +0200 Michal Hocko wrote:
>
> > On Thu 23-05-19 17:57:37, Andrew Morton wrote:
> > [...]
> > > It does appear to me that this patch does more good than harm for the
> > > totality of kernel users, so I'm inclined to
On 30/07/2019 12.57, Andrew Jones wrote:
> On Tue, Jul 30, 2019 at 12:01:12PM +0200, Thomas Huth wrote:
>> To run the dirty_log_test on s390x, we have to make sure that we
>> access the dirty log bitmap with little endian byte ordering and
>> we have to properly align the memslot of the guest.
>>
Add an 'order' argument to __page_cache_alloc() and
do_read_cache_page(). Ensure the allocated pages are compound pages.
Signed-off-by: Matthew Wilcox (Oracle)
Signed-off-by: William Kucharski
Reported-by: kbuild test robot
---
fs/afs/dir.c| 2 +-
fs/btrfs/compression.c | 2 +-
This set of patches is the first step towards a mechanism for automatically
mapping read-only text areas of appropriate size and alignment to THPs
whenever possible.
For now, the central routine, filemap_huge_fault(), amd various support
routines are only included if the experimental kernel
Add filemap_huge_fault() to attempt to satisfy page
faults on memory-mapped read-only text pages using THP when possible.
Signed-off-by: William Kucharski
---
include/linux/huge_mm.h | 16 ++-
include/linux/mm.h | 6 +
mm/Kconfig | 15 ++
mm/filemap.c| 300
As it is done for all the other structs within this driver.
Signed-off-by: Hubert Feurstein
---
drivers/net/dsa/mv88e6xxx/ptp.c | 32
drivers/net/dsa/mv88e6xxx/ptp.h | 4 ++--
2 files changed, 18 insertions(+), 18 deletions(-)
diff --git
This adds PTP support for the MV88E6250 family.
Signed-off-by: Hubert Feurstein
---
drivers/net/dsa/mv88e6xxx/chip.c | 4 ++
drivers/net/dsa/mv88e6xxx/chip.h | 4 ++
drivers/net/dsa/mv88e6xxx/ptp.c | 79 +++-
drivers/net/dsa/mv88e6xxx/ptp.h | 2 +
4 files
The MV88E6250 family doesn't support the MV88E6XXX_PORT_CTL1_MESSAGE_PORT
bit.
Signed-off-by: Hubert Feurstein
Reviewed-by: Andrew Lunn
---
drivers/net/dsa/mv88e6xxx/chip.c | 34 +---
drivers/net/dsa/mv88e6xxx/chip.h | 1 +
2 files changed, 32 insertions(+), 3
With this it is possible to mark certain chip ports as invalid. This is
required for example for the MV88E6220 (which is in general a MV88E6250
with 7 ports) but the ports 2-4 are not routed to pins.
If a user configures an invalid port, an error is returned.
Signed-off-by: Hubert Feurstein
---
The MV88E6220 is almost the same as MV88E6250 except that the ports 2-4 are
not routed to pins. So the usable ports are 0, 1, 5 and 6.
Signed-off-by: Hubert Feurstein
---
drivers/net/dsa/mv88e6xxx/chip.c | 25 +
drivers/net/dsa/mv88e6xxx/chip.h | 3 ++-
This patch series adds support for the MV88E6220 chip to the mv88e6xxx driver.
The MV88E6220 is almost the same as MV88E6250 except that the ports 2-4 are
not routed to pins.
Furthermore, PTP support is added to the MV88E6250 family.
v2:
- insert all 6220 entries in correct numerical order
-
The MV88E6220 is part of the MV88E6250 family.
Signed-off-by: Hubert Feurstein
Reviewed-by: Andrew Lunn
---
Documentation/devicetree/bindings/net/dsa/marvell.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/dsa/marvell.txt
Hello,
syzbot found the following crash on:
HEAD commit:fde50b96 Add linux-next specific files for 20190726
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15ea7f3fa0
kernel config: https://syzkaller.appspot.com/x/.config?x=4b58274564b354c1
On Wed, Jul 31, 2019 at 09:01:44AM +0100, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a warning message, fix it.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/infiniband/core/netlink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Thanks,
Hello,
syzbot found the following crash on:
HEAD commit:fde50b96 Add linux-next specific files for 20190726
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1431fb9460
kernel config: https://syzkaller.appspot.com/x/.config?x=4b58274564b354c1
On 09. 07. 19 19:28, Nishka Dasgupta wrote:
> Each iteration of for_each_available_child_of_node puts the previous
> node, but in the case of a goto from the middle of the loop, there is
> no put, thus causing a memory leak. Hence add an of_node_put before the
> goto.
> Issue found with
On Wed, Jul 31, 2019 at 1:41 AM Stephen Boyd wrote:
>
> Quoting Rafael J. Wysocki (2019-07-30 16:05:55)
> > On Wed, Jul 31, 2019 at 12:26 AM Stephen Boyd wrote:
> > >
> > > Quoting Rafael J. Wysocki (2019-07-30 15:17:55)
> > > > On Tuesday, July 30, 2019 8:48:09 PM CEST Stephen Boyd wrote:
> > >
> On Jul 31, 2019, at 1:25 AM, William Kucharski
> wrote:
>
> This set of patches is the first step towards a mechanism for automatically
> mapping read-only text areas of appropriate size and alignment to THPs
> whenever possible.
>
> For now, the central routine, filemap_huge_fault(), amd
On Mon, 29 Jul 2019 23:52:14 +0200
Jacopo Mondi wrote:
> Hello,
> so I finally run some test and...
>
> On Sun, Jul 14, 2019 at 05:19:32AM -0700, Joe Perches wrote:
> > On Sun, 2019-07-14 at 12:54 +0100, Jonathan Cameron wrote:
> > > On Tue, 9 Jul 2019 22:04:17 -0700
> > > Joe Perches
Refer to tmpfs use inode number and generation number to construct the
filehandle for nfs-export
Without this patch, when run exportfs for nfs-kernel-server to export
ramfs, it will report "not support NFS export"
Signed-off-by: Haodong Wong
---
fs/ramfs/inode.c | 72
Configure CDNS_UFS_REG_HCLKDIV in .hce_enable_notify()
because if UFSHCD resets the controller ip because of
phy or device related errors then CDNS_UFS_REG_HCLKDIV
is reset to default value and .setup_clock() is not
called later in the sequence whereas hce_enable_notify
will be called everytime
The G12A/G12B Socs embeds a specific clock tree for each CPU cluster :
cpu_clk / cpub_clk
| \- cpu_clk_dyn
| | \- cpu_clk_premux0
| ||- cpu_clk_postmux0
| |||- cpu_clk_dyn0_div
| ||\- xtal/fclk_div2/fclk_div3
| |\-
Add a clock driver for the cpu dynamic divider, this divider needs
to have a flag set before setting the divider value then removed
while writing the new value to the register.
This drivers implements this behavior and will be used essentially
on the Amlogic G12A and G12B SoCs for cpu clock
In order to implement clock switching for the CLKID_CPU_CLK and
CLKID_CPUB_CLK, notifiers are added on specific points of the
clock tree :
cpu_clk / cpub_clk
| \- cpu_clk_dyn
| | \- cpu_clk_premux0
| ||- cpu_clk_postmux0
| |||- cpu_clk_dyn0_div
| |
Introduce the clk_hw_set_parent() provider call to change parent of
a clock by using the clk_hw pointers.
This eases the clock reparenting from clock rate notifiers and
implementing DVFS with simpler code avoiding the boilerplates
functions as __clk_lookup(clk_hw_get_name()) then
The default-on property - or the def_value via legacy pdata) should be
handled as:
if it is 1, the backlight must be enabled (kept enabled)
if it is 0, the backlight must be disabled (kept disabled)
This only works for the case when default-on is set. If it is not set then
the brightness of the
1 - 100 of 1297 matches
Mail list logo
