Add new --transport parameter to skip some tests or checks
not supported by a specific transport.
Suggested-by: Jorgen Hansen
Signed-off-by: Stefano Garzarella
---
tools/testing/vsock/util.h | 8
tools/testing/vsock/vsock_test.c | 20 +++-
2 files changed, 27
From: Stefan Hajnoczi
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Stefano Garzarella
---
v2:
* Aligned with the current SPDX [Stefano]
---
tools/testing/vsock/control.h | 1 +
tools/testing/vsock/timeout.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/tools/testing/vsock/control.h
From: Stefan Hajnoczi
See code comment for details.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Stefano Garzarella
---
tools/testing/vsock/util.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/tools/testing/vsock/util.c b/tools/testing/vsock/util.c
From: Stefan Hajnoczi
Move useful functions into a separate file in preparation for more
vsock test programs.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Stefano Garzarella
---
v2:
* aligned with the current SPDX [Stefano]
---
tools/testing/vsock/Makefile | 2 +-
From: Stefan Hajnoczi
The vsock_test.c program runs a test suite of AF_VSOCK test cases.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Stefano Garzarella
---
v2:
* Drop unnecessary includes [Stefan]
* Aligned with the current SPDX [Stefano]
* Set MULTICONN_NFDS to 100 [Stefano]
* Change
From: Stefan Hajnoczi
Many test cases will need to connect to the server or accept incoming
connections. This patch extracts these operations into utility
functions that can be reused.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Stefano Garzarella
---
tools/testing/vsock/util.c
The vsock_diag.ko module already has a test suite but the core AF_VSOCK
functionality has no tests. This patch series adds several test cases that
exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept,
half-closed connections, simultaneous connections).
Stefan: Do you think
From: Stefan Hajnoczi
The vsock_diag_test program directly included ../../../include/uapi/
headers from the source tree. Tests are supposed to use the
usr/include/linux/ headers that have been prepared with make
headers_install instead.
Suggested-by: David S. Miller
Signed-off-by: Stefan
Joe Perches 于2019年7月30日周二 上午8:16写道：
>
> On Mon, 2019-07-29 at 23:15 +0800, Chuhong Yuan wrote:
> > strncmp(str, const, len) is error-prone.
> > We had better use newly introduced
> > str_has_prefix() instead of it.
> []
> > diff --git a/kernel/printk/braille.c b/kernel/printk/braille.c
> []
> >
On Wed, Jun 19, 2019 at 08:56:25AM -0600, Raul Rangel wrote:
> Your patch looks good. I tried it out and got over 57k insertion/removal
> iterations. Do you want me to send out your patch, or do you want to do
> it?
>
> Just to recap, the patch you proposed + the AMD SDHCI specific patch fix
>
Allow the full scale current to be configured at init.
Valid rangles are 5mA->29.8mA.
Signed-off-by: Dan Murphy
---
drivers/leds/leds-lm3532.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/leds/leds-lm3532.c b/drivers/leds/leds-lm3532.c
index
Fix the brightness control for I2C mode. Instead of
changing the full scale current register update the ALS target
register for the appropriate banks.
In addition clean up some code errors and random misspellings found
during coding.
Tested on Droid4 as well as LM3532 EVM connected to a
Add a property for each control bank to configure the
full scale current setting for the device.
Signed-off-by: Dan Murphy
---
Documentation/devicetree/bindings/leds/leds-lm3532.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/leds-lm3532.txt
On Wed, Jul 31, 2019 at 02:59:59PM -0300, Fabio Estevam wrote:
> Hi Andrey,
>
> On Wed, Jul 31, 2019 at 2:53 PM Andrey Smirnov
> wrote:
> >
> > Everyone:
> >
> > This series contains fixes/improvements to LPUART dirver I came up
> > with recently as well as fixes picked up from Toradex and NXP
Hi Stephen,
On 7/31/19 2:35 PM, Stephen Boyd wrote:
> A future patch is going to change semantics of clk_register() so that
> clk_hw::init is guaranteed to be NULL after a clk is registered. Avoid
> referencing this member here so that we don't run into NULL pointer
> exceptions.
>
> Cc: Dinh
On Tue, Jul 30, 2019 at 11:15:55AM -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.
>
> //
> @@
>
On Thu, 1 Aug 2019, Peter Zijlstra wrote:
> On Thu, Aug 01, 2019 at 04:32:54PM +0200, Thomas Gleixner wrote:
> > --- a/kernel/time/Kconfig
> > +++ b/kernel/time/Kconfig
> > @@ -52,6 +52,11 @@ config GENERIC_CLOCKEVENTS_MIN_ADJUST
> > config GENERIC_CMOS_UPDATE
> > bool
> >
> > +# Select to
On Thu, 1 Aug 2019, Peter Zijlstra wrote:
> On Thu, Aug 01, 2019 at 04:32:51PM +0200, Thomas Gleixner wrote:
> > +#ifdef CONFIG_HAVE_ARCH_TRACEHOOK
> > +/**
> > + * tracehook_handle_notify_resume - Notify resume handling for virt
> > + *
> > + * Called with interrupts and preemption enabled from
On 25.07.19 18:02, Oscar Salvador wrote:
> It seems that we have some users out there that want to expose all
> hotpluggable memory to userspace, so this implements a toggling mechanism
> for those users who want to disable it.
>
> By default, vmemmap pages mechanism is enabled.
>
>
On 25.07.19 18:02, Oscar Salvador wrote:
> Physical memory hotadd has to allocate a memmap (struct page array) for
> the newly added memory section. Currently, alloc_pages_node() is used
> for those allocations.
>
> This has some disadvantages:
> a) an existing memory is consumed for that
On 07/31, Song Liu wrote:
>
> > On Jul 31, 2019, at 8:18 AM, Oleg Nesterov wrote:
> >
> > Now, I don't understand why do we need pmd_trans_unstable() after
> > split_huge_pmd(huge-zero-pmd), but whatever reason we have, why can't we
> > unify both cases?
> >
> > IOW, could you explain why the
Hi, Tom
Recently, i ran into a problem about SME and used crash tool to check the
vmcore as follow:
crash> kmem -s | grep -i invalid
kmem: dma-kmalloc-512: slab: e192c0001000 invalid freepointer:
e5ffef4e9a040b7e
kmem: dma-kmalloc-512: slab: e192c0001000 invalid freepointer:
On Fri, Jul 26, 2019 at 1:50 PM Enrico Weigelt, metux IT consult
wrote:
>
> On 26.07.19 08:21, Florian Eckert wrote:
> > 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
On Mon, Jul 29, 2019 at 5:39 PM Enrico Weigelt, metux IT consult
wrote:
>
> From: Enrico Weigelt
>
> The APU3+ boards have two SIM sockets, while only one of them
> can be routed to the mpcie slots at a time. Selection is done
> via simswap gpio.
>
> We currently don't have a fitting subsystem
On Thu, Jul 25, 2019 at 10:06 PM Enrico Weigelt, metux IT consult
wrote:
>
> From: Enrico Weigelt
>
> The keycode KEY_RESTART is more appropriate for the front button,
> as most people use it for things like restart or factory reset.
>
Applied, thanks!
> Signed-off-by: Enrico Weigelt
> Fixes:
On Thu, Aug 01, 2019 at 11:59:26PM +1000, Stephen Rothwell wrote:
> Commit
> 66b25f247e90 ("ASoC: amd: use dma_ops of parent device for acp3x dma
> driver")
> is missing a Signed-off-by from its author.
Ugh, yes - misparsed that as being a variant on the same name.
Dropped, please fix and
On Fri, 26 Jul 2019 at 16:23, Jia-Ju Bai wrote:
>
> In dw_mci_runtime_resume(), there is an if statement on line 3420
> to check whether host->slot is NULL:
> if (host->slot && ...)
>
> When host->slot is NULL, it is used on line 3458:
> if (host->slot->mmc->pm_flags & MMC_PM_KEEP_POWER)
Hi Oleksij,
Thanks for review
>
> your patch is in conflicht with Richard's Zhu
> patch "[PATCH v3] mailbox: imx: add support for imx v1 mu".
> Please sync your works.
Sent an email to Richard. Hopefully he can rebase his change on my patches.
>
> Looks like here is one more bug "from the
On Thu, Aug 01, 2019 at 04:32:54PM +0200, Thomas Gleixner wrote:
> --- a/kernel/time/Kconfig
> +++ b/kernel/time/Kconfig
> @@ -52,6 +52,11 @@ config GENERIC_CLOCKEVENTS_MIN_ADJUST
> config GENERIC_CMOS_UPDATE
> bool
>
> +# Select to handle posix CPU timers from task_work
> +# and not from
On Thu, Aug 01, 2019 at 03:30:53PM +0200, Enric Balletbo i Serra wrote:
> Got it. I don't think this is a "kernel" way to do it. Also, I don't see a big
> value on doing this.
Code generation sounds great, but it makes finding and looking at the
source file difficult unless you have a build. It
On 07/31, Song Liu wrote:
>
> +static int khugepaged_add_pte_mapped_thp(struct mm_struct *mm,
> + unsigned long addr)
> +{
> + struct mm_slot *mm_slot;
> + int ret = 0;
> +
> + /* hold mmap_sem for khugepaged_test_exit() */
> +
On Thu, Aug 01, 2019 at 04:32:51PM +0200, Thomas Gleixner wrote:
> +#ifdef CONFIG_HAVE_ARCH_TRACEHOOK
> +/**
> + * tracehook_handle_notify_resume - Notify resume handling for virt
> + *
> + * Called with interrupts and preemption enabled from VMENTER/EXIT.
> + */
> +void
When CONFIG_KASAN_SW_TAGS=n, set_tag() is compiled away. GCC throws a
warning,
mm/kasan/common.c: In function '__kasan_kmalloc':
mm/kasan/common.c:464:5: warning: variable 'tag' set but not used
[-Wunused-but-set-variable]
u8 tag = 0xff;
^~~
Fix it by making __tag_set() a static inline
Hi Richard,
Thanks for the patch. Please always add linux-...@nxp.com mailing
list for imx related patches. I missed it.
Few comments inline.
Please also update in a separate patch attached to this series
the devictree bindings doc Documentation/devicetree/bindings/mailbox/fsl,mu.txt
by adding
On Thu, Aug 01, 2019 at 12:46:42PM +, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> If CONFIG_GPIOLIB is not enabled, mctrl_gpio_init() and
> mctrl_gpio_init_noauto() will currently return an error pointer with
> -ENOSYS. As the mctrl GPIOs are usually optional, drivers need to
>
On 25.07.19 18:02, Oscar Salvador wrote:
> When hot-removing memory, we need to be careful about two things:
>
> 1) Memory range must be memory_block aligned. This is what
>check_hotplug_memory_range() checks for.
>
> 2) If a range was hot-added using MHP_MEMMAP_ON_MEMORY, we need to check
>
On Thu, Aug 01, 2019 at 06:51:03AM -0700, Paul E. McKenney wrote:
> On Thu, Aug 01, 2019 at 01:13:50PM +0200, Peter Zijlstra wrote:
> > A rather embarrasing mistake had us call sched_setscheduler() before
> > initializing the parameters passed to it.
> >
> > Cc: Juri Lelli
> > Cc: "Paul E.
Sean Christopherson writes:
> On Thu, Aug 01, 2019 at 07:14:16AM +0200, Vitaly Kuznetsov wrote:
>> Regardless of the way how we skip instruction, interrupt shadow needs to be
>> cleared.
>>
>> Signed-off-by: Vitaly Kuznetsov
>> Reviewed-by: Jim Mattson
>> ---
>> arch/x86/kvm/svm.c | 4 +++-
The load_balance algorithm contains some heuristics which have becomes
meaningless since the rework of metrics and the introduction of PELT.
Furthermore, it's sometimes difficult to fix wrong scheduling decisions
because everything is based on load whereas some imbalances are not
related to the
runnable load has been introduced to take into account the case
where blocked load biases the load balance decision which was selecting
underutilized group with huge blocked load whereas other groups were
overloaded.
The load is now only used when groups are overloaded. In this case,
it's worth
utilization is used to detect a misfit task but the load is then used to
select the task on the CPU which can lead to select a small task with
high weight instead of the task that triggered the misfit migration.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 28
Rename sum_nr_running to sum_h_nr_running because it effectively tracks
cfs->h_nr_running so we can use sum_nr_running to track rq->nr_running
when needed.
There is no functional changes.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 34 +-
1 file
cfs load_balance only takes care of CFS tasks whereas CPUs can be used by
other scheduling class. Typically, a CFS task preempted by a RT or deadline
task will not get a chance to be pulled on another CPU because the
load_balance doesn't take into account tasks from classes.
Add sum of nr_running
When there is only 1 cpu per group, using the idle cpus to evenly spread
tasks doesn't make sense and nr_running is a better metrics.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 40
1 file changed, 28 insertions(+), 12 deletions(-)
diff
clean up load_balance and remove meaningless calculation and fields before
adding new algorithm.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 105 +---
1 file changed, 1 insertion(+), 104 deletions(-)
diff --git a/kernel/sched/fair.c
Clean up asym packing to follow the default load balance behavior:
- classify the group by creating a group_asym_capacity field.
- calculate the imbalance in calculate_imbalance() instead of bypassing it.
We don't need to test twice same conditions anymore to detect asym packing
and we
Several wrong task placement have been raised with the current load
balance algorithm but their fixes are not always straight forward and
end up with using biased values to force migrations. A cleanup and rework
of the load balance will help to handle such UCs and enable to fine grain
the behavior
in_accel_x_scale, in_accel_y_scale and in_accel_z_scale are always
the same. The scale is still defined to be in "info_mask_separate".
Userspace (iio-sensor-proxy and others) is not used to that and only
looks for "in_accel_scale" for the scaling factor to apply.
Change IIO_CHAN_INFO_SCALE from
Running posix cpu timers in hard interrupt context has a few downsides:
- For PREEMPT_RT it cannot work as the expiry code needs to take sighand
lock, which is a 'sleeping spinlock' in RT
- For fine grained accounting it's just wrong to run this in context of
the timer interrupt because
TIF_NOTITY_RESUME is evaluated on return to user space along with other TIF
flags.
>From the kernels point of view a VMENTER is more or less equivalent to
return to user space which means that at least a subset of TIF flags needs
to be evaluated and handled.
Currently KVM handles only
Running posix cpu timers in hard interrupt context has a few downsides:
- For PREEMPT_RT it cannot work as the expiry code needs to take sighand
lock, which is a 'sleeping spinlock' in RT
- For fine grained accounting it's just wrong to run this in context of
the timer interrupt because
TIF_NOTITY_RESUME is evaluated on return to user space along with other TIF
flags.
>From the kernels point of view a VMENTER is more or less equivalent to
return to user space which means that at least a subset of TIF flags needs
to be evaluated and handled.
Currently KVM handles only
Split run_posix_cpu_timers() into two pieces, the hard interrupt context
part and the actual timer evaluation/expiry part.
The hard interrupt context part contains only the lockless fast path check
and for now calls the expiry part as before.
No functional change. Preparatory change to move the
X86 handles task work in KVM now. Enable the delegation of posix cpu timer
expiry into task work.
Signed-off-by: Thomas Gleixner
---
arch/x86/Kconfig |1 +
1 file changed, 1 insertion(+)
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -213,6 +213,7 @@ config X86
select
Hi Jason,
I have tested these series on a P4080 platform.
Regards,
Diana
On 7/31/2019 12:26 PM, Jason Yan wrote:
> This series implements KASLR for powerpc/fsl_booke/32, as a security
> feature that deters exploit attempts relying on knowledge of the location
> of kernel internals.
>
> Since
Make debug exceptions visible from RCU so that synchronize_rcu()
correctly track the debug exception handler.
This also introduces sanity checks for user-mode exceptions as same
as x86's ist_enter()/ist_exit().
The debug exception can interrupt in idle task. For example, it warns
if we put a
On Thu 01 Aug 03:07 PDT 2019, Rajendra Nayak wrote:
> From: Jitendra Sharma
>
> Add the binding for the TLMM pinctrl block found in the SC7180 platform
>
> Signed-off-by: Jitendra Sharma
> Signed-off-by: Vivek Gautam
> [rnayak: Fix some copy-paste issues, sort and fix functions]
>
Em Thu, Aug 01, 2019 at 04:26:42PM +0200, Jiri Olsa escreveu:
> Michael reported an issue with perf bench numa failing with
> binding to cpu0 with '-0' option.
>
> # perf bench numa mem -p 3 -t 1 -P 512 -s 100 -zZcm0 --thp 1 -M 1 -ddd
> # Running 'numa/mem' benchmark:
>
># Running main,
On Thu 01 Aug 03:07 PDT 2019, Rajendra Nayak wrote:
[..]
> +static const struct msm_pingroup sc7180_groups[] = {
> + [0] = PINGROUP(0, SOUTH, qup01, cri_trng, _, phase_flag, _, _, _, _, _),
> + [1] = PINGROUP(1, SOUTH, qup01, cri_trng, _, phase_flag, _, _, _, _, _),
> + [2] =
On 8/1/2019 5:17 PM, Robert Richter wrote:
Don't you think it'll be confused to have different APIs between EDAC_MC and
EDAC_DEVICE?
(in MC the count passed as part of edac_mc_handle_error())
I don't think edac_mc_handle_error() with 11 function arguments is a
good reference for somethin we
Hello, Greg, all,
I've just double-checked your backports, indeed, they are fine.
Check for operations is not added for protocols which does not
use these operations. Thanks!
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
- Original Message -
>
The PSOC scratch-pad registers are used for communication with the
device CPU. This patch adds new definitions for these registers which
are more descriptive than their general names.
The new set of definitions also gathers and documents the current usage
of the scratch-pad registers by the
Add a meaningful name to the general PSOC application status register
which better describes its usage in keeping the HW state.
Signed-off-by: Tomer Tayar
---
drivers/misc/habanalabs/goya/goya.c | 4 ++--
drivers/misc/habanalabs/include/goya/goya_reg_map.h | 2 ++
2 files
Michael reported an issue with perf bench numa failing with
binding to cpu0 with '-0' option.
# perf bench numa mem -p 3 -t 1 -P 512 -s 100 -zZcm0 --thp 1 -M 1 -ddd
# Running 'numa/mem' benchmark:
# Running main, "perf bench numa numa-mem -p 3 -t 1 -P 512 -s 100 -zZcm0
--thp 1 -M 1 -ddd"
kprobes manipulates the interrupted PSTATE for single step, and
doesn't restore it. Thus, if we put a kprobe where the pstate.D
(debug) masked, the mask will be cleared after the kprobe hits.
Moreover, in the most complicated case, this can lead a kernel
crash with below message when a nested
Hi Will,
On Thu, 1 Aug 2019 15:10:09 +0100 Will Deacon wrote:
>
> On Thu, Aug 01, 2019 at 11:56:14PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Commit
> >
> > 23fb9748a46d ("arm64: Lower priority mask for GIC_PRIO_IRQON")
> >
> > is missing a Signed-off-by from its committer.
>
>
All the way back to introducing dma_common_mmap we've defaulyed to mark
the pages as uncached. But this is wrong for DMA coherent devices or
if using DMA_ATTR_NON_CONSISTENT. Later on DMA_ATTR_WRITE_COMBINE
also got incorrect treatment as that flag is only treated special on
the alloc side for
+++ Matthew Garrett [31/07/19 15:15 -0700]:
From: David Howells
If the kernel is locked down, require that all modules have valid
signatures that we can verify.
I have adjusted the errors generated:
(1) If there's no signature (ENODATA) or we can't check it (ENOPKG,
ENOKEY), then:
--
Hello Dear,
I am Caroline Tagro, I am 22 yrs old an Ivorian national. I solicit
that you to assist me to a fund transfer for urgent project in your
country.
Reply through my email below if you should be interested to help.
Regards From
Caroline
Email: caroline.tagr...@gmail.com
On Thu, Aug 01, 2019 at 07:14:16AM +0200, Vitaly Kuznetsov wrote:
> Regardless of the way how we skip instruction, interrupt shadow needs to be
> cleared.
>
> Signed-off-by: Vitaly Kuznetsov
> Reviewed-by: Jim Mattson
> ---
> arch/x86/kvm/svm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1
On 01.08.19 15:29:03, Hawa, Hanna wrote:
> On 8/1/2019 2:35 PM, Robert Richter wrote:
> > On 15.07.19 13:53:07, Hanna Hawa wrote:
> > > Add a counter parameter in order to avoid losing errors count for edac
> > > device, the error count reports the number of errors reported by an edac
> > > device
On Thu, Aug 01, 2019 at 01:02:18PM +0800, Jason Wang wrote:
>
> On 2019/8/1 上午3:30, Jason Gunthorpe wrote:
> > On Wed, Jul 31, 2019 at 09:28:20PM +0800, Jason Wang wrote:
> > > On 2019/7/31 下午8:39, Jason Gunthorpe wrote:
> > > > On Wed, Jul 31, 2019 at 04:46:53AM -0400, Jason Wang wrote:
> > > >
On Thu, Aug 1, 2019 at 4:57 PM Tomer Tayar wrote:
>
> In case kernel context init fails during device initialization, both
> hl_ctx_put() and kfree() are called, ending with a double free of the
> kernel context.
> Calling kfree() is needed only when a failure happens between the
> allocation of
On Thu, Aug 01, 2019 at 11:56:14PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 23fb9748a46d ("arm64: Lower priority mask for GIC_PRIO_IRQON")
>
> is missing a Signed-off-by from its committer.
Urgh, I just can't get this one right, can I? Let's see if I managed it
this time.
On Fri, 26 Jul 2019 13:55:44 -0700
Andres Freund wrote:
> > Care to send a formal patch?
>
> Will do.
Hi Andres,
Have you had a chance to send a patch?
Thanks!
-- Steve
On Thu, 1 Aug 2019 13:16:22 +0100
Will Deacon wrote:
> On Thu, Jul 25, 2019 at 05:15:54PM +0900, Masami Hiramatsu wrote:
> > kprobes manipulates the interrupted PSTATE for single step, and
> > doesn't restore it. Thus, if we put a kprobe where the pstate.D
> > (debug) masked, the mask will be
Cc few more people
On Thu 01-08-19 15:42:50, Jan Hadrava wrote:
> There seems to be a bug in mm/vmscan.c shrink_slab function when kernel is
> compilled with CONFIG_MEMCG=y and it is then disabled at boot with commandline
> parameter cgroup_disable=memory. SLABs are then not getting shrinked if
On Thu, Aug 01, 2019 at 09:55:55AM -0400, Vladis Dronov wrote:
> Thank you, Greg!
>
> I've just noticed the patch landed in the upstream and was going to start
> stable
> backports, but it appeared you've already done this.
Verifying that I got the 4.4.y and 4.9.y and 4.14.y backports done
On Thu, Aug 01, 2019 at 03:03:06PM +0100, Suzuki K Poulose wrote:
> On 08/01/2019 02:54 PM, Greg KH wrote:
> > On Thu, Aug 01, 2019 at 11:20:24AM +0100, Suzuki K Poulose wrote:
> > > The patch "drivers: Introduce device lookup variants by ACPI_COMPANION
> > > device"
> > > converted an incorrect
Added device tree binding documentation for Nuvoton BMC
NPCM Flash Interface Unit(FIU) SPI master controller
using SPI-MEM interface.
Signed-off-by: Tomer Maimon
---
.../bindings/spi/nuvoton,npcm-fiu.txt | 47 +++
1 file changed, 47 insertions(+)
create mode 100644
This patch set adds Flash Interface Unit(FIU) SPI
master support for the Nuvoton NPCM Baseboard
Management Controller (BMC).
The FIU supports single, dual or quad communication interface.
the FIU controller can operate in following modes:
- User Mode Access(UMA): provides flash access by using
Add Nuvoton NPCM BMC Flash Interface Unit(FIU) SPI master
controller driver using SPI-MEM interface.
The FIU supports single, dual or quad communication interface.
the FIU controller can operate in following modes:
- User Mode Access(UMA): provides flash access by using an
indirect
Hi all,
In commit
9c5718e14b81 ("i2c: at91: disable TXRDY interrupt after sending data")
Fixes tag
Fixes: fac368a0404 ("i2c: at91: add new driver")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
On Wed, 31 Jul 2019 11:25:39 -0400
Steven Rostedt wrote:
> On Thu, 20 Jun 2019 00:07:09 +0900
> Masami Hiramatsu wrote:
>
> > Hello,
> >
> > This is the 2nd version of multi-probes per event support on ftrace
> > and perf-tools.
> >
> > Previous version is here;
> >
On 08/01/2019 02:54 PM, Greg KH wrote:
On Thu, Aug 01, 2019 at 11:20:24AM +0100, Suzuki K Poulose wrote:
The patch "drivers: Introduce device lookup variants by ACPI_COMPANION device"
converted an incorrect instance in i2c driver to a new helper. Revert this
change.
Reported-by: Stephen
Hi all,
Commit
66b25f247e90 ("ASoC: amd: use dma_ops of parent device for acp3x dma driver")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpOfBDcPerjx.pgp
Description: OpenPGP digital signature
On 7/31/19 8:28 AM, Thomas Huth wrote:
The kvm_create_max_vcpus test has been moved to the main directory,
and sync_regs_test is now available on s390x, too.
Signed-off-by: Thomas Huth
---
tools/testing/selftests/kvm/.gitignore | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
In case kernel context init fails during device initialization, both
hl_ctx_put() and kfree() are called, ending with a double free of the
kernel context.
Calling kfree() is needed only when a failure happens between the
allocation of the kernel context and its initialization, so move it to
there
On Tue, Jul 30, 2019 at 11:15:34AM -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.
>
> //
> @@
>
Hi all,
Commit
23fb9748a46d ("arm64: Lower priority mask for GIC_PRIO_IRQON")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpd1CWwJ_DFD.pgp
Description: OpenPGP digital signature
Thank you, Greg!
I've just noticed the patch landed in the upstream and was going to start stable
backports, but it appeared you've already done this.
So, not only automated mailers are slow :)
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
-
On Thu, Aug 01, 2019 at 11:20:24AM +0100, Suzuki K Poulose wrote:
> The patch "drivers: Introduce device lookup variants by ACPI_COMPANION device"
> converted an incorrect instance in i2c driver to a new helper. Revert this
> change.
>
> Reported-by: Stephen Rothwell
> Cc: Mika Westerberg
> Cc:
The commit 069d11465a80 ("net/mlx5e: RX, Enhance legacy Receive Queue
memory scheme") introduced an undefined behaviour below due to
"frag->last_in_page" is only initialized in mlx5e_init_frags_partition()
when,
if (next_frag.offset + frag_info[f].frag_stride > PAGE_SIZE)
or after bailed out the
On Thu, Aug 01, 2019 at 01:31:31PM +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: .
>
> The bot has tested the following trees: v5.2.4, v5.1.21, v4.19.62, v4.14.134,
> v4.9.186, v4.4.186.
There seems to be a bug in mm/vmscan.c shrink_slab function when kernel is
compilled with CONFIG_MEMCG=y and it is then disabled at boot with commandline
parameter cgroup_disable=memory. SLABs are then not getting shrinked if the
system memory is consumed by userspace.
This issue is present in
On Thu, Aug 01, 2019 at 01:13:50PM +0200, Peter Zijlstra wrote:
> A rather embarrasing mistake had us call sched_setscheduler() before
> initializing the parameters passed to it.
>
> Cc: Juri Lelli
> Cc: "Paul E. McKenney"
Thank you for having CCed me this time. ;-)
Reviewed-by: Paul E.
Hallo, ich hoffe du bekommst meine Nachrichtenvorschläge?
Vielen Dank
Michelle
The pull request you sent on Thu, 1 Aug 2019 12:43:19 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git tags/mmc-v5.3-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1e78030e5e5b2d8b0cad7136caf9cfab986a6bff
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Thu, 1 Aug 2019 10:53:48 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
> tags/gpio-v5.3-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/28f5ab1e12ba702389c41bc95d02733673020d85
Thank you!
--
On Thu, Aug 01, 2019 at 03:31:34PM +0200, Geert Uytterhoeven wrote:
> Hi Sudeep,
>
> On Thu, Aug 1, 2019 at 3:15 PM Sudeep Holla wrote:
> > On Mon, Jun 17, 2019 at 04:35:47PM +0200, Geert Uytterhoeven wrote:
> > > "git diff" says:
> > >
> > > \ No newline at end of file
> > >
> > > after
601 - 700 of 1042 matches
Mail list logo
