Add process for the situation that more than one irq is coming to
a single chip at the same time. The original code will only respond
to the lowest setted bit in JZ_REG_INTC_PENDING, and then exit the
interrupt dispatch function. After exiting the interrupt dispatch
function, since the second
From: Paul Cercueil
By creating the generic chips from the IRQ domain, we don't rely on the
JZ4740_IRQ_BASE macro. It also makes the code a bit cleaner.
Signed-off-by: Paul Cercueil
Signed-off-by: Zhou Yanjie
---
drivers/irqchip/irq-ingenic.c | 30 +-
1 file
From: Paul Cercueil
Get the virq number from the IRQ domain instead of calculating it from
the hardcoded irq base.
Signed-off-by: Paul Cercueil
Signed-off-by: Zhou Yanjie
---
drivers/irqchip/irq-ingenic.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
From: Paul Cercueil
If we cannot create the IRQ domain, the driver should fail to probe
instead of succeeding with just a warning message.
Signed-off-by: Paul Cercueil
Signed-off-by: Zhou Yanjie
---
drivers/irqchip/irq-ingenic.c | 15 ++-
1 file changed, 10 insertions(+), 5
From: Paul Cercueil
The same behaviour can be obtained by using the IRQCHIP_MASK_ON_SUSPEND
flag on the IRQ chip.
Signed-off-by: Paul Cercueil
Signed-off-by: Zhou Yanjie
---
drivers/irqchip/irq-ingenic.c | 24 +---
include/linux/irqchip/ingenic.h | 14 --
2
v5->v6: add my Signed-off-by for patches from Paul Cercueil.
Patch entirely from Davidlohr:
pipelined_send() and pipelined_receive() are identical, so merge them.
Signed-off-by: Manfred Spraul
Cc: Davidlohr Bueso
---
ipc/mqueue.c | 31 ++-
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/ipc/mqueue.c
Transfer findings from ipc/mqueue.c:
- A control barrier was missing for the lockless receive case
So in theory, not yet initialized data may have been copied
to user space - obviously only for architectures where
control barriers are not NOP.
- use smp_store_release(). In theory, the
The patch documents and updates the memory barriers in ipc/sem.c:
- Add smp_store_release() to wake_up_sem_queue_prepare() and
document why it is needed.
- Read q->status using READ_ONCE+smp_acquire__after_ctrl_dep().
as the pair for the barrier inside wake_up_sem_queue_prepare().
- Add
The documentation in memory-barriers.txt claims that
smp_mb__{before,after}_atomic() are for atomic ops that do not return a
value.
This is misleading and doesn't match the example in atomic_t.txt,
and e.g. smp_mb__before_atomic() may and is used together with
cmpxchg_relaxed() in the wake_q
Update and document memory barriers for mqueue.c:
- ewp->state is read without any locks, thus READ_ONCE is required.
- add smp_aquire__after_ctrl_dep() after the READ_ONCE, we need
acquire semantics if the value is STATE_READY.
- add an explicit memory barrier to __pipelined_op(), the
1) wake_q_add() contains a memory barrier, and callers such as
ipc/mqueue.c rely on this barrier.
Unfortunately, this is documented in ipc/mqueue.c, and not in the
description of wake_q_add().
Therefore: Update the documentation.
Removing/updating ipc/mqueue.c will happen with the next patch in
Hi,
Updated series, based on input from Davidlohr:
- Mixing WRITE_ONCE(), when not holding a lock, and "normal" writes,
when holding a lock, makes the code less readable.
Thus use _ONCE() everywhere, for both WRITE_ONCE() and READ_ONCE().
- According to my understanding, wake_q_add() does
On Thu, Oct 10, 2019 at 02:30:46PM +0200, Geert Uytterhoeven wrote:
> At the end of the v5.3 upstream kernel development cycle, Simon stepped
> down from his role as Renesas SoC maintainer.
>
> Remove his maintainership, git repository, and branch from the
> MAINTAINERS file, and add an entry to
On Fri, 11 Oct 2019, Gabriela Bittencourt wrote:
> Cleans up checks of "Alignment should match open parenthesis" in tree sm750fb
>
> Signed-off-by: Gabriela Bittencourt
> ---
> drivers/staging/sm750fb/ddk750_display.c | 2 +-
> drivers/staging/sm750fb/sm750_accel.c| 2 +-
>
add support for low power mode of Ingenic's MMC/SD Controller.
Signed-off-by: Zhou Yanjie
---
drivers/mmc/host/jz4740_mmc.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/mmc/host/jz4740_mmc.c b/drivers/mmc/host/jz4740_mmc.c
index 44a04fe..4cbe7fb 100644
Add support for probing mmc driver on the X1000 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
---
drivers/mmc/host/jz4740_mmc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/jz4740_mmc.c b/drivers/mmc/host/jz4740_mmc.c
index f4c4890..44a04fe 100644
---
Add support for probing mmc driver on the JZ4760 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
---
drivers/mmc/host/jz4740_mmc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mmc/host/jz4740_mmc.c b/drivers/mmc/host/jz4740_mmc.c
index 69c4a8b..f4c4890 100644
---
Add the MMC bindings for the X1000 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
---
Documentation/devicetree/bindings/mmc/jz4740.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/mmc/jz4740.txt
Add the MMC bindings for the JZ4760 Soc from Ingenic.
Signed-off-by: Zhou Yanjie
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/mmc/jz4740.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mmc/jz4740.txt
Add support for 8bit mode, now supports 1bit/4bit/8bit modes.
Signed-off-by: Zhou Yanjie
---
drivers/mmc/host/jz4740_mmc.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/jz4740_mmc.c b/drivers/mmc/host/jz4740_mmc.c
index ffdbfaa..69c4a8b
v1->v2: drop macro definition rename, split patch, add support for x1000.
On Fri, Oct 11, 2019 at 06:08:24PM +0100, Ben Dooks wrote:
> The rcu_state, rcu_rnp_online_cpus and rcu_dynticks_curr_cpu_in_eqs
> do not have declarations in a header. Add these to remove the
> following sparse warnings:
>
> kernel/rcu/tree.c:87:18: warning: symbol 'rcu_state' was not declared.
On Sat, Oct 12, 2019 at 12:43 AM Matthias Maennich wrote:
>
> On Fri, Oct 11, 2019 at 05:31:27PM +0200, Greg Kroah-Hartman wrote:
> >On Thu, Oct 10, 2019 at 04:14:43PM +0100, Matthias Maennich wrote:
> >> Now that the namespace value is not part of the __ksymtab entry name
> >> anymore, we can
From: David Howells
Date: Thu, 10 Oct 2019 15:52:34 +0100
> If an ICMP packet comes in on the UDP socket backing an AF_RXRPC socket as
> the UDP socket is being shut down, rxrpc_error_report() may get called to
> deal with it after sk_user_data on the UDP socket has been cleared, leading
> to a
Enable the drivers for GENI SPI and QSPI controllers found on the
Qualcomm SDM845 platform, among others.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index
Add a IIO driver for the Bosch BMA400 3-axes ultra-low power accelerometer.
The driver supports reading from the acceleration and temperature
registers. The driver also supports reading and configuring the output data
rate, oversampling ratio, and scale.
Signed-off-by: Dan Robertson
---
This patchset adds a IIO driver for the Bosch BMA400 3-axes ultra low-power
accelerometer. The initial implementation of the driver adds read support for
the acceleration and temperature data registers. The driver also has support
for reading and writing to the output data rate, oversampling
Add devicetree binding for the Bosch BMA400 3-axes ultra-low power
accelerometer sensor.
Signed-off-by: Dan Robertson
---
.../devicetree/bindings/iio/accel/bma400.txt | 16
1 file changed, 16 insertions(+)
create mode 100644
re Board (RK3399)
- Radxa Rock Pi 4 (RK3399)
- Pine64 RockPro64 (RK3399)
All of the above seem to use the RK808 regulator for sd io voltage.
The ROC-RK3328-CC did not have this issue and seem to automatically
reset to 3.3v.
[1]
https://github.com/Kwiboo/linux-rockchip/compare/next-20191011...nex
On Fri, Oct 11, 2019 at 08:10:30AM -0400, Vineeth Remanan Pillai wrote:
> > Thanks for the clarification.
> >
> > Yes, this is the initialization issue I mentioned before when core
> > scheduling is initially enabled. rq1's vruntime is bumped the first time
> > update_core_cfs_rq_min_vruntime() is
From: Vito Caputo
Date: Wed, 9 Oct 2019 21:08:24 -0700
> Remove pointless use of size return variable by directly returning
> sizes.
>
> Signed-off-by: Vito Caputo
Looks good, applied to net-next.
From: Vito Caputo
Date: Wed, 9 Oct 2019 20:43:47 -0700
> Remove pointless return variable dance.
>
> Appears vestigial from when the function did locking as seen in
> unix_find_socket_byinode(), but locking is handled in
> unix_find_socket_byname() for __unix_find_socket_byname().
>
>
From: Andrew Jeffery
Date: Thu, 10 Oct 2019 12:37:53 +1030
> This series slightly extends the devicetree binding and driver for the
> FTGMAC100 to describe an optional RMII RCLK gate in the clocks property.
> Currently it's necessary for the kernel to ungate RCLK on the AST2600 in NCSI
>
We are testing Virtual Machine with KSM on v5.4-rc2 kernel,
and found the zero_page refcount overflow.
The cause of refcount overflow is increased in try_async_pf
(get_user_page) without being decreased in mmu_set_spte()
while handling ept violation.
In kvm_release_pfn_clean(), only unreserved
On Fri, Oct 11, 2019 at 12:16 AM Matthias Maennich wrote:
>
> The introduction Symbol Namespaces changed the naming schema of the
> __ksymtab entries from __kysmtab__symbol to __ksymtab_NAMESPACE.symbol.
>
> That caused some breakages in tools that depend on the name layout in
> either the
The mm-of-the-moment snapshot 2019-10-11-20-23 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Fri, Oct 11, 2019 at 12:16 AM Matthias Maennich wrote:
>
> Setting the symbol namespace of a symbol within sym_add_exported feels
> displaced and lead to issues in the current implementation of symbol
> namespaces. This patch makes updating the namespace an explicit call to
> decouple it from
On Sat, Oct 12, 2019 at 12:33 AM Greg Kroah-Hartman
wrote:
>
> On Thu, Oct 10, 2019 at 04:14:40PM +0100, Matthias Maennich wrote:
> > Let the function 'sym_update_namespace' take care of updating the
> > namespace for a symbol. While this currently only replaces one single
> > location where
On 2019/10/12 1:03, Greg KH wrote:
> On Sat, Oct 12, 2019 at 12:34:07AM +0800, zhong jiang wrote:
>> I hit the following error when compile the kernel.
>>
>> drivers/staging/wfx/main.o: In function `wfx_core_init':
>> /home/z00352263/linux-next/linux-next/drivers/staging/wfx/main.c:488:
>>
If SND_ATMEL_SOC_SSC_PDC=y and SND_ATMEL_SOC_SSC_DMA=m,
below errors can be found:
sound/soc/atmel/atmel_ssc_dai.o: In function
`atmel_ssc_set_audio':
atmel_ssc_dai.c:(.text+0x6fe): undefined reference to
`atmel_pcm_dma_platform_register'
make: *** [vmlinux] Error 1
After commit 18291410557f
On Wed, 9 Oct 2019 23:45:02 +0200 Rikard Falkeborn
wrote:
> GENMASK() and GENMASK_ULL() are supposed to be called with the high bit
> as the first argument and the low bit as the second argument. Mixing
> them will return a mask with zero bits set.
>
> Recent commits show getting this wrong
On Fri, 11 Oct 2019 20:57:51 -0400
Steven Rostedt wrote:
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -1391,9 +1391,6 @@ static int subsystem_open(struct inode *inode, struct
> file *filp)
> struct trace_array *tr;
> int ret;
>
> - if
On Fri, 2019-10-11 at 22:19 -0300, Gabriela Bittencourt wrote:
> Cleans up checks of "Alignment should match open parenthesis" in tree sm750fb
[]
> diff --git a/drivers/staging/sm750fb/sm750_accel.c
> b/drivers/staging/sm750fb/sm750_accel.c
[]
> @@ -289,7 +289,7 @@ static unsigned int
Acked,
I need optimize commit log with:
...
It's tested with strcpy local array overflow in sys_kill and get:
stack-protector: Kernel stack is corrupted in: sys_kill+0x23c/0x23c
TODO:
- Support task switch for different cannary
On Fri, Oct 11, 2019 at 10:59 AM Mao Han wrote:
On 10/11/2019 3:21 PM, Jiri Olsa wrote:
On Fri, Oct 11, 2019 at 10:50:35AM +0800, Jin, Yao wrote:
On 10/10/2019 8:33 PM, Arnaldo Carvalho de Melo wrote:
Em Thu, Oct 10, 2019 at 04:33:57PM +0800, Jin, Yao escreveu:
On 10/10/2019 4:00 PM, Jiri Olsa wrote:
On Thu, Oct 10, 2019 at
On Fri, 11 Oct 2019 at 21:33, Jiaxun Yang wrote:
>
> Hi kernel.org sysadmin team,
>
> It seems like SSL certification of kernel.org is expired today. With HSTS
> enable, we can't reach kernel.org now.
The APAC frontends were still serving the old certificate because the
cert renewal process
Hi kernel.org sysadmin team,
It seems like SSL certification of kernel.org is expired today. With HSTS
enable, we can't reach kernel.org now.
Thanks
--
Jiaxun Yang
Cleans up checks of "Alignment should match open parenthesis" in tree sm750fb
Signed-off-by: Gabriela Bittencourt
---
drivers/staging/sm750fb/ddk750_display.c | 2 +-
drivers/staging/sm750fb/sm750_accel.c| 2 +-
drivers/staging/sm750fb/sm750_accel.h| 8
Hi Daniel:
New version patch-set had been sent out on Oct9.
https://patchwork.kernel.org/cover/11180683/
Best Regards
Richard Zhu
> -Original Message-
> From: Richard Zhu
> Sent: 2019年10月9日 9:48
> To: Daniel Baluta
> Cc: jassisinghb...@gmail.com; Oleksij Rempel ;
> Daniel Baluta ;
Hi, Vladimir
> On Fri, 11 Oct 2019 at 04:11, Anson Huang wrote:
> >
> > Hi, Jakub
> >
> > > On Fri, 11 Oct 2019 00:38:50 +, Anson Huang wrote:
> > > > > Hm. Looks like the commit you need is commit f1da567f1dc1 ("driver
> core:
> > > > > platform: Add platform_get_irq_byname_optional()") and
Because pids->limit can be changed concurrently (but we don't want to
take a lock because it would be needlessly expensive), use the
appropriate memory barriers.
Fixes: commit 49b786ea146f ("cgroup: implement the PIDs subsystem")
Cc: sta...@vger.kernel.org # v4.3+
Signed-off-by: Aleksa Sarai
---
Hi, Fabio
> On Fri, Oct 11, 2019 at 5:39 AM Anson Huang
> wrote:
> >
> > In the latest reference manual Rev.0,06/2019, the SCG1's system
>
> This should be SCS instead of SCG1.
The reference states SCG system clock, SCS stands for system clock source, so I
think
it is actually meaning SCG1's
From: "Steven Rostedt (VMware)"
Running the latest kernel through my "make instances" stress tests, I
triggered the following bug (with KASAN and kmemleak enabled):
mkdir invoked oom-killer:
gfp_mask=0x40cd0(GFP_KERNEL|__GFP_COMP|__GFP_RECLAIMABLE), order=0,
oom_score_adj=0
CPU: 1 PID: 2229
From: "Steven Rostedt (VMware)"
Added various checks on open tracefs calls to see if tracefs is in lockdown
mode, and if so, to return -EPERM.
Note, the event format files (which are basically standard on all machines)
as well as the enabled_functions file (which shows what is currently being
From: "Steven Rostedt (VMware)"
The ftrace set_ftrace_filter and set_ftrace_notrace files are specific for
an instance now. They need to take a reference to the instance otherwise
there could be a race between accessing the files and deleting the instance.
It wasn't until the :mod: caching
From: "Steven Rostedt (VMware)"
If on boot up, lockdown is activated for tracefs, don't even bother creating
the files. This can also prevent instances from being created if lockdown is
in effect.
Link:
http://lkml.kernel.org/r/CAHk-=whC6Ji=fwnjh2+es4b15tnbss4vpvtvbowcy1jjeg_...@mail.gmail.com
From: "Steven Rostedt (VMware)"
As instances may have different tracers available, we need to look at the
trace_array descriptor that shows lists the available tracers for the
instance. But there's a race between opening the file and the admin from
deleting the instance. The trace_array_get()
It appears that using destroy_inode() to clean up the proxy_ops that was
used by the lockdown code to have all open calls to the tracefs directory
was totally broken. It caused the inodes to not be cleaned up as the
destroy_inode() method is expected to clean up the inode, and not just what
it
From: "Steven Rostedt (VMware)"
Currently, most files in the tracefs directory that gets opened needs to
test if tracing_disabled is set. If so, it should return -ENODEV. The
tracing_disabled is called when tracing is found to be broken. Originally it
was done in case the ring buffer was found
From: "Steven Rostedt (VMware)"
Instead of having the trace events system open calls open code the taking of
the trace_array descriptor (with trace_array_get()) and then calling
trace_open_generic(), have it use the tracing_open_generic_tr() that does
the combination of the two. This requires
Jacek
On 10/11/19 3:15 PM, Jacek Anaszewski wrote:
Dan,
On 10/11/19 3:06 PM, Dan Murphy wrote:
Update the DT binding to include the properties to use the
multicolor framework for the devices that use the LP55xx
framework.
Signed-off-by: Dan Murphy
CC: Tony Lindgren
CC: "Benoît Cousson"
Jacek
On 10/11/19 3:36 PM, Jacek Anaszewski wrote:
Dan,
On 10/11/19 3:06 PM, Dan Murphy wrote:
Add multicolor framework support for the lp55xx family.
Signed-off-by: Dan Murphy
---
drivers/leds/Kconfig | 1 +
drivers/leds/leds-lp55xx-common.c | 176
Jacek
On 10/11/19 2:40 PM, Jacek Anaszewski wrote:
Dan,
On 10/11/19 3:06 PM, Dan Murphy wrote:
Hello
Minor changes per review comments.
https://lore.kernel.org/patchwork/project/lkml/list/?series=413385
Rebased the series on top of Pavel's next branch.
Multicolor changes:
Rename
On Fri, Oct 11, 2019 at 8:52 PM Qian Cai wrote:
>
>
> It simply error-prone to reuse the sysctl.conf from the first kernel, as it
> could contains lots of things that will kill kdump kernel.
Makes sense, I agree with you. But still, there's no
formal/right/single way to do kdump, so I don't
__get_user_asm macro leaves result register uninitialized when alignment
check fails. Add 'insn' parameter to __check_align_{1,2,4} and pass an
instruction that initializes result register from __get_user_asm.
Signed-off-by: Max Filippov
---
arch/xtensa/include/asm/uaccess.h | 12 +++-
__get_user_[no]check uses temporary buffer of type long to store result
of __get_user_size and do sign extension on it when necessary. This
doesn't work correctly for 64-bit data. Fix it by moving temporary
buffer/sign extension logic to __get_user_asm.
Don't do assignment of __get_user_bad result
Hello,
this series fixes return value, out-of-bound stack access and value
truncation in xtensa implementation of {get,put}_user() for 64bit
values. It also cleans up naming of assembly parameters in
__{get,put}_user_asm and __check_align_{1,2,4}.
Changes v1->v2:
- initialize result when
Numeric assembly arguments are hard to understand and assembly code that
uses them is hard to modify. Use named arguments in __check_align_*,
__get_user_asm and __put_user_asm. Modify macro parameter names so that
they don't affect argument names.
Signed-off-by: Max Filippov
---
From: Al Viro
First of all, on short copies __copy_{to,from}_user() return the amount
of bytes left uncopied, *not* -EFAULT. get_user() and put_user() are
expected to return -EFAULT on failure.
Another problem is get_user(v32, (__u64 __user *)p); that should
fetch 64bit value and the assign it
On 10/9/2019 14:43, Christoph Hellwig wrote:
>> +++ b/arch/mips/sgi-ip30/ip30-pci.c
>> @@ -0,0 +1,19 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * ip30-pci.c: misc PCI related helper code for IP30 architecture
>> + */
>> +
>> +#include
>> +
>> +dma_addr_t __phys_to_dma(struct device
__get_user_[no]check uses temporary buffer of type long to store result
of __get_user_size and do sign extension on it when necessary. This
doesn't work correctly for 64-bit data. Fix it by moving temporary
buffer/sign extension logic to __get_user_asm.
Don't do assignment of __get_user_bad result
Numeric assembly arguments are hard to understand and assembly code that
uses them is hard to modify. Use named arguments in __check_align_*,
__get_user_asm and __put_user_asm. Modify macro parameter names so that
they don't affect argument names.
Signed-off-by: Max Filippov
---
Hello,
this series fixes return value, out-of-bound stack access and value
truncation in xtensa implementation of {get,put}_user() for 64bit
values. It also cleans up naming of assembly parameters in
__{get,put}_user_asm and __check_align_{1,2,4}.
Al Viro (1):
xtensa: fix {get,put}_user() for
From: Al Viro
First of all, on short copies __copy_{to,from}_user() return the amount
of bytes left uncopied, *not* -EFAULT. get_user() and put_user() are
expected to return -EFAULT on failure.
Another problem is get_user(v32, (__u64 __user *)p); that should
fetch 64bit value and the assign it
On Thu, 10 Oct 2019 17:17:49 +0200 Uladzislau Rezki wrote:
> > > : * The preload is done in non-atomic context, thus it allows us
> > > : * to use more permissive allocation masks to be more stable
> > > under
> > > : * low memory condition and high memory pressure.
>
> On Oct 11, 2019, at 7:42 PM, Guilherme Piccoli wrote:
>
> Thanks for the quick response. Kdump in Ubuntu, for example, rely in
> mounting the root filesystem.
> Even in initrd-only approaches, we could have sysctl.conf being copied
> to initramfs, and hugepages end-up getting set.
It
Most Qualcomm platforms contain a pseudo random number generator
hardware block. Enable the driver for this block.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
The Qualcomm socinfo driver provides SoC information to userspace using
the standard soc interface as well as a number of debugfs entries.
Enable this to allow certain user space tools to acquire this
information, as well as getting developers access to the information in
debugfs that is useful
The Qualcomm CPUfreq HW provides CPU voltage and frequency scaling on
many modern Qualcomm SoCs. Enable the driver for this hardware block to
enable this functionality on the SDM845 platform.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
On Fri, Oct 11, 2019 at 8:36 PM Qian Cai wrote:
>
> Typically, kdump kernel has its own initramfs, and don’t even need to mount a
> rootfs, so I can’t see how sysfs/sysctl is relevant here.
Thanks for the quick response. Kdump in Ubuntu, for example, rely in
mounting the root filesystem.
Even
The compressed cache for swap pages (zswap) currently needs from 1 to 3
extra kernel command line parameters in order to make it work: it has to be
enabled by adding a "zswap.enabled=1" command line parameter and if one
wants a different compressor or pool allocator than the default lzo / zbud
> On Oct 11, 2019, at 6:40 PM, Guilherme G. Piccoli
> wrote:
>
> Kdump kernels won't benefit from hugepages - in fact it's quite opposite,
> it may be the case hugepages on kdump kernel can lead to OOM if kernel
> gets unable to allocate demanded pages due to the fact the preallocated
>
On Fri, Oct 11, 2019 at 3:33 PM Benjamin Tissoires
wrote:
>
> On Fri, Oct 11, 2019 at 9:39 PM Andrey Smirnov
> wrote:
> >
> > On Fri, Oct 11, 2019 at 7:56 AM Benjamin Tissoires
> > wrote:
> > >
> > > On Mon, Oct 7, 2019 at 7:13 AM Andrey Smirnov
> > > wrote:
> > > >
> > > > G920 device only
merge window is over could you please take a look at the
> > series?
>
> I will.
>
> It would help to resend the whole series with a CC to linux-acpi, though.
Rebased to next-20191011 and sent to linux-acpi and others.
Thanks!
--
Dmitry
On Sat, Oct 12, 2019 at 12:48:42AM +0200, Benjamin Tissoires wrote:
> On Fri, Oct 11, 2019 at 11:34 PM Dmitry Torokhov
> wrote:
> >
> > On Fri, Oct 11, 2019 at 01:35:09PM -0700, Dmitry Torokhov wrote:
> > > On Fri, Oct 11, 2019 at 01:33:03PM -0700, Dmitry Torokhov wrote:
> > > > On Fri, Oct 11,
On 2019-10-11 4:19 p.m., Florian Fainelli wrote:
Instead of having a hard failure and stopping the driver's probe
routine, generate a random Ethernet MAC address to keep going.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/broadcom/genet/bcmgenet.c | 15 ++-
1 file
Instead of having a hard failure and stopping the driver's probe
routine, generate a random Ethernet MAC address to keep going.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/broadcom/genet/bcmgenet.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git
Am 11.10.19 um 20:48 schrieb matthias@kernel.org:
> From: Matthias Brugger
>
> Enable Gigabit Ethernet support on the Raspberry Pi 4
> Model B.
I asked some questions about genet to the RPi guys [1] which are
relevant to this patch (missing clocks and interrupt, MAC address
assignment) but i
On 10/11/19 4:09 PM, Stefan Wahren wrote:
> Am 11.10.19 um 20:48 schrieb matthias@kernel.org:
>> From: Matthias Brugger
>>
>> Enable Gigabit Ethernet support on the Raspberry Pi 4
>> Model B.
>
> I asked some questions about genet to the RPi guys [1] which are
> relevant to this patch
We do not need a special flag to know if we are dealing with an array,
as we can get that data from ratio between element length and the data
size, however we do need a flag to know whether the data is stored
directly inside property_entry or separately.
Signed-off-by: Dmitry Torokhov
---
It is possible to store references to software nodes in the same fashion as
other static properties, so that users do not need to define separate
structures:
static const struct software_node gpio_bank_b_node = {
.name = "B",
};
static const struct property_entry simone_key_enter_props[]
Instead of explicitly setting values of integer types when copying
property entries lets just copy entire value union when processing
non-array values.
For value arrays we no longer use union of pointers, but rather a single
void pointer, which allows us to remove property_set_pointer().
In
Now that all users of references have moved to reference properties,
we can remove separate handling of references.
Signed-off-by: Dmitry Torokhov
---
drivers/base/swnode.c| 46 +++-
include/linux/property.h | 14
2 files changed, 17
Now that static device properties allow defining reference properties
together with all other types of properties, instead of managing them
separately, let's adjust the driver.
Signed-off-by: Dmitry Torokhov
---
drivers/platform/x86/intel_cht_int33fe.c | 81
1 file
There is absolutely no reason to have them as we can handle it all nicely in
property_entry_read_int_array().
Signed-off-by: Dmitry Torokhov
---
drivers/base/swnode.c | 85 +++
1 file changed, 14 insertions(+), 71 deletions(-)
diff --git
When copying/duplicating set of properties, move smaller properties that
were stored separately directly inside property entry structures. We can
move:
- up to 8 bytes from U8 arrays
- up to 4 words
- up to 2 double words
- one U64 value
- one or 2 strings.
Signed-off-by: Dmitry Torokhov
---
We can unify string properties initializer macros with integer
initializers.
Signed-off-by: Dmitry Torokhov
---
include/linux/property.h | 64 +---
1 file changed, 27 insertions(+), 37 deletions(-)
diff --git a/include/linux/property.h
Sometimes we want to initialize property entry array from a regular
pointer, when we can't determine length automatically via ARRAY_SIZE.
Let's introduce PROPERTY_ENTRY_ARRAY_XXX_LEN macros that take explicit
"len" argument.
Signed-off-by: Dmitry Torokhov
---
include/linux/property.h | 45
nline when copying property entries; patch #12 implements
PROPERTY_ENTRY_REF() and friends; patch #13 converts the user of
references to the property syntax, and patch #14 removes the remains of
references as entities that are managed separately.
Changes in v5:
- rebased onto next-20191011
Changes in v
1 - 100 of 899 matches
Mail list logo
