On Mon, Sep 30, 2019 at 2:07 PM Benoit Parrot wrote:
>
> On some board it is possible that the sensor 'powerdown' and or 'reset'
> pin might be controlled by gpio instead of being tied.
>
> To implement we add pm_runtime support which will handle the power
> up/down sequence when it is available
On Mon, Sep 30, 2019 at 2:07 PM Benoit Parrot wrote:
>
> In ov2659_s_stream() return value for invoked function should be checked
> and propagated.
>
> Signed-off-by: Benoit Parrot
> ---
> drivers/media/i2c/ov2659.c | 14 +-
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
Mostly this hardware can work with generic PHY driver, but this change
is needed to provided interrupt handling support.
Tested with dsa ar9331-switch driver.
Signed-off-by: Oleksij Rempel
---
drivers/net/phy/at803x.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
struct at803x_priv is never used in this driver. So remove it
and the probe function allocating it.
Suggested-by: Heiner Kallweit
Signed-off-by: Oleksij Rempel
---
drivers/net/phy/at803x.c | 21 -
1 file changed, 21 deletions(-)
diff --git a/drivers/net/phy/at803x.c
Use exact match for all IDs. We have no sanity checks, so we can peek
a device with no exact ID and different register layout.
Suggested-by: Heiner Kallweit
Signed-off-by: Oleksij Rempel
---
drivers/net/phy/at803x.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff
changes v2:
- use PHY_ID_MATCH_EXACT instead of leaky masking
- remove probe and struct at803x_priv
Oleksij Rempel (3):
net: phy: at803x: use PHY_ID_MATCH_EXACT for IDs
net: phy: at803x: add ar9331 support
net: phy: at803x: remove probe and struct at803x_priv
drivers/net/phy/at803x.c | 45
Hi,
On 30-09-2019 22:42, Navid Emamdoost wrote:
In hgcm_call_preprocess_linaddr memory is allocated for bounce_buf but
is not released if copy_form_user fails. In order to prevent memory leak
in case of failure, the assignment to bounce_buf_ret is moved before the
error check. This way the
Hi,
Changes since v2
)https://patchwork.kernel.org/project/linux-dmaengine/list/?series=152609=*)
- Based on 5.4-rc1
- Support for Flow only data transfer for the glue layer
- cppi5 header
- comments converted to kernel-doc style
- Remove the excessive WARN_ONs and rely on the user for sanity
New binding document for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P).
UDMA-P is introduced as part of the K3 architecture and can be found in
AM654 and j721e.
Signed-off-by: Peter Ujfalusi
---
.../devicetree/bindings/dma/ti/k3-udma.txt| 185 ++
Update the provider and client documentation with details about the
metadata support.
Signed-off-by: Peter Ujfalusi
---
Documentation/driver-api/dmaengine/client.rst | 75 +++
.../driver-api/dmaengine/provider.rst | 46
2 files changed, 121 insertions(+)
Split patch for review containing:
device_prep_slave_sg and device_prep_dma_cyclic implementation supporting
packet and TR channels.
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P)
The UDMA-P is intended to perform similar (but significantly upgraded)
From: Grygorii Strashko
The Ring Accelerator (RINGACC or RA) provides hardware acceleration to
enable straightforward passing of work between a producer and a consumer.
There is one RINGACC module per NAVSS on TI AM65x and j721e.
This patch introduces RINGACC device tree bindings.
Split patch for review containing: defines, structs, io and low level
functions and interrupt callbacks.
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P)
The UDMA-P is intended to perform similar (but significantly upgraded) functions
as the
Signed-off-by: Peter Ujfalusi
---
include/linux/dma/ti-cppi5.h | 1049 ++
1 file changed, 1049 insertions(+)
create mode 100644 include/linux/dma/ti-cppi5.h
diff --git a/include/linux/dma/ti-cppi5.h b/include/linux/dma/ti-cppi5.h
new file mode 100644
index
Split patch for review containing:
device_config, device_issue_pending, device_tx_status, device_pause,
device_resume, device_terminate_all and device_synchronize callback
implementation and the custom udma_vchan_complete.
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root
Split patch for review containing: channel rsource allocation and free
functions.
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P)
The UDMA-P is intended to perform similar (but significantly upgraded) functions
as the packet-oriented DMA used on previous
Split patch for review containing: module probe/remove functions, of_xlate
and filter_fn for slave channel requests.
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P)
The UDMA-P is intended to perform similar (but significantly upgraded) functions
as the
Split patch for review containing:
Kconfig and Makefile changes
DMA driver for
Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P)
The UDMA-P is intended to perform similar (but significantly upgraded) functions
as the packet-oriented DMA used on previous SoC devices. The
From: Grygorii Strashko
Certain users can not use right now the DMAengine API due to missing
features in the core. Prime example is Networking.
These users can use the glue layer interface to avoid misuse of DMAengine
API and when the core gains the needed features they can be converted to
use
From: Grygorii Strashko
The Ring Accelerator (RINGACC or RA) provides hardware acceleration to
enable straightforward passing of work between a producer and a consumer.
There is one RINGACC module per NAVSS on TI AM65x SoCs.
The RINGACC converts constant-address read and write accesses to
The metadata is best described as side band data or parameters traveling
alongside the data DMAd by the DMA engine. It is data
which is understood by the peripheral and the peripheral driver only, the
DMA engine see it only as data block and it is not interpreting it in any
way.
The metadata can
A DMA hardware can have big cache or FIFO and the amount of data sitting in
the DMA fabric can be an interest for the clients.
For example in audio we want to know the delay in the data flow and in case
the DMA have significantly large FIFO/cache, it can affect the latenc/delay
Signed-off-by:
On Mon, Sep 30, 2019 at 04:31:51PM -0600, shuah wrote:
> On 9/29/19 7:56 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.2 release.
> > There are 25 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Mon, Sep 30, 2019 at 08:11:37PM -0500, Dan Rue wrote:
> On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.2 release.
> > There are 25 patches in this series, all will be posted as a response
> > to this one. If
On Mon, Sep 30, 2019 at 11:30:15AM -0700, Guenter Roeck wrote:
> On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.2 release.
> > There are 25 patches in this series, all will be posted as a response
> > to this one.
On Sat, Sep 21, 2019 at 11:22:14AM +0100, Okash Khawaja wrote:
> Speakup exposes a set of sysfs attributes under
> /sys/accessibility/speakup/ for user-space to interact with and
> configure speakup's kernel modules. This patch describes those
> attributes. Some attributes either lack a
On Mon, Sep 30, 2019 at 01:23:10AM -0700, Christoph Hellwig wrote:
> And drivers really have no business looking at the dma mask. I have
> a plan for dma_alloc_pages API that could replace that cruft, but
> until then please use GFP_KERNEL and let the dma subsystem bounce
> buffer if needed.
Can
On Mon, 30 Sep 2019, Lukasz Majewski wrote:
> Dear Lee,
>
> > This patch set provides several enhancements to mc13xxx MFD family
> > of devices by introducing mc34708 as a separate device.
> >
> > This IC has dedicated pen detection feature, which allows better
> > touchscreen experience.
> >
On Wed, Sep 25, 2019 at 04:54:37PM -0400, Qian Cai wrote:
> Ping. Please take a look at this trivial patch.
No need to rush. We just had the 5.4 merge window closing. I'll
queue this up in the dma-mapping for-next tree for 5.5 once I open it.
This patch is syncing driver with actual devicetree documentation:
Documentation/devicetree/bindings/net/qca,ar71xx.txt
|Optional subnodes:
|- mdio : specifies the mdio bus, used as a container for phy nodes
| according to phy.txt in the same directory
The driver was working with fixed phy
On 30.09.19 16:50:46, Borislav Petkov wrote:
> --
> On Mon, Sep 23, 2019 at 08:17:40PM +0100, Hanna Hawa wrote:
> > +void edac_device_handle_ce(struct edac_device_ctl_info *edac_dev,
> > + int inst_nr, int
Currently, vmalloc space is backed by the early shadow page. This
means that kasan is incompatible with VMAP_STACK.
This series provides a mechanism to back vmalloc space with real,
dynamically allocated memory. I have only wired up x86, because that's
the only currently supported arch I can work
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 +
Test kasan vmalloc support by adding a new test to the module.
Signed-off-by: Daniel Axtens
--
v5: split out per Christophe Leroy
---
lib/test_kasan.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/lib/test_kasan.c b/lib/test_kasan.c
index
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
Provide the current number of vmalloc shadow pages in
/sys/kernel/debug/kasan/vmalloc_shadow_pages.
Signed-off-by: Daniel Axtens
---
v8: rename kasan_vmalloc/shadow_pages -> kasan/vmalloc_shadow_pages
On v4 (no dynamic freeing), I saw the following approximate figures
on my test VM:
- fresh
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
On Mon, Sep 30, 2019 at 05:23:18PM -0700, Atish Patra wrote:
> /proc/cpuinfo should just print all the isa string as an information
> instead of determining what is supported or not. ELF hwcap can be
> used by the userspace to figure out that.
>
> Simplify the isa string printing by removing the
Hello Fabrice,
On Mon, Sep 30, 2019 at 05:39:11PM +0200, Fabrice Gasnier wrote:
> Add suspend/resume PM sleep ops. When going to low power, enforce the PWM
> channel isn't active. Let the PWM consumers disable it during their own
> suspend sequence, see [1]. So, perform a check here, and handle
I'm announcing the release of the 5.3.2 kernel.
All users of the 5.3 kernel series must upgrade.
The updated 5.3.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.3.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index f32e8d2e09c3..13fa3a409ddd 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 3
-SUBLEVEL = 1
+SUBLEVEL = 2
EXTRAVERSION =
NAME = Bobtail Squid
diff --git a/arch/powerpc/include/asm/opal.h
On Tue, Oct 01, 2019 at 05:00:25AM +, Zhang, Jun wrote:
> Please see my comments.
>
Please use a normal MUA that can quote text you're replying to. This is
unreadable garbage.
On Tue, Oct 01, 2019 at 09:04:57AM +0200, Greg KH wrote:
> I'm announcing the release of the 5.3.2 kernel.
>
> All users of the 5.3 kernel series must upgrade.
Ok, I messed up this morning and typed "5.3" instead of "5.2" in my
scripts and an "empty" 5.3.3 kernel got released. Well kind of, it
This reverts commit 883a2a80f79ca5c0c105605fafabd1f3df99b34c.
Apparently use dmi_get_bios_year() as manufacturing date isn't accurate
and this breaks older laptops with new BIOS update.
So let's revert this patch.
There are still new HP laptops still need to use SMBus to support all
features,
Hi,
Reviewed-by: Pierre-Yves MORDRET
Thx
On 9/30/19 5:28 PM, Fabrice Gasnier wrote:
> The slave-interface documentation [1] states "the bus driver should
> transmit the first byte" upon I2C_SLAVE_READ_REQUESTED slave event:
> - 'val': backend returns first byte to be sent
> The driver
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 for a while so that I could eventually convert gfs2
over to it, but I never got to it. Now Damien has a new zonefs
file system for
diff --git a/Makefile b/Makefile
index 4bf6f24916bf..9cb471a75a1b 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 75
+SUBLEVEL = 76
EXTRAVERSION =
NAME = "People's Front"
diff --git
I'm announcing the release of the 4.19.76 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
In preparation for moving the writeback code to iomap.c, replace the
XFS-specific COW fork concept with the iomap IOMAP_F_SHARED flag.
Signed-off-by: Christoph Hellwig
Reviewed-by: Carlos Maiolino
Reviewed-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 42
Now that all the writepage code is in the iomap code there is no
need to keep this structure public.
Signed-off-by: Christoph Hellwig
Reviewed-by: Carlos Maiolino
Reviewed-by: Darrick J. Wong
---
fs/iomap/buffered-io.c | 17 +
include/linux/iomap.h | 17 -
2
In preparation for moving the XFS writeback code to fs/iomap.c, switch
it to use struct iomap instead of the XFS-specific struct xfs_bmbt_irec.
Signed-off-by: Christoph Hellwig
Reviewed-by: Carlos Maiolino
Reviewed-by: Darrick J. Wong
---
fs/xfs/libxfs/xfs_bmap.c | 14 +--
The actual iomap implementations now have equivalent trace points.
Signed-off-by: Christoph Hellwig
---
fs/xfs/xfs_aops.c | 2 --
fs/xfs/xfs_trace.h | 26 --
2 files changed, 28 deletions(-)
diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
index
And inline mapping should never mark the page dirty and thus never end up
in writepages. Add a check for that condition and warn if it happens.
Signed-off-by: Christoph Hellwig
Reviewed-by: Darrick J. Wong
Signed-off-by: Darrick J. Wong
---
fs/iomap/buffered-io.c | 2 ++
1 file changed, 2
Takes the xfs writeback code and copies it to iomap.c. A new structure
with three methods is added as the abstraction from the generic
writeback code to the file system. These methods are used to map
blocks, submit an ioend, and cancel a page that encountered an error
before it was added to an
File systems like gfs2 don't support delayed allocations or unwritten
extents and thus allocate normal mapped blocks to fill holes. To
cover the case of such file systems allocating new blocks to fill holes
also zero out mapped blocks with the new flag.
Signed-off-by: Christoph Hellwig
Currently we don't overwrite the flags field in the iomap in
xfs_bmbt_to_iomap. This works fine with 0-initialized iomaps on stack,
but is harmful once we want to be able to reuse an iomap in the
writeback code. Replace the shared paramter with a set of initial
flags an thus ensures the flags
Don't set IOMAP_F_NEW if we COW over and existing allocated range, as
these aren't strictly new allocations. This is required to be able to
use IOMAP_F_NEW to zero newly allocated blocks, which is required for
the iomap code to fully support file systems that don't do delayed
allocations or use
Lift the xfs code for tracing address space operations to the iomap
layer.
Signed-off-by: Christoph Hellwig
---
fs/iomap/buffered-io.c | 7 +++
include/trace/events/iomap.h | 27 +++
2 files changed, 34 insertions(+)
create mode 100644
Use the new iomap writeback code that was copied from XFS to perform
writeback.
Signed-off-by: Christoph Hellwig
[darrick: reduce this patch only to convert the xfs writeback code]
Signed-off-by: Darrick J. Wong
---
fs/xfs/xfs_aops.c | 667 +
Grandios! http://knrsbwy.Merissa836.xyz/index
___
Bis bald
nik_bin_nek_a...@yahoo.com
Looks good! Thanks for this, Joe.
regards,
dan carpenter
On Mon, Sep 30, 2019 at 04:45:49PM -0700, John Stultz wrote:
> Reverting the following patches:
> "sched/membarrier: Fix p->mm->membarrier_state racy load"
ARGH, I fudged it... please try:
diff --git a/kernel/sched/membarrier.c b/kernel/sched/membarrier.c
index a39bed2c784f..168479a7d61b
Sorry, for not replying. I got sick last week so I was out of office.
Feeling better now.
regards,
dan carpenter
I'm announcing the release of the 5.2.18 kernel.
All users of the 5.2 kernel series must upgrade.
The updated 5.2.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.2.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 32226d81fbb5..440e473687eb 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 2
-SUBLEVEL = 17
+SUBLEVEL = 18
EXTRAVERSION =
NAME = Bobtail Squid
diff --git a/arch/powerpc/include/asm/opal.h
On Mon, Sep 30, 2019 at 06:43:50PM +, Dexuan Cui wrote:
> Lockdep is unhappy if two locks from the same class are held.
>
> Fix the below warning for hyperv and virtio sockets (vmci socket code
> doesn't have the issue) by using lock_sock_nested() when __vsock_release()
> is called
On Tue, 2019-10-01 at 12:58 +0800, Alan Kao wrote:
> On Fri, Sep 27, 2019 at 10:57:45PM +, Atish Patra wrote:
> > On Fri, 2019-09-27 at 15:19 -0700, Christoph Hellwig wrote:
> > > On Thu, Sep 26, 2019 at 05:09:12PM -0700, Atish Patra wrote:
> > > > The Supervisor Binary Interface(SBI)
After 'Initial git repository build' commit,
'mapping_table_ERRHRD' variable has not been used.
So 'mapping_table_ERRHRD' const variable could be removed
to mute below warning message:
fs/cifs/netmisc.c:120:40: warning: unused variable 'mapping_table_ERRHRD'
[-Wunused-const-variable]
Actual changes:
-# CONFIG_BACKLIGHT_CLASS_DEVICE is not set
-CONFIG_CRYPTO_AEGIS128L=m
-CONFIG_CRYPTO_AEGIS256=m
-CONFIG_CRYPTO_MORUS1280=m
-CONFIG_CRYPTO_MORUS640=m
+CONFIG_DM_CLONE=m
+CONFIG_EROFS_FS=m
-# CONFIG_LCD_CLASS_DEVICE is not set
Signed-off-by: Geert
Looks like this changes got lost so resend these changes again.
Below small changes help re-configure or fix missing inter linking
of regulator node.
Re-based on *next-20191001*
Changes from previous patch's series.
Build using Cross Compiler.
Added missing Reviewed-by Neil's and Martin.
Added
As per schematics HDMI_P5V0 is supplied by P5V0 so add missing link.
Cc: Martin Blumenstingl
Cc: Jerome Brunet
Cc: Neil Armstrong
Reviewed-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
Signed-off-by: Anand Moon
---
Changes from previous
Patchv1
- As per Martin's suggestion added the
As per schematics VDDIO_AO18, VDDIO_AO3V3/VDD3V3 DDR3_1V5/DDR_VDDC:
fixed regulator output which is supplied by P5V0.
Cc: Martin Blumenstingl
Cc: Jerome Brunet
Cc: Neil Armstrong
Reviewed-by: Neil Armstrong
Reviewed-by: Martin Blumenstingl
Signed-off-by: Anand Moon
---
Changes from
As per schematics TFLASH_VDD, TF_IO, VCC3V3 fixed regulator output which
is supplied by VDDIO_AO3V3.
While here, move the comment name with the signal name in the
schematics above the gpio property to make it consistent with other
regulators.
Cc: Martin Blumenstingl
Cc: Jerome Brunet
Cc: Neil
On 30.09.19 08:23, Alastair D'Silva wrote:
> From: Alastair D'Silva
>
> On PowerPC, the address ranges allocated to OpenCAPI LPC memory
> are allocated from firmware. These address ranges may be higher
> than what older kernels permit, as we increased the maximum
> permissable address in commit
On 09/30/19 at 05:14am, Eric W. Biederman wrote:
> Baoquan He writes:
> >> needs a little better description. I know it is not a lot on modern
> >> systems but reserving an extra 1M of memory to avoid having to special
> >> case it later seems in need of calling out.
> >>
> >> I have an old
On do, 26 sep 2019 08:50:51 +, Jeroen Hofstee wrote:
> While the state is update when the error counters increase and decrease,
> there is no event when the bus recovers and the error counters decrease
> again. So add that event as well.
>
> Change the state going downward to be ERROR_PASSIVE
Hi Benoit,
On Wed, Sep 25, 2019 at 10:22:59AM -0500, Benoit Parrot wrote:
> Add v4l2 controls to report the pixel rates of each mode. This is
> needed by some CSI2 receiver in order to perform proper DPHY
> configuration.
>
> Signed-off-by: Benoit Parrot
> ---
> drivers/media/i2c/ov5640.c | 25
On Mon, Sep 30, 2019 at 08:29:07PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:014077b5 DO-NOT-SUBMIT: usb-fuzzer: main usb gadget fuzzer..
> git tree: https://github.com/google/kmsan.git master
> console output:
I was investigating a crash in our Virtuozzo7 kernel which happened in
in svcauth_unix_set_client. I found out that we access m_client field
in ip_map structure, which was received from sunrpc_cache_lookup (we
have a bit older kernel, now the code is in sunrpc_cache_add_entry), and
these field
On 10/1/19 1:49 AM, Qian Cai wrote:
>
>
>> On Sep 30, 2019, at 5:43 PM, Vlastimil Babka wrote:
>>
>> Well, my use case is shipping production kernels with CONFIG_PAGE_OWNER
>> and CONFIG_DEBUG_PAGEALLOC enabled, and instructing users to boot-time
>> enable only for troubleshooting a crash or
On Mon, Sep 30, 2019 at 06:52:30PM +0200, Remi Pommarel wrote:
> On Mon, Sep 30, 2019 at 04:40:18PM +0100, Andrew Murray wrote:
> > On Wed, May 22, 2019 at 11:33:51PM +0200, Remi Pommarel wrote:
> > > Aardvark's PCI_EXP_LNKSTA_LT flag in its link status register is not
> > > implemented and does
On 01/10/19 9:27 AM, Martin K. Petersen wrote:
>
> Vignesh,
>
>> This series add DT bindings and driver for TI wrapper for Cadence UFS
>> IP that is present on TI's J721e SoC
>
> Will need some reviews from DT and ufs folks respectively before I can
> queue this up.
>
Ok, thanks for the
Hello,
syzbot found the following crash on:
HEAD commit:54ecb8f7 Linux 5.4-rc1
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14972bf360
kernel config: https://syzkaller.appspot.com/x/.config?x=fb0b431ccdf08c1c
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:afb37288 Add linux-next specific files for 20191001
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1761963560
kernel config: https://syzkaller.appspot.com/x/.config?x=659cb5bf73e72c6c
On Mon, 30 Sep 2019 at 18:24, Dietmar Eggemann wrote:
>
> Hi Vincent,
>
> On 19/09/2019 09:33, Vincent Guittot wrote:
>
> these are just some comments & questions based on a code study. Haven't
> run any tests with it yet.
>
> [...]
>
> > The type of sched_group has been extended to better
On 19/09/2019 09:33, Vincent Guittot wrote:
[...]
> @@ -8042,14 +8104,24 @@ static inline void update_sg_lb_stats(struct lb_env
> *env,
> }
> }
>
> - /* Adjust by relative CPU capacity of the group */
> + /* Check if dst cpu is idle and preferred to this group */
Hi Lee,
> On Mon, 30 Sep 2019, Lukasz Majewski wrote:
>
> > Dear Lee,
> >
> > > This patch set provides several enhancements to mc13xxx MFD family
> > > of devices by introducing mc34708 as a separate device.
> > >
> > > This IC has dedicated pen detection feature, which allows better
> > >
On 10/1/19 9:04 AM, Uwe Kleine-König wrote:
> Hello Fabrice,
>
> On Mon, Sep 30, 2019 at 05:39:11PM +0200, Fabrice Gasnier wrote:
>> Add suspend/resume PM sleep ops. When going to low power, enforce the PWM
>> channel isn't active. Let the PWM consumers disable it during their own
>> suspend
On Mon, Sep 30, 2019 at 03:22:56PM +0800, Like Xu wrote:
> diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
> index 46875bbd0419..74bc5c42b8b5 100644
> --- a/arch/x86/kvm/pmu.c
> +++ b/arch/x86/kvm/pmu.c
> @@ -140,6 +140,35 @@ static void pmc_reprogram_counter(struct kvm_pmc *pmc,
> u32 type,
On Mon, Sep 30, 2019 at 01:36:03PM -0300, Mauro Carvalho Chehab wrote:
> Em Mon, 30 Sep 2019 18:12:01 +0200
> Johan Hovold escreveu:
>
> > A recent change in USB core broke runtime-PM after driver unbind in
> > several drivers (when counting all USB serial drivers). Specifically,
> > drivers
On Tue, 2019-10-01 at 00:02 -0700, Christoph Hellwig wrote:
> On Mon, Sep 30, 2019 at 05:23:18PM -0700, Atish Patra wrote:
> > /proc/cpuinfo should just print all the isa string as an
> > information
> > instead of determining what is supported or not. ELF hwcap can be
> > used by the userspace to
On Mon, Sep 30, 2019 at 03:22:57PM +0800, Like Xu wrote:
> + union {
> + u8 event_count :7; /* the total number of created perf_events */
> + bool enable_cleanup :1;
That's atrocious, don't ever create a bitfield with base _Bool.
> + } state;
Hi Russell,
On Tue, Oct 1, 2019 at 2:50 AM Russell King - ARM Linux admin
wrote:
>
> On Mon, Sep 30, 2019 at 02:59:25PM +0900, Masahiro Yamada wrote:
> > KernelCI reports that bcm2835_defconfig is no longer booting since
> > commit ac7c3e4ff401 ("compiler: enable CONFIG_OPTIMIZE_INLINING
> >
Today the EFI runtime functions are setup in architecture specific
code (x86 and arm), with the functions themselves living in drivers/xen
as they are not architecture dependent.
As the setup is exactly the same for arm and x86 move the setup to
drivers/xen, too. This at once removes the need to
Hi Nick,
On Tue, Oct 1, 2019 at 7:19 AM Nick Desaulniers wrote:
>
> On Sun, Sep 29, 2019 at 11:00 PM Masahiro Yamada
> wrote:
> >
> > KernelCI reports that bcm2835_defconfig is no longer booting since
> > commit ac7c3e4ff401 ("compiler: enable CONFIG_OPTIMIZE_INLINING
> > forcibly"):
> >
> >
There're some Pine64+ boards known to have broken RTL8211E chips, and
a hack is given by Pine64+, which is said to be from Realtek.
This patchset adds the hack.
The hack is taken from U-Boot, and it contains magic numbers without
any document.
Icenowy Zheng (3):
dt-bindings: add binding for
From: Icenowy Zheng
Some RTL8211E Ethernet PHY have an issue that needs a workaround, and a
way to indicate the need of the workaround should be added.
Add the binding for a DT property that indicates this workaround.
Signed-off-by: Icenowy Zheng
---
.../bindings/net/realtek,rtl8211e.yaml
> The allocated memory for new_opts is only released if pare_options fail.
Can the following wording be nicer?
The allocated memory for the buffer “new_opts” will be released
only if a call of the function “parse_options” failed.
> The release for new_opts is added.
* How do you think
Some of the Pine64+ boards are known to use a batch of broken RTL8211E
PHYs. A magic number that is in an undocumented field of a register is
passed from Realtek via Pine64.
Add the property to apply the hack to the Pine64+ device tree.
Signed-off-by: Icenowy Zheng
---
On Tue, Oct 01, 2019 at 06:56:58AM +, Robert Richter wrote:
> It is *not* the counterpart. The __* version already has the...
Lemme cut to the chase:
"Make the main workhorse the "count" functions which can log a @count
of errors. Have the current APIs edac_device_handle_{ce,ue}() call
the
1 - 100 of 1334 matches
Mail list logo
