Hi!
> This is the start of the stable review cycle for the 4.19.143 release.
> There are 125 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 03 Sep 2020 15:09:01
Hi Markus,
Thanks for your comments.
No real fix, as normally , we should return a negative code,
In function h8300_8timer_init(), it set ' ret = -EINVAL ', ' ret = ENXIO' , it
should be align with a negative code
static int __init h8300_8timer_init(struct device_node *node)
{
ret =
On Sat, Aug 29, 2020 at 02:00:16PM +0100, Valentin Schneider wrote:
> In the absence of ACPI or DT topology data, we fallback to haphazardly
> decoding *something* out of MPIDR. Sadly, the contents of that register are
> mostly unusable due to the implementation leniancy and things like Aff0
>
My Dear in the lord
My name is Mrs. Mina A. Brunel I am a Norway Citizen who is living in Burkina
Faso, I am married to Mr. Brunel Patrice, a politician who owns a small gold
company in Burkina Faso; He died of Leprosy and Radesyge, in the year February
2010, During his lifetime he
On Tue, Sep 01, 2020 at 05:31:00PM +0200, Krzysztof Kozlowski wrote:
> Common pattern of handling deferred probe can be simplified with
> dev_err_probe(). Less code and the error value gets printed.
>
> Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Lukas Wunner
On Sun, Aug 30, 2020 at 07:31:39AM -0500, Eric W. Biederman wrote:
> pet...@infradead.org writes:
> > Could we check privs twice instead?
> >
> > Something like the completely untested below..
>
> That might work.
>
> I am thinking that for cases where we want to do significant work it
> might
Hi Kaaira, Dafna,
On 28/08/2020 21:37, Dafna Hirschfeld wrote:
> Hi,
>
> Am 21.08.20 um 23:01 schrieb Kaaira Gupta:
>> Hi,
>>
>> On Fri, Aug 21, 2020 at 05:11:23PM +0200, Dafna Hirschfeld wrote:
>>>
>>>
>>> Am 19.08.20 um 20:04 schrieb Kaaira Gupta:
Separate the process of initialising
On Thu, Aug 27, 2020 at 10:55:28PM +0300, Andrey Lebedev wrote:
> Hello,
>
> I think I'm experiencing problem with pwm-sun4i module. I'll describe
> the symptoms first.
>
> I have a device, based on Allwinner A20 (Cubieboard 2) with LVDS display
> that has a PWM-based backlight. The problem is:
On 8/28/20 6:47 PM, Pavel Tatashin wrote:
> There appears to be another problem that is related to the
> cgroup_mutex -> mem_hotplug_lock deadlock described above.
>
> In the original deadlock that I described, the workaround is to
> replace crash dump from piping to Linux traditional save to
On Wed, Sep 02, 2020 at 10:38:39AM +0100, Mark Brown wrote:
> On Wed, Sep 02, 2020 at 11:10:38AM +0200, Krzysztof Kozlowski wrote:
> > On Tue, Sep 01, 2020 at 12:03:49PM +0100, Mark Brown wrote:
>
> > > Please submit patches using subject lines reflecting the style for the
> > > subsystem, this
On Wed, Sep 02, 2020 at 05:17:43PM +0800, Hanjun Guo wrote:
> +Cc Will
>
> On 2020/8/18 17:16, Hanjun Guo wrote:
> > On 2020/8/18 14:36, Zenghui Yu wrote:
> > > * From v1 [1]:
> > > - As pointed out by Hanjun, remove two now unused inline functions.
> > > Compile tested with
Excerpts from Michael Ellerman's message of September 1, 2020 10:00 pm:
> Nicholas Piggin writes:
>> Commit 0cef77c7798a7 ("powerpc/64s/radix: flush remote CPUs out of
>> single-threaded mm_cpumask") added a mechanism to trim the mm_cpumask of
>> a process under certain conditions. One of the
Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with
multiple mode and integrated waveform memory and wideband support.
It communicates via an I2C bus to the device.
Reviewed-by: Jes Sorensen .
Signed-off-by: Roy Im
---
v19:
- Corrected some errors and replaced some code to
This patch adds support for the Dialog DA7280 Haptic driver IC.
In this patch set the following is provided:
[PATCH v19 1/3] MAINTAINERS file update for DA7280
[PATCH v19 2/3] DA7280 DT Binding
[PATCH v19 3/3] DA7280 Driver
This patch applies against linux-next and v5.8
Thank you,
Roy Im,
Add device tree binding information for DA7280 haptic driver.
Example bindings for DA7280 are added.
Reviewed-by: Rob Herring .
Signed-off-by: Roy Im
---
v19: No changes.
v18: No changes.
v17: No changes.
v16: No changes.
v15: No changes.
v14: No changes.
v13: No changes.
v12: No changes.
v11:
This patch adds the da7280 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Roy Im
---
v19: No changes.
v18: No changes.
v17: No changes.
v16: No changes.
v15: No changes.
v14: No changes.
v13: No changes.
v12: Corrected file list order.
v11: No changes.
v10: No
On Wed, Sep 02, 2020 at 10:35:08AM +0900, Masami Hiramatsu wrote:
> On Tue, 18 Aug 2020 15:57:43 +0200
> Peter Zijlstra wrote:
>
> > Similar to how we disallow kprobes on any other dynamic text
> > (ftrace/jump_label) also disallow kprobes on inline static_call()s.
>
> Looks good to me.
>
>
Tue, Sep 01, 2020 at 09:43:00PM CEST, mo...@nvidia.com wrote:
>
>On 8/31/2020 3:15 PM, Jiri Pirko wrote:
>> Sun, Aug 30, 2020 at 05:27:21PM CEST, mo...@mellanox.com wrote:
>> > Add devlink reload action to allow the user to request a specific reload
>> > action. The action parameter is optional,
The important bit of this patchset is patch#1, which is a fix to take off
HWPoison pages off a buddy freelist since it can lead to us having HWPoison
pages back in the game and no one noticing it is handling a HWPoison page.
So fix it (we did that already for soft_offline_page [1]).
The other
The crux of the matter is that historically we left poisoned pages
in the buddy system because we have some checks in place when
allocating a page that a gatekeeper for poisoned pages.
Unfortunately, we do have other users (e.g: compaction [1]) that scan
buddy freelists and try to get a page from
memory_failure and soft_offline_path paths now drain pcplists by calling
get_hwpoison_page.
memory_failure flags the page as HWPoison before, so that page cannot longer
go into a pcplist, and soft_offline_page only flags a page as HWPoison
if 1) we took the page off a buddy freelist 2) the page
Make a proper if-else condition for {hard,soft}-offline.
Signed-off-by: Oscar Salvador
---
mm/madvise.c | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff --git a/mm/madvise.c b/mm/madvise.c
index e32e7efbba0f..e92e06890b08 100644
--- a/mm/madvise.c
+++
A page with 0-refcount and !PageBuddy could perfectly be a pcppage.
Currently, we bail out with an error if we encounter such a page,
meaning that we do not handle pcppages neither from hard-offline
nor from soft-offline path.
Fix this by draining pcplists whenever we find this kind of page
and
On Wed, Sep 02, 2020 at 08:00:24AM +0200, Juri Lelli wrote:
> On 31/08/20 13:07, Lucas Stach wrote:
> > When a boosted task gets throttled, what normally happens is that it's
> > immediately enqueued again with ENQUEUE_REPLENISH, which replenishes the
> > runtime and clears the dl_throttled flag.
The bugs fixed in this patchset have been present since the following commits:
patch #1: Fixes: 00e57a6d4ad3 ("net-next/hinic: Add Tx operation")
patch #2: Fixes: 5e126e7c4e52 ("hinic: add firmware update support")
patch #3: Fixes: 2eed5a8b614b ("hinic: add set_channels ethtool_ops support")
Luo
Firmware erases the entire flash region which may take several
seconds before flashing, so we bump up the timeout to ensure this
cmd won't return failure.
Fixes: 5e126e7c4e52 ("hinic: add firmware update support")
Signed-off-by: Luo bin
---
drivers/net/ethernet/huawei/hinic/hinic_hw_mgmt.c | 4
We free memory regardless of the return value of SET_FUNC_STATE
cmd in hinic_close function to avoid memory leak and this cmd may
timeout when fw is busy with handling other cmds, so we bump up the
timeout of this cmd to ensure it won't return failure.
Fixes: 00e57a6d4ad3 ("net-next/hinic: Add Tx
When calling hinic_close in hinic_set_channels, netif_carrier_off
and netif_tx_disable are excuted, and TX host resources are freed
after that. Core may call hinic_xmit_frame to send pkt after
netif_tx_disable within a short time, so we should judge whether
carrier is on before sending pkt
+++ Qu Wenruo [02/09/20 14:46 +0800]:
When kernel module loading failed, user space only get one of the
following error messages:
- ENOEXEC
This is the most confusing one. From corrupted ELF header to bad
WRITE|EXEC flags check introduced by in module_enforce_rwx_sections()
all returns this
On Wed, Sep 02, 2020 at 11:10:38AM +0200, Krzysztof Kozlowski wrote:
> On Tue, Sep 01, 2020 at 12:03:49PM +0100, Mark Brown wrote:
> > Please submit patches using subject lines reflecting the style for the
> > subsystem, this makes it easier for people to identify relevant patches.
> The usual
On Wed, Sep 2, 2020 at 1:11 AM Arnaldo Carvalho de Melo
wrote:
>
> Hi Tzvetomir,
>
> I noticed this:
>
> 27 debian:experimental-x-mips: Ok mips-linux-gnu-gcc (Debian
> 8.3.0-19) 8.3.0
> 29 debian:experimental-x-mipsel : Ok mipsel-linux-gnu-gcc (Debian
> 9.2.1-8) 9.2.1
any comment?
Thanks,
Yang
On 2020/8/24 11:11, Yang Shen wrote:
This patchset make some clean up:
patch 1:remove useless parameters
patch 4:replace 'sprintf' with 'scnprintf'
patch 7:fix static check warning
and the rest patch fix some coding style
Resend this patch series because it depends
On Wed, Sep 02, 2020 at 05:17:55PM +0900, Masami Hiramatsu wrote:
> > Ok, but then lockdep will yell at you if you have that enabled and run
> > the unoptimized things.
>
> Oh, does it warn for all spinlock things in kprobes if it is unoptimized?
> Hmm, it has to be noted in the documentation.
On 01. 09. 20, 14:01, Artem Savkov wrote:
> b6da31b2c07c "tty: Fix data race in tty_insert_flip_string_fixed_flag"
> puts tty_flip_buffer_push under port->lock introducing the following
> possible circular locking dependency:
>
> [30129.876566]
Hi all,
I have sent a patch which reverts cddae808aeb7 ("block: pass a
hd_struct to delete_partition") to syzbot, and it is now pending for
testing:
Link: https://groups.google.com/g/syzkaller-bugs/c/fnk0t9aqhDw/m/FO46-S8XAgAJ
Thank you,
Peilin Ye
Hi,
it could be a silly question, but better to ask...
> + if (regs)
> + start_backtrace(, regs->regs[29], regs->pc);
> + else
> + start_backtrace(, thread_saved_fp(task),
> + thread_saved_pc(task));
Would this also work for task ==
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: Tuesday, September 01, 2020 8:06 PM
> To: 吳昊澄 Ricky
> Cc: a...@arndb.de; gre...@linuxfoundation.org; ulf.hans...@linaro.org;
> bhelg...@google.com; rui_f...@realsil.com.cn; vailbhavgupt...@gamail.com;
>
On Tue, Aug 18, 2020 at 02:36:23PM +0800, Zenghui Yu wrote:
> * From v1 [1]:
> - As pointed out by Hanjun, remove two now unused inline functions.
> Compile tested with CONFIG_IOMMU_API is not selected.
>
> [1] https://lore.kernel.org/r/20200817105946.1511-1-yuzeng...@huawei.com
>
>
On Wed, Sep 2, 2020 at 12:12 PM Hennerich, Michael
wrote:
> > From: Andy Shevchenko
> > Sent: Mittwoch, 2. September 2020 10:52
> > On Wed, Sep 2, 2020 at 11:09 AM Hennerich, Michael
> > wrote:
...
> > I see. Can we consider this email as the official answer from AD that this
> > ID is
> >
On 2/09/20 5:12 am, Martin K. Petersen wrote:
>
> Adrian,
>
>> Intel host controllers support the setting of latency tolerance.
>> Accordingly, implement the PM QoS ->set_latency_tolerance() callback. The
>> raw register values are also exposed via debugfs.
>
> Does not apply to
On Wed, 19 Aug 2020, Mark Brown wrote:
> As with the generic arch_stack_walk() code the arm64 stack walk code takes
> a callback that is called per stack frame. Currently the arm64 code always
> passes a struct stackframe to the callback and the generic code just passes
> the pc, however none of
On Wed, 19 Aug 2020, Mark Brown wrote:
> Currently the callback passed to arch_stack_walk() has an argument called
> reliable passed to it to indicate if the stack entry is reliable, a comment
> says that this is used by some printk() consumers. However in the current
> kernel none of the
On 9/2/20 1:14 AM, Yunsheng Lin wrote:
> On 2020/9/2 15:32, Eric Dumazet wrote:
>>
>>
>> On 9/1/20 11:34 PM, Yunsheng Lin wrote:
>>
>>>
>>> I am not familiar with TCQ_F_CAN_BYPASS.
>>> From my understanding, the problem is that there is no order between
>>> qdisc enqueuing and qdisc reset.
>>
Document SoC specific compatible strings for r8a7742. No driver change
is needed as the fallback strings will activate the right code.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
Reviewed-by: Geert Uytterhoeven
---
v1->v2
* Reabsed the patch on top YAML conversion
*
+Cc Will
On 2020/8/18 17:16, Hanjun Guo wrote:
On 2020/8/18 14:36, Zenghui Yu wrote:
* From v1 [1]:
- As pointed out by Hanjun, remove two now unused inline functions.
Compile tested with CONFIG_IOMMU_API is not selected.
[1]
When adding allwinner,sun8i-a33-crypto, I forgot to add that it needs reset.
Furthermore, there are no need to use items to list only one compatible
in compatible list.
Fixes: f81547ba7a98 ("dt-bindings: crypto: add new compatible for A33 SS")
Signed-off-by: Corentin Labbe
---
On Wed, Sep 02, 2020 at 11:09:35AM +0200, pet...@infradead.org wrote:
> On Tue, Sep 01, 2020 at 09:21:37PM -0700, Guenter Roeck wrote:
> > [0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:4875
> > check_flags.part.39+0x280/0x2a0
> > [0.00]
> -Original Message-
> From: Andy Shevchenko
> Sent: Mittwoch, 2. September 2020 10:52
> To: Hennerich, Michael
> Cc: AceLan Kao ; Ardelean, Alexandru
> ; William Sung
> ; Lars-Peter Clausen ;
> Jonathan Cameron ; Hartmut Knaack ;
> Peter Meerwald-Stadler ; linux-iio
Dear Friend,
How are you I hope you are very fine with your entire family? If so glory be to
Almighty God.
I'm happy to inform you about my success in getting those funds transferred
under the cooperation of a new partner from GREECE, Presently i'm in GREECE
for a better treatment and
On Tue, Sep 01, 2020 at 07:40:16PM -0600, Tycho Andersen wrote:
> In seccomp_set_mode_filter() with TSYNC | NEW_LISTENER, we first initialize
> the listener fd, then check to see if we can actually use it later in
> seccomp_may_assign_mode(), which can fail if anyone else in our thread
> group has
On Tue, Sep 01, 2020 at 09:21:37PM -0700, Guenter Roeck wrote:
> [0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:4875
> check_flags.part.39+0x280/0x2a0
> [0.00] DEBUG_LOCKS_WARN_ON(lockdep_hardirqs_enabled())
> [0.00] [<004cff18>]
On Tue, Sep 01, 2020 at 12:03:49PM +0100, Mark Brown wrote:
> On Sun, Aug 30, 2020 at 01:26:32PM +0200, Krzysztof Kozlowski wrote:
> > The "sound-dai" property has cells therefore phandle-array should be
> > used, even if it is just one phandle. This fixes dtbs_check warnings
> > like:
>
>
On Tuesday, September 1, 2020 3:26 PM, Daniel Vetter wrote:
> On Tue, Sep 01, 2020 at 08:57:37AM +, Simon Ser wrote:
>
> > On Monday, August 31, 2020 3:48 PM, Ville Syrjälä
> > ville.syrj...@linux.intel.com wrote:
> >
> > > > > It doesn't seem like this IGT test's goal is to exercise
register_mem_sect_under_nodem() is checking the memory block's node id only
if the system state is "SYSTEM_BOOTING". On PowerPC, the memory blocks are
registered while the system state is "SYSTEM_SCHEDULING", the one before
SYSTEM_RUNNING.
The consequence on PowerPC guest with interleaved memory
On Tue, 1 Sep 2020 at 10:50, Matthias Schiffer
wrote:
>
> As with GPIO, UART and others, allow specifying the device index via the
> aliases node in the device tree.
>
> On embedded devices, there is often a combination of removable (e.g.
> SD card) and non-removable MMC devices (e.g. eMMC).
>
On Sat, 29 Aug 2020 at 08:25, Krzysztof Kozlowski wrote:
>
> The i.MX 8 DTSes use two compatibles so update the binding to fix
> dtbs_check warnings like:
>
> arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml: mmc@30b4:
> compatible: ['fsl,imx8mn-usdhc', 'fsl,imx7d-usdhc'] is too long
>
On Tue, 1 Sep 2020 at 10:50, Matthias Schiffer
wrote:
>
> As for I2C and SPI, it now is possible to reserve a fixed index for
> mmc/mmcblk devices.
>
> Signed-off-by: Matthias Schiffer
Applied for next, thanks!
Kind regards
Uffe
> ---
>
> v4: moved alias documentation from example to
On Mon, 31 Aug 2020 at 12:23, Wolfram Sang
wrote:
>
> Signed-off-by: Wolfram Sang
Applied for next, thanks!
Kind regards
Uffe
> ---
>
> Only buildtested. Found while analyzing retune-handling in the core.
>
> drivers/mmc/host/meson-gx-mmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Mon, 31 Aug 2020 at 18:11, Krzysztof Kozlowski wrote:
>
> There might be multiple reset GPIOs but dtschema has trouble parsing it
> if there are no maxItems:
>
> arch/arm/boot/dts/exynos5250-snow.dt.yaml: mmc3_pwrseq: reset-gpios: [[20,
> 2, 1], [20, 1, 1]] is too long
> From schema:
On Thu, 27 Aug 2020 at 11:33, Chun-Hung Wu wrote:
>
> This series provides MediaTek cqhci implementations as below:
> - Add cqhci_host_ops->pre_enable() and cqhci_host_ops->post_disable()
> - Implement MediaTek's hook functions
>
> Chun-Hung Wu (2):
> mmc: cqhci: add new cqhci_host_ops
On Thu, 27 Aug 2020 at 16:59, Douglas Anderson wrote:
>
> As the comments in this patch say, if we tune and find all phases are
> valid it's _almost_ as bad as no phases being found valid. Probably
> all phases are not really reliable but we didn't detect where the
> unreliable place is. That
On Mon, Aug 24, 2020 at 07:44:21PM -0400, Tong Zhang wrote:
> ocrdma_qp_state_change() returns 1 when new and old state are the same,
> however caller is checking using <0
>
> Signed-off-by: Tong Zhang
> ---
> drivers/infiniband/hw/ocrdma/ocrdma_verbs.c | 2 +-
> 1 file changed, 1 insertion(+),
On Mon, 31 Aug 2020 at 23:10, Raul E Rangel wrote:
>
> commit 61d7437ed1390 ("mmc: sdhci-acpi: Fix HS400 tuning for AMDI0040")
> broke resume for HS400. When the system suspends the eMMC controller is
> powered down. So on resume we need to reinitialize the controller.
> amd_sdhci_host was not
Hello Denis,
Quoting Denis Efremov (2020-08-27 08:43:59)
> Use kfree_sensitive() instead of open-coding it.
>
> Signed-off-by: Denis Efremov
Acked-by: Antoine Tenart
Thanks!
Antoine
> ---
> drivers/crypto/inside-secure/safexcel_hash.c | 3 +--
> 1 file changed, 1 insertion(+), 2
Peter Xu writes:
> On Tue, Sep 01, 2020 at 04:43:25PM +0200, Vitaly Kuznetsov wrote:
>> Peter Xu writes:
>>
>> > On Fri, Aug 07, 2020 at 04:12:29PM +0200, Vitaly Kuznetsov wrote:
>> >> When testing Linux kernel boot with QEMU q35 VM and direct kernel boot
>> >> I observed 8193 accesses to PCI
On Wed, Sep 02, 2020 at 11:43:56AM +0300, Andy Shevchenko wrote:
> On Wed, Sep 02, 2020 at 09:17:47AM +1200, Evan Nimmo wrote:
> > If something goes wrong (such as the SCL being stuck low) then we need
> > to reset the PCA chip. The issue with this is that on reset we lose all
> > config settings
On Wed, Sep 02, 2020 at 09:22:53AM +1000, Benjamin Herrenschmidt wrote:
> On Tue, 2020-09-01 at 13:37 -0500, Bjorn Helgaas wrote:
> > On Mon, Aug 31, 2020 at 03:18:27PM +, Clint Sbisa wrote:
> > > Using write-combine is crucial for performance of PCI devices where
> > > significant amounts of
On Wed, Sep 02, 2020 at 09:17:47AM +1200, Evan Nimmo wrote:
> If something goes wrong (such as the SCL being stuck low) then we need
> to reset the PCA chip. The issue with this is that on reset we lose all
> config settings and the chip ends up in a disabled state which results
> in a lock
On Tue, Sep 01, 2020 at 08:51:46PM -0700, Guenter Roeck wrote:
> [ 27.056457] include/trace/events/lock.h:13 suspicious
> rcu_dereference_check() usage!
> [ 27.057006] Hardware name: Generic OMAP3-GP (Flattened Device Tree)
> [ 27.057098] [] (unwind_backtrace) from []
>
From: Leon Romanovsky
The kernel with KASAN and GCOV enabled generates the following splat
due to the situation that gcov_info can be both user and kernel pointer.
It is triggered by the memcpy() inside kmemdup(), so as a possible solution
let's copy fields manually.
From: Leon Romanovsky
Hi Linus,
Both Colin in Ubuntu [1] and I in FC 32 are having same kernel crashes
while GCOV is enabled. The reason to it that n_fuction variable that
should be provided by GCC is not initialized (or wrongly set).
This patch is based on the RFC [2] which I sent to gather
From: Leon Romanovsky
The filename is a const pointer, so use the proper string duplication
routine that takes into account const identifier.
Cc: Colin Ian King
Signed-off-by: Leon Romanovsky
---
kernel/gcov/gcc_4_7.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Leon Romanovsky
The kernel compiled with GCC 10.2.1 and KASAN together with GCOV enabled
produces the following splat while reloading modules. The very similar
trace was reported by Colin [1].
[ cut here ]
WARNING: CPU: 0 PID: 296 at mm/page_alloc.c:4859
From: Leon Romanovsky
Once GCOV fails to duplicate information, the following error is
printed:
gcov: could not save data for
'/home/leonro/src/kernel/drivers/infiniband/hw/mlx5/std_types.gcda' (out of
memory)
In the event of out-of-memory such prints are seen for almost every kernel
file,
On Wed, Sep 2, 2020 at 11:09 AM Hennerich, Michael
wrote:
> > From: Andy Shevchenko
> > Sent: Montag, 31. August 2020 14:46
> > On Mon, Aug 31, 2020 at 2:28 PM AceLan Kao
> > wrote:
...
> > P.S. Jonathan, it seems this driver has artificial ACPI HID. We probably
> > have to
> > remove it.
On Wed, Sep 02, 2020 at 07:53:02AM +0200, Michal Hocko wrote:
> On Tue 01-09-20 18:25:58, Suren Baghdasaryan wrote:
> > Currently __set_oom_adj loops through all processes in the system to
> > keep oom_score_adj and oom_score_adj_min in sync between processes
> > sharing their mm. This is done for
This will improve this driver's build coverage.
Reported-by: Ezequiel Garcia
Signed-off-by: Alexandre Courbot
---
Hi Ohad, Bjorn,
As explained in
https://www.spinics.net/lists/linux-media/msg175991.html, we need this
patch in order to merge a driver series in the media tree. If that looks
ok
On Wed, Sep 02, 2020 at 01:34:59AM +, linmiaohe wrote:
> Christian Brauner wrote:
> >On Tue, Sep 01, 2020 at 06:39:05PM +0200, Oleg Nesterov wrote:
> >> On 09/01, Christian Brauner wrote:
> >> >
> >> > On Tue, Sep 01, 2020 at 07:58:00AM -0400, Miaohe Lin wrote:
> >> > > No functional change
If usb-role-switch is present in the device tree, it means that ID and Vbus
signals are not connected to the OTG controller but to an external
component (GPIOs, Type-C controller). In this configuration, usb role
switch is used to force valid sessions on STM32MP15 SoCs.
Acked-by: Martin
This patch documents the usb-role-switch property in dwc2 bindings, now
that usb-role-switch support is available in dwc2 driver.
Reviewed-by: Martin Blumenstingl
Acked-by: Rob Herring
Signed-off-by: Amelie Delaunay
---
Documentation/devicetree/bindings/usb/dwc2.yaml | 4
1 file changed,
This patch adds support for usb role switch to dwc2, by using overriding
control of the PHY voltage valid and ID input signals.
iddig signal (ID) can be overridden:
- when setting GUSBCFG_FORCEHOSTMODE, iddig input pin is overridden with 1;
- when setting GUSBCFG_FORCEDEVMODE, iddig input pin is
When using usb-c connector (but it can also be the case with a micro-b
connector), iddig, avalid, bvalid, vbusvalid input signals may not be
connected to the DWC2 OTG controller.
DWC2 OTG controller features an overriding control of the PHY voltage valid
and ID input signals.
So, missing signals
Rakesh Pillai writes:
> Board Data File (BDF) is loaded upon driver boot-up procedure.
> The right board data file is identified using bus and qmi-board-id.
>
> The problem, however, can occur when the (default) board data
> file cannot fulfill with the vendor requirements and it is
> necessary
Currently, there is an assumption that the performance domains as provided
by the SCMI protocol should be mirroring the exact implementation in
hardware, for example, the clock domains, which are a typical type of
performance domains.
By design, an SCMI performance domain defines the granularity
Hi Pavel,
Maybe I miss something, but it seems that in 4.19 vpif_probe() ignores
error codes from vpif_probe_complete() and returns 0 even if it fails.
That was fixed by commit 64f883cd98c6, but it was not backported to 4.19.
In addition, this commit contains a fix of one more bug.
Regarding
On Tue, Sep 01, 2020 at 07:40:17PM -0600, Tycho Andersen wrote:
> I've changed my e-mail address to tycho.pizza, so let's reflect that in
> these files.
>
> Signed-off-by: Tycho Andersen
> ---
> .mailmap| 1 +
> MAINTAINERS | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff
Hello Joel,
On Wed, Sep 02, 2020 at 01:08:35AM +, Joel Stanley wrote:
> On Tue, 1 Sep 2020 at 14:09, Gautham R. Shenoy
> wrote:
> >
> > From: "Gautham R. Shenoy"
> >
> > commit d947fb4c965c ("cpuidle: pseries: Fixup exit latency for
> > CEDE(0)") sets the exit latency of CEDE(0) based on
Hi,
On 2020/9/2 2:05, George Cherian wrote:
Hi Yang,
-Original Message-
From: Yang Yingliang
Sent: Tuesday, September 1, 2020 6:59 PM
To: George Cherian ; linux-kernel@vger.kernel.org;
linux-a...@vger.kernel.org; linux-...@vger.kernel.org
Cc: kbuild-...@lists.01.org;
On Tue, 1 Sep 2020 at 17:40, Christoph Hellwig wrote:
>
> On Tue, Sep 01, 2020 at 05:36:17PM +0200, Ulf Hansson wrote:
> > > I still don't think this makes sense, as the dma_mask should always
> > > be non-NULL here.
> >
> > If that is the case, I wonder how the driver could even have worked
On Tue, Sep 01 2020 at 17:09, Andy Lutomirski wrote:
> On Tue, Sep 1, 2020 at 4:50 PM Thomas Gleixner wrote:
>> > I think that they almost work for x86, but not quite as
>> > indicated by this bug. Even if we imagine we can somehow hack around
>> > this bug, I imagine we're going to find other
On Wed, 2 Sep 2020, Boqun Feng wrote:
> When PAGE_SIZE > HV_HYP_PAGE_SIZE, we need the ringbuffer size to be at
> least 2 * PAGE_SIZE: one page for the header and at least one page of
> the data part (because of the alignment requirement for double mapping).
>
> So make sure the ringbuffer sizes
On Wed, 2 Sep 2020 09:02:26 +0200
pet...@infradead.org wrote:
> On Wed, Sep 02, 2020 at 09:37:39AM +0900, Masami Hiramatsu wrote:
> > On Tue, 1 Sep 2020 21:08:08 +0200
> > Peter Zijlstra wrote:
> >
> > > On Sat, Aug 29, 2020 at 09:59:49PM +0900, Masami Hiramatsu wrote:
> > > > Masami Hiramatsu
Hi Jiri,
On 9/2/2020 4:09 AM, Jiri Olsa wrote:
On Tue, Sep 01, 2020 at 10:26:25AM +0800, Jin, Yao wrote:
Hi Jiri,
On 8/31/2020 9:56 PM, Jiri Olsa wrote:
On Tue, Aug 25, 2020 at 07:35:07AM +0800, Jin Yao wrote:
SNIP
+ int nr_streams_max,
+
On 9/2/20 1:41 PM, Christophe Leroy wrote:
Le 02/09/2020 à 05:23, Aneesh Kumar K.V a écrit :
Christophe Leroy writes:
The following random segfault is observed from time to time with
map_hugetlb selftest:
root@localhost:~# ./map_hugetlb 1 19
524288 kB hugepages
Mapping 1 Mbytes
From: Leon Romanovsky
Continue with allocation patches.
Leon Romanovsky (2):
RDMA: Clean MW allocation and free flows
RDMA: Convert RWQ table logic to ib_core allocation scheme
drivers/infiniband/core/device.c| 2 +
drivers/infiniband/core/uverbs_cmd.c| 45
On 2020/9/2 15:32, Eric Dumazet wrote:
>
>
> On 9/1/20 11:34 PM, Yunsheng Lin wrote:
>
>>
>> I am not familiar with TCQ_F_CAN_BYPASS.
>> From my understanding, the problem is that there is no order between
>> qdisc enqueuing and qdisc reset.
>
> Thw qdisc_reset() should be done after rcu grace
On 9/2/20 12:16 AM, Nicolin Chen wrote:
> These two patches are to update default segment_boundary_mask.
>
> PATCH-1 fixes overflow issues in callers of dma_get_seg_boundary.
> Previous version was a series: https://lkml.org/lkml/2020/8/31/1026
>
> Then PATCH-2 sets default
On 9/1/20 17:21, Lukasz Stelmach wrote:
It was <2020-08-25 wto 21:06>, when Sylwester Nawrocki wrote:
On 8/21/20 18:13, Łukasz Stelmach wrote:
Check return values in prepare_dma() and s3c64xx_spi_config() and
propagate errors upwards.
Signed-off-by: Łukasz Stelmach
---
From: Leon Romanovsky
>From Jason:
The RDMA CMA continues to attract syzkaller bugs due to its somewhat loose
operation of its FSM. Audit and scrub the whole thing to follow modern
expectations.
Overall the design elements are broadly:
- The ULP entry points MUST NOT run in parallel with each
Le 02/09/2020 à 05:23, Aneesh Kumar K.V a écrit :
Christophe Leroy writes:
The following random segfault is observed from time to time with
map_hugetlb selftest:
root@localhost:~# ./map_hugetlb 1 19
524288 kB hugepages
Mapping 1 Mbytes
Segmentation fault
[ 31.219972] map_hugetlb[365]:
1101 - 1200 of 1333 matches
Mail list logo
