On 10/8/19 7:44 AM, Kirill A. Shutemov wrote:
On Mon, Oct 07, 2019 at 04:30:30PM +0200, Michal Hocko wrote:
On Mon 07-10-19 16:19:59, Vlastimil Babka wrote:
On 10/2/19 10:43 AM, Michal Hocko wrote:
On Wed 02-10-19 06:16:43, Yang Shi wrote:
The commit
On Mon, 7 Oct 2019 15:08:43 +0800, MarkLee wrote:
> Add missing configuration for mt7629 gmii mode support
>
> Fixes: 7e538372694b ("net: ethernet: mediatek: Re-add support SGMII")
Thank you for adding the Fixes tag. It seem, however, that the patch in
question did not change the ge_mode
On Mon, 7 Oct 2019 15:08:42 +0800, MarkLee wrote:
> This patch target to update mt7629 eth driver and dts to support PHYLINK
Thanks for the patches Mark. The description of the set should probably
say that it _fixes_ some issues. Right now it sounds a little bit like
you were adding a new
The pull request you sent on Tue, 8 Oct 2019 22:42:58 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git
> tags/led-fixes-for-5.4-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e3280b54afed870d531571212f1fc375df39b7d2
Thank you!
On Tue, Oct 8, 2019 at 11:15 AM Kees Cook wrote:
>
> On Tue, Oct 08, 2019 at 10:48:37AM -0700, Brendan Higgins wrote:
> > On Mon, Oct 07, 2019 at 02:36:33PM -0700, David Gow wrote:
> > > This change adds a KUnit test for the kernel doubly linked list
> > > implementation in include/linux/list.h
>
Quoting Evan Green (2019-10-07 14:20:47)
> On Fri, Oct 4, 2019 at 4:31 PM Stephen Boyd wrote:
> >
> > We'll end up with debugfs collisions if we don't give names to the
> > regmaps created inside this driver. Copy the template config over into
> > this function and give the regmap the same name
On Tue, Oct 8, 2019 at 11:16 PM Bjorn Helgaas wrote:
>
> On Tue, Oct 08, 2019 at 11:27:51AM +0200, Rafael J. Wysocki wrote:
> > On Tue, Oct 8, 2019 at 12:34 AM Bjorn Helgaas wrote:
> > > On Thu, Aug 08, 2019 at 11:55:07PM +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> > > >
>
On Mon, Oct 07, 2019 at 12:12:08PM -0700, James Bottomley wrote:
> From: James Bottomley
> Subject: [PATCH] tpm: use GFP kernel for tpm_buf allocations
>
> The current code uses GFP_HIGHMEM, which is wrong because GFP_HIGHMEM
> (on 32 bit systems) is memory ordinarily inaccessible to the kernel
On Tue, Oct 08 2019, J . Bruce Fields wrote:
> On Tue, Oct 08, 2019 at 10:02:53AM +, Pavel Tikhomirov wrote:
>> Add Neil to CC, sorry, had lost it somehow...
>
> Always happy when we can fix a bug by deleting code, and your
> explanation makes sense to me, but I'll give Neil a chance to
Quoting patrick.rudo...@9elements.com (2019-10-08 04:53:25)
> From: Patrick Rudolph
>
> Expose coreboot's binary FMAP[1] to /sys/firmware/fmap.
>
> coreboot copies the FMAP to a CBMEM buffer at boot since CB:35377[2],
> allowing an architecture independ way of exposing the FMAP to userspace.
>
Hi all,
Today's linux-next merge of the bpf-next tree got a conflict in:
tools/lib/bpf/Makefile
between commit:
1bd63524593b ("libbpf: handle symbol versioning properly for libbpf.a")
from the bpf tree and commit:
e01a75c15969 ("libbpf: Move bpf_{helpers, helper_defs, endian,
Quoting patrick.rudo...@9elements.com (2019-10-08 04:53:26)
> From: Patrick Rudolph
>
> Expose the name of the active CBFS partition under
> /sys/firmware/cbfs_active_partition
Somehow we've gotten /sys/firmware/log to be the coreboot log, and quite
frankly that blows my mind that this path was
On Mon, 23 Sep 2019 04:12:17 PDT (-0700), pbonz...@redhat.com wrote:
On 04/09/19 18:15, Anup Patel wrote:
+ unsigned long guest_sstatus =
+ vcpu->arch.guest_context.sstatus | SR_MXR;
+ unsigned long guest_hstatus =
+
On Sun, 22 Sep 2019 21:25:18 PDT (-0700), pet...@redhat.com wrote:
The idea comes from the upstream discussion between Linus and Andrea:
https://lore.kernel.org/lkml/20171102193644.gb22...@redhat.com/
A summary to the issue: there was a special path in handle_userfault()
in the past that
Use the correct function type for sys_ni_syscall in system
call tables to fix indirect call mismatches with Control-Flow
Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/entry/syscall_32.c| 8 +++-
arch/x86/entry/syscall_64.c| 14 ++
> From: Vitaly Kuznetsov
> Sent: Tuesday, October 8, 2019 6:00 AM
> ...
> > Looking at the uses of VERSION_INVAL, I find one remaining occurrence
> > of this macro in vmbus_bus_resume(), which does:
> >
> > if (vmbus_proto_version == VERSION_INVAL ||
> > vmbus_proto_version == 0) {
>
This patch set changes x86 syscall wrappers and related functions to
use function types that match sys_call_ptr_t. This fixes indirect call
mismatches with Control-Flow Integrity (CFI) checking.
Changes since v1:
- Use SYSCALL_DEFINE0 for __x64_sys_ni_syscall.
- Include Andy's
From: Andy Lutomirski
x86 has special handling for COMPAT_SYSCALL_DEFINEx, but there was
no override for COMPAT_SYSCALL_DEFINE0. Wire it up so that we can
use it for rt_sigreturn.
Signed-off-by: Andy Lutomirski
Signed-off-by: Sami Tolvanen
---
arch/x86/include/asm/syscall_wrapper.h | 32
Define a weak function in COND_SYSCALL instead of a weak alias to
sys_ni_syscall, which has an incompatible type. This fixes indirect
call mismatches with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/include/asm/syscall_wrapper.h | 21 -
1
Although a syscall defined using SYSCALL_DEFINE0 doesn't accept
parameters, use the correct function type to avoid type mismatches
with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
Acked-by: Andy Lutomirski
---
arch/x86/include/asm/syscall_wrapper.h | 23
Use COMPAT_SYSCALL_DEFINE0 to define (rt_)sigreturn syscalls to
replace sys32_sigreturn and sys32_rt_sigreturn. This fixes indirect
call mismatches with Control-Flow Integrity (CFI) checking.
Signed-off-by: Sami Tolvanen
---
arch/x86/entry/syscalls/syscall_32.tbl | 4 ++--
On Fri, 20 Sep 2019 21:34:57 PDT (-0700), a...@brainfault.org wrote:
On Sat, Sep 21, 2019 at 6:30 AM Albert Ou wrote:
This fixes an error with how the FDT blob is reserved in memblock.
An incorrect physical address calculation exposed the FDT header to
unintended corruption, which typically
rmi_process_interrupt_requests() calls handle_nested_irq() for
each interrupt status bit it finds. If the irq domain mapping for
this bit had not yet been set up, then it ends up calling
handle_nested_irq(0), which causes a NULL pointer dereference.
There's already code that masks the irq_status
Hello,
syzbot found the following crash on:
HEAD commit:1e76a3e5 kmsan: replace __GFP_NO_KMSAN_SHADOW with kmsan_i..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=130b16fd60
kernel config:
LGTM.
Reviewed-by: Daniel Campello
struct iowarrior gets freed prematurely in iowarrior_release while
it is still being referenced from usb_interface, so let only
iowarrior_disconnect call iowarrior_delete.
Fixes: KMSAN: uninit-value in iowarrior_disconnect
Reported-by: syzbot+0761012cebf7bdb38...@syzkaller.appspotmail.com
Hi Petr,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc2 next-20191008]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
Hi,
Please find the following patches which help support
Non-Transparent-Bridge (NTB) devices on AMD platforms with the IOMMU
enabled.
The first patch implements dma_map_resource() correctly with the AMD
IOMMU. This is required for correct functioning of ntb_transport which
uses that interface.
On Tue, Sep 24, 2019 at 12:51 PM Sami Tolvanen wrote:
> Someone else probably knows better, but yes, we could also fix this by
> changing set_fixmap to accept enum fixed_addresses as the first
> parameter, and changing the type of xen_set_fixmap instead.
This approach is actually more
USB PowerShare is a policy which affects charging via the special
USB PowerShare port (marked with a small lightning bolt or battery icon)
when in low power states:
- In S0, the port will always provide power.
- In S0ix, if usb_charge is enabled, then power will be supplied to
the port when on
"Michael Kerrisk (man-pages)" writes:
> On 10/8/19 9:40 PM, Eric W. Biederman wrote:
>> "Michael Kerrisk (man-pages)" writes:
>>
>>> Hello Eric,
>>>
>> Creating of a mount namespace in a user namespace automatically does
>> 'mount("", "/", MS_SLAVE | MS_REC, NULL);' if the starting
On Tue, Oct 8, 2019 at 2:27 PM 'Sami Tolvanen' via Clang Built Linux
wrote:
>
> Unlike gcc, clang considers each inline assembly block to be independent
> and therefore, when using the integrated assembler for inline assembly,
> any preambles that enable features must be repeated in each block.
>
This new trace option "console-latency" will enable the latency
tracers to trace the console latencies. Previously this has always been
implicitely disabled. I guess this is because they are considered
to be well known and unavoidable.
However, for some organizations it may nevertheless be
This burst feature enables the user to generate a burst of
preempt/irqsoff latencies. This makes it possible to test whether we
are able to detect latencies that systematically occur very close to
each other.
The maximum burst size is 10. We also create 10 identical test
functions, so that we get
This is a tool that is intended to work around the fact that the
preemptoff, irqsoff, and preemptirqsoff tracers only work in
overwrite mode. The idea is to act randomly in such a way that we
do not systematically lose any latencies, so that if enough testing
is done, all latencies will be
Hello all,
I have retained the fourth patch, although it was suggested that is becoming
obsolete soon. I have retained it only because I do not know the status of
the code that will make it obsolete. It's the last patch of the series and
if there indeed is some code that will remove the latency
This patch implements the feature that the tracing_max_latency file,
e.g. /sys/kernel/debug/tracing/tracing_max_latency will receive
notifications through the fsnotify framework when a new latency is
available.
One particularly interesting use of this facility is when enabling
threshold tracing,
On 10/08/2019 05:38 PM, Bjorn Helgaas wrote:
On Thu, Oct 03, 2019 at 05:10:07PM -0500, Bjorn Helgaas wrote:
On Thu, Oct 03, 2019 at 11:04:45AM +0200, CREGUT Pierre IMT/OLN wrote:
...
NIC drivers send netlink events when their state change, but it is
the core that changes the value of
On Mon, Oct 07, 2019 at 10:50:21PM +0200, Stephan Gerhold wrote:
> MMS345L is another first generation touch screen from Melfas,
> which uses the same registers as MMS152.
>
> However, using I2C_M_NOSTART for it causes errors when reading:
>
> i2c i2c-0: sendbytes: NAK bailout.
>
On Tue, Oct 08, 2019 at 02:44:26PM +0300, Andi Shyti wrote:
> Hi Stephan,
>
> > device_get_match_data is available now, so we can replace the call
> > to of_device_get_match_data and remove the FIXME comment.
> >
> > Signed-off-by: Stephan Gerhold
>
> Reviewed-by: Andi Shyti
Applied, thank
From: Ivan Lazeev
Bug link: https://bugzilla.kernel.org/show_bug.cgi?id=195657
cmd/rsp buffers are expected to be in the same ACPI region.
For Zen+ CPUs BIOS's might report two different regions, some of
them also report region sizes inconsistent with values from TPM
registers.
Memory
Dne petek, 27. september 2019 ob 16:34:08 CEST je Paul Kocialkowski
napisal(a):
> HEVC/H.265 stateless support for V4L2 and Cedrus
>
> This is early support for HEVC/H.265 stateless decoding in V4L2,
> including both definitions and driver support for the Cedrus VPU
> driver, which concerns
On Tue, Oct 08, 2019 at 03:55:46PM +0100, Alan Maguire wrote:
> Documentation should describe how to build kunit and tests as
> modules.
>
> Signed-off-by: Alan Maguire
> Signed-off-by: Knut Omang
>
> ---
> Documentation/dev-tools/kunit/faq.rst | 3 ++-
>
On 08.10.19 22:18, Qian Cai wrote:
> The linux-next series "mm/memory_hotplug: Shrink zones before removing memory"
> [1] causes a kernel panic while reading /proc/kpagecount after offlining a
> memory section. It was reproduced on both x86 and powerpc. Reverted the whole
> series fixed the
On 10/8/19 9:40 PM, Eric W. Biederman wrote:
> "Michael Kerrisk (man-pages)" writes:
>
>> Hello Eric,
>>
> Creating of a mount namespace in a user namespace automatically does
> 'mount("", "/", MS_SLAVE | MS_REC, NULL);' if the starting mount
> namespace was not created in that user
Add the intermediate p4d accessors to make it 5 level compliant.
Thi sis non-functional change anyways since ARC has software page walker
with 2 lookup levels (pgd -> pte)
Signed-off-by: Vineet Gupta
---
arch/arc/include/asm/pgtable.h | 1 -
arch/arc/mm/fault.c| 10 --
2
On Thu, Oct 03, 2019 at 05:10:07PM -0500, Bjorn Helgaas wrote:
> On Thu, Oct 03, 2019 at 11:04:45AM +0200, CREGUT Pierre IMT/OLN wrote:
> > ...
> > NIC drivers send netlink events when their state change, but it is
> > the core that changes the value of num_vfs. So I would think it is
> > the
On Tue, Oct 08, 2019 at 03:55:44PM +0100, Alan Maguire wrote:
> as tests are added to kunit, it will become less feasible to execute
> all built tests together. By supporting modular tests we provide
> a simple way to do selective execution on a running system; specifying
>
> CONFIG_KUNIT=y
>
On Mon, 7 Oct 2019, Steven Price wrote:
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information is provided by the
> p?d_leaf() functions/macros.
>
> For
On Tue, Oct 08, 2019 at 08:25:23AM +, Robert Richter wrote:
> On 04.10.19 14:48:13, Bjorn Helgaas wrote:
> > commit 37b22fbfec2d
> > Author: George Cherian
> > Date: Thu Sep 19 02:43:34 2019 +
> >
> > PCI: Apply Cavium ACS quirk to CN99xx and CN11xxx Root Ports
> >
> > Add
Unlike gcc, clang considers each inline assembly block to be independent
and therefore, when using the integrated assembler for inline assembly,
any preambles that enable features must be repeated in each block.
This change defines __LSE_PREAMBLE and adds it to each inline assembly
block that has
On Tue, Oct 8, 2019 at 10:44 PM Nicolas Dufresne wrote:
>
> Le mardi 08 octobre 2019 à 16:27 -0400, Nicolas Dufresne a écrit :
> > Le lundi 07 octobre 2019 à 16:59 +0200, Maxime Jourdan a écrit :
> > > Add support for the H264 compressed format (V4L2_PIX_FMT_H264).
> > >
> > > Signed-off-by:
Hi All:
net/wireless/chan.c:
Inside function cfg80211_chandef_compatible(), variable "c1_pri40",
" c2_pri40", "c1_pri80" and "c2_pri80" could be uninitialized if
chandef_primary_freqs() fails. However, they are used later in the if
statement to decide the control flow, which is potentially unsafe.
On Tue, Oct 08, 2019 at 11:27:51AM +0200, Rafael J. Wysocki wrote:
> On Tue, Oct 8, 2019 at 12:34 AM Bjorn Helgaas wrote:
> > On Thu, Aug 08, 2019 at 11:55:07PM +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > Add a function checking whether or not PCIe ASPM has been
I think that's a fair point. Sorry for not noticing it earlier.
> On Tue, Oct 8, 2019, 6:12 PM Andy Shevchenko <
> andriy.shevche...@linux.intel.com> wrote:
> > Maybe we can even split this to two patches?
I assume splitting means one to add devm_ioremap_uc and one to use it
for intel-lpss-pci.
syzbot has bisected this bug to:
commit 057af70713445fad2459aa348c9c2c4ecf7db938
Author: Jiri Pirko
Date: Sat Oct 5 18:04:39 2019 +
net: tipc: have genetlink code to parse the attrs during dumpit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11675620e0
start
On Tue, 8 Oct 2019 at 18:19, Robin Murphy wrote:
>
> On 08/10/2019 16:22, Sami Tolvanen wrote:
> > On Mon, Oct 7, 2019 at 2:46 PM 'Nick Desaulniers' via Clang Built
> > Linux wrote:
> >> I'm worried that one of these might lower to LSE atomics without
> >> ALTERNATIVE guards by blanketing all C
On Tue, Oct 08, 2019 at 03:55:43PM +0100, Alan Maguire wrote:
> The current kunit execution model is to provide base kunit functionality
> and tests built-in to the kernel. The aim of this series is to allow
> building kunit itself and tests as modules. This in turn allows a
Cool! I had plans
From: Michael Kelley Sent: Friday, October 4, 2019
3:33 PM
>
> From: Roman Kagan Sent: Friday, October 4, 2019 2:19 AM
> >
> > On Fri, Oct 04, 2019 at 03:01:51AM +, Michael Kelley wrote:
> > > From: Roman Kagan Sent: Thursday, October 3, 2019
> > > 5:53 AM
> > > > >
> > > > > AFAIU
Hi Rob/Robin,
On Tue, 2019-10-08 at 14:52 -0500, Rob Herring wrote:
> From: Robin Murphy
>
> Since the "dma-ranges" property is only valid for a node representing a
> bus, of_dma_get_range() currently assumes the node passed in is a leaf
> representing a device, and starts the walk from its
On Wed, 9 Oct 2019 07:38:03 +1100
Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 69eea31a26da ("arm64: dts: armada-3720-turris-mox: convert usb-phy to
> phy-supply")
>
> Fixes tag
>
> Fixes: eb6c2eb6c7fb ("usb: host: xhci-plat: Prevent an abnormally
>
This is weird, in the patch
On Mon, 2019-10-07 at 10:27 -0700, Alexander Duyck wrote:
> From: Alexander Duyck
>
> This patch is meant to address possible race conditions that can exist
> between network configuration and power management. A similar issue was
> fixed for igb in commit 9474933caf21 ("igb: close/suspend race
Update the document to be consistent in case when using "LED".
This acronym should be capital throughout the document.
Signed-off-by: Dan Murphy
---
Documentation/devicetree/bindings/leds/leds-lp55xx.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Add DT bindings for the LEDs multicolor class framework.
Signed-off-by: Dan Murphy
---
.../bindings/leds/leds-class-multicolor.txt | 98 +++
1 file changed, 98 insertions(+)
create mode 100644
Documentation/devicetree/bindings/leds/leds-class-multicolor.txt
diff --git
Introduce the LP5036/30/24/18/12/9 RGB LED driver.
The difference in these parts are the number of
LED outputs where the:
LP5036 can control 36 LEDs
LP5030 can control 30 LEDs
LP5024 can control 24 LEDs
LP5018 can control 18 LEDs
LP5012 can control 12 LEDs
LP5009 can control 9 LEDs
The device
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"
CC: Linus Walleij
CC: Shawn Guo
CC: Sascha Hauer
CC: Pengutronix Kernel Team
CC: Fabio Estevam
Add the intensity function call back to support the multicolor
framework. This function allows setting a specific brightness on
a specific channel.
Signed-off-by: Dan Murphy
---
drivers/leds/leds-lp5523.c | 20
1 file changed, 20 insertions(+)
diff --git
Add the intensity function call back to support the multicolor
framework. This function allows setting a specific brightness on
a specific channel.
Signed-off-by: Dan Murphy
---
drivers/leds/leds-lp5521.c | 20
1 file changed, 20 insertions(+)
diff --git
Add the reg property to each channel node. This update is
to accomodate the multicolor framework. In addition to the
accomodation this allows the LEDs to be placed on any channel
and allow designs to skip channels as opposed to requiring
sequential order.
Signed-off-by: Dan Murphy
CC: Tony
Introduce the bindings for the Texas Instruments LP5036, LP5030, LP5024,
LP5018, LP5012 and LP5009 RGB LED device driver. The LP5036/30/24/18/12/9
can control RGB LEDs individually or as part of a control bank group.
These devices have the ability to adjust the mixing control for the RGB
LEDs to
Add a new color ID that is declared as MULTICOLOR as with the
multicolor framework declaring a definitive color is not accurate
as the node can contain multiple colors.
Signed-off-by: Dan Murphy
---
drivers/leds/led-core.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Add the reg property to each channel node. This update is
to accomodate the multicolor framework. In addition to the
accomodation this allows the LEDs to be placed on any channel
and allow designs to skip channels as opposed to requiring
sequential order.
Signed-off-by: Dan Murphy
CC: Linus
Introduce a multicolor class that groups colored LEDs
within a LED node.
The multi color class groups monochrome LEDs and allows controlling two
aspects of the final combined color: hue and lightness. The former is
controlled via _intensity files and the latter is controlled
via brightness file.
Add multicolor framework support for the lp55xx family.
Signed-off-by: Dan Murphy
---
drivers/leds/Kconfig | 1 +
drivers/leds/leds-lp55xx-common.c | 176 +++---
drivers/leds/leds-lp55xx-common.h | 11 ++
Fix checkpatch errors and warnings for the LP5523.c device
driver.
Signed-off-by: Dan Murphy
---
drivers/leds/leds-lp5523.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/leds/leds-lp5523.c b/drivers/leds/leds-lp5523.c
index
Add a new color ID that is declared as MULTICOLOR as with the
multicolor framework declaring a definitive color is not accurate
as the node can contain multiple colors.
Signed-off-by: Dan Murphy
---
include/dt-bindings/leds/common.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Hello
This is v11 of the multicolor framework patchset.
This patchet has been tested on LP5523, LP5521, and the LP5012,24 and 36 evms
connected to a beagle bone black. For the LP5523/5521 I have tested with both
MC and non-MC DT as well as an intermixed DT with color and white LEDs.
Changes
Fix the checkpatch warnings for the use of the file permission macros.
In converting the file permissions to the DEVICE_ATTR_XX macros the
call back function names needed to be updated within the code.
This means that the lp55xx_ needed to be dropped in the name to keep in
harmony with the ABI
Add the reg property to each channel node. This update is
to accomodate the multicolor framework. In addition to the
accomodation this allows the LEDs to be placed on any channel
and allow designs to skip channels as opposed to requiring
sequential order.
Signed-off-by: Dan Murphy
CC: Shawn
Inside function hpet_msi_resume(), variable "msg" could be
uninitialized if irq_chip_compose_msi_msg() returns -ENOSYS.
However, it is directly used in hpet_msi_write(), which is
potentially unsafe.
Signed-off-by: Yizhuo
---
arch/x86/kernel/hpet.c | 1 +
1 file changed, 1 insertion(+)
diff
Cc: Peter Hurley
Cc: Greg Kroah-Hartman
---
drivers/tty/serial/serial_core.c |2 ++
1 file changed, 2 insertions(+)
--- linux-next-20191008.orig/drivers/tty/serial/serial_core.c
+++ linux-next-20191008/drivers/tty/serial/serial_core.c
@@ -1964,8 +1964,10 @@ uart_get_console(struct uart_p
Le mardi 08 octobre 2019 à 16:27 -0400, Nicolas Dufresne a écrit :
> Le lundi 07 octobre 2019 à 16:59 +0200, Maxime Jourdan a écrit :
> > Add support for the H264 compressed format (V4L2_PIX_FMT_H264).
> >
> > Signed-off-by: Maxime Jourdan
> > ---
> > drivers/staging/media/meson/vdec/Makefile
y.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20191008.orig/include/linux/xarray.h
+++ linux-next-20191008/include/linux/xarray.h
@@ -230,8 +230,8 @@ static inline int xa_err(void *entry)
* This structure is used either directly or via the XA_LIMIT() macro
* to c
Hi Linus,
Please pull two patches for 5.4-rc3:
- fix a leftover from earlier stage of development in the documentation
of recently added led_compose_name() and fix old mistake in
the documentation of led_set_brightness_sync() parameter name.
- MAINTAINERS: add pointer to Pavel Machek's
Cc: Thomas Gleixner
Cc: Andrew Morton
---
include/linux/bitmap.h |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- linux-next-20191008.orig/include/linux/bitmap.h
+++ linux-next-20191008/include/linux/bitmap.h
@@ -326,10 +326,11 @@ static inline int bitmap_equal
code")
Signed-off-by: Randy Dunlap
Cc: Linus Walleij
Cc: Bartosz Golaszewski
Cc: linux-g...@vger.kernel.org
---
drivers/gpio/gpiolib-of.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- linux-next-20191008.orig/drivers/gpio/gpiolib-of.c
+++ linux-next-20191008/drivers/gpio/gp
On 2019-10-08 16:12, Jonas Karlman wrote:
> On 2019-10-08 15:53, Tomasz Figa wrote:
>> On Tue, Oct 8, 2019 at 10:35 PM Tomasz Figa wrote:
>>> On Tue, Oct 8, 2019 at 7:42 PM Tomasz Figa wrote:
On Tue, Oct 8, 2019 at 3:31 PM Jonas Karlman wrote:
> On 2019-10-08 07:27, Tomasz Figa wrote:
Hi all,
In commit
69eea31a26da ("arm64: dts: armada-3720-turris-mox: convert usb-phy to
phy-supply")
Fixes tag
Fixes: eb6c2eb6c7fb ("usb: host: xhci-plat: Prevent an abnormally
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no
On Wed, 25 Sep 2019, Rob Herring wrote:
> On Wed, Sep 25, 2019 at 4:24 PM Palmer Dabbelt wrote:
> >
> > On Wed, 25 Sep 2019 06:12:52 PDT (-0700), r...@kernel.org wrote:
> > > Fix the errors in the RiscV CPU DT schema:
> > >
> > > Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml:
On Tue, Oct 08, 2019 at 08:58:58PM +0100, Al Viro wrote:
> The difference is, they have separate "for read" and "for write" primitives
> and they want the range in their user_access_end() analogue. Separating
> the read and write isn't a problem for callers (we want them close to
> the actual
On Tue, Oct 08, 2019 at 06:33:15PM +0200, Enric Balletbo i Serra wrote:
> Hi Uwe,
>
> Thanks for the quick reply.
>
> On 8/10/19 16:34, Uwe Kleine-König wrote:
> > Hello Enric,
> >
> > On Tue, Oct 08, 2019 at 12:54:17PM +0200, Enric Balletbo i Serra wrote:
> >> @@ -117,17 +122,28 @@ static void
Le lundi 07 octobre 2019 à 16:59 +0200, Maxime Jourdan a écrit :
> Add support for the H264 compressed format (V4L2_PIX_FMT_H264).
>
> Signed-off-by: Maxime Jourdan
> ---
> drivers/staging/media/meson/vdec/Makefile | 2 +-
> drivers/staging/media/meson/vdec/codec_h264.c | 482
Hi,
On 08-10-2019 17:38, Kai-Heng Feng wrote:
Runtime power management in i2c-hid brings lots of issues, such as:
- When transitioning from display manager to desktop session, i2c-hid
was closed and opened, so the device was set to SLEEP and ON in a short
period. Vendors confirmed that their
On Tue, Oct 08, 2019 at 10:02:53AM +, Pavel Tikhomirov wrote:
> Add Neil to CC, sorry, had lost it somehow...
Always happy when we can fix a bug by deleting code, and your
explanation makes sense to me, but I'll give Neil a chance to look it
over if he wants.
--b.
>
> On 10/1/19 11:03 AM,
On 10/4/19 11:39 AM, Bart Van Assche wrote:
> Have you already had a look at the /dev/disk/by-path directory? An
> example of the contents of that directory:
>
> $ (cd /dev/disk/by-path && ls -l | grep /s)
> lrwxrwxrwx 1 root root 9 Oct 3 16:49 pci-:00:02.0-ata-1 -> ../../sda
>
On 10/7/19 8:38 AM, Steven Price wrote:
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information will be provided by the
> p?d_leaf() functions/macros.
>
>
The linux-next series "mm/memory_hotplug: Shrink zones before removing memory"
[1] causes a kernel panic while reading /proc/kpagecount after offlining a
memory section. It was reproduced on both x86 and powerpc. Reverted the whole
series fixed the problem.
[1]
On 19-10-08 17:23, Mark Brown wrote:
> On Tue, Oct 08, 2019 at 06:16:40PM +0200, Marco Felsch wrote:
> > On 19-10-08 16:42, Mark Brown wrote:
>
> > > If this is a GPIO regulator then the Linux APIs mean you can't read the
> > > status back so it's one of the regulators for which this property was
On Tue, Oct 08, 2019 at 08:58:58PM +0100, Al Viro wrote:
> That's powerpc. And while the constant-sized bits are probably pretty
> useless there as well, note the
> allow_read_from_user()/prevent_read_from_user()
> part. Looks suspiciously similar to user_access_begin()/user_access_end()...
>
> Am 08.10.2019 um 10:00 schrieb Tero Kristo :
>
> On 07/10/2019 22:24, H. Nikolaus Schaller wrote:
>> Hi Tero,
>>> Am 07.10.2019 um 21:18 schrieb Tero Kristo :
>>>
>>> On 07/10/2019 18:52, Tony Lindgren wrote:
Hi,
* H. Nikolaus Schaller [191005 16:59]:
Please try with Tero's
101 - 200 of 925 matches
Mail list logo
