On Wed, Aug 19, 2020 at 8:50 PM Andy Shevchenko
wrote:
>
> On Wed, Aug 19, 2020 at 8:56 PM Bartosz Golaszewski
> wrote:
> >
> > On Tue, Jul 21, 2020 at 6:05 PM Andy Shevchenko
> > wrote:
> > >
> > > On Tue, Jul 21, 2020 at 5:49 PM Abanoub Sameh
> > > wrote:
> > > >
> > > > Changed 'unsigned' t
On Wed, Aug 19, 2020 at 9:52 AM Frank Wunderlich wrote:
>
> hi,
>
> does the fix you've linked to my revert [1] not work in your case?
>
> [1] https://patchwork.kernel.org/patch/11718481/
Thanks for pointing it out Frank. Also, might want to avoid top
posting in the future.
Enric, Can you please
On Wed, Aug 19, 2020 at 12:40:20PM -0600, Jens Axboe wrote:
> On 8/18/20 6:03 AM, Vaibhav Gupta wrote:
> > On Mon, Aug 17, 2020 at 07:06:03AM -0700, Jens Axboe wrote:
> >> On 8/17/20 2:25 AM, Vaibhav Gupta wrote:
> >>> Hello,
> >>>
> >>> I am working to upgrade power management framework support fo
On 12/08/2020 12:06, Mark Rutland wrote:
> On Thu, Aug 06, 2020 at 12:26:02PM -0500, Madhavan T. Venkataraman wrote:
>> Thanks for the lively discussion. I have tried to answer some of the
>> comments below.
>>
>> On 8/4/20 9:30 AM, Mark Rutland wrote:
>>>
So, the context is - if security se
Wed, Aug 19, 2020 at 06:25:51PM CEST, k...@kernel.org wrote:
>On Wed, 19 Aug 2020 17:18:15 +0200 Jiri Pirko wrote:
> I will add counters on which reload were done. reload_down()/up() can
> return
> which actions were actually done and devlink will show counters.
Why a counter? J
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 18445bf405cb331117bc98427b1ba6f12418ad17
commit: 32a363d0b0b142f35512848dc646ee53e0926723 media: Kconfig files: use
select for V4L2 subdevs and MC
date: 4 months ago
compiler: h8300-linux-gcc (GCC) 9.3.0
Linux Kernel Mentee: Remove Legacy Power Management.
The purpose of this patch series is to upgrade power management in video fbdev
drivers. This has been done by upgrading .suspend() and .resume() callbacks.
The upgrade makes sure that the involvement of PCI Core does not change the
order of ope
Switch to the new generic framework by updating function signatures and
define a "struct dev_pm_ops" variable to bind PM callbacks. This way we can
remove the legacy .suspend & .resume bindings from "gxfb_driver".
The gxfb_suspend() is designed to function only in the case of Suspend.
Thus, the co
Switch to the new generic framework by updating function signatures and
define a "struct dev_pm_ops" variable to bind PM callbacks. This way we can
remove the legacy .suspend & .resume bindings from "lxfb_driver".
The lxfb_suspend() is designed to function only in the case of Suspend.
Thus, the co
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Switch to the new generic framework by updating function signatures and
define a "struct dev_pm_ops" variable to bind PM callbacks. This way we can
remove the legacy .suspend & .resume bindings from "lxfb_driver".
Signed-off-by: Vaibhav Gupta
---
drivers/video/fbdev/cyber2000fb.c | 13 --
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
The AMD eMMC Controller can only use the tuned clock while in HS200 and
HS400 mode. If we switch to a different mode, we need to disable the
tuned clock. If we have previously performed tuning and switch back to
HS200 or HS400, we can re-enable the tuned clock.
Previously the tuned clock was not g
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
Drivers should do only device-specific jobs. But in general, drivers using
legacy PCI PM framework for .suspend()/.resume() have to manage many PCI
PM-related tasks themselves which can be done by PCI Core itself. This
brings extra load on the driver and it directly calls PCI helper functions
to ha
On Wed, Aug 19, 2020 at 01:15:29PM +0100, Mark Brown wrote:
> On Thu, 6 Aug 2020 20:20:18 +0200, Krzysztof Kozlowski wrote:
> > Not all units use the contents of mach/hardware.h and
> > mach/dma.h. Remove these includes when not needed.
>
> Applied to
>
>https://git.kernel.org/pub/scm/linux/
Hi Linus,
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.9-rc2
for you to fetch changes up to aae7a75a821a793ed6b8ad502a5890
Am 19. August 2020 19:12:29 MESZ schrieb Matthias Brugger
:
>Isn't that worth a Fixes tag?
This could be
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fc721b2968e3cadec520c60d2fc63498d865055
(add support for mt2701/mt7623).
It uses existing framework which
From: Christoph Hellwig
Date: Wed, 19 Aug 2020 07:19:45 +0200
> Sending Slab or tail pages into ->sendpage will cause really strange
> delayed oops. Prevent it right in the networking code instead of
> requiring drivers to guess the exact conditions where sendpage works.
>
> Based on a patch fr
On Wed, Aug 19, 2020 at 11:35:11AM -0700, Nick Desaulniers wrote:
> On Wed, Aug 19, 2020 at 7:08 AM Arvind Sankar wrote:
> >
> > gcc can transform the loop in a naive implementation of memset/memcpy
> > etc into a call to the function itself. This optimization is enabled by
> > -ftree-loop-distrib
On Fri, Jul 31, 2020 at 09:41:22AM +0200, Krzysztof Kozlowski wrote:
> Remove unused 'udc' variable to fix compile warnings:
>
> drivers/usb/gadget/udc/s3c2410_udc.c: In function 's3c2410_udc_dequeue':
> drivers/usb/gadget/udc/s3c2410_udc.c:1268:22: warning: variable 'udc' set
> but not u
On Tue, 2020-08-18 at 07:12 +, Christoph Hellwig wrote:
> On Tue, Aug 18, 2020 at 10:59:36AM +0530, Kanchan Joshi wrote:
> > If drive does not support zone-append natively, enable emulation
> > using
> > regular write.
> > Make emulated zone-append cmd write-lock the zone, preventing
> > concur
On Wed, Aug 19, 2020 at 04:01:52PM +0200, Lukasz Stelmach wrote:
> It was <2020-08-19 śro 14:16>, when Mark Brown wrote:
> > On Wed, Aug 19, 2020 at 02:58:22PM +0200, Krzysztof Kozlowski wrote:
> >> On Wed, Aug 19, 2020 at 02:51:27PM +0200, Lukasz Stelmach wrote:
> >> > 0732a9d2a155 spi/s3c64x
If only the dynamic part of procfs is mounted (subset=pid), then there is no
need to check if procfs is fully visible to the user in the new user namespace.
Alexey Gladkov (2):
proc: Relax check of mount visibility
Show /proc/self/net only for CAP_NET_ADMIN
fs/namespace.c | 27 +
Cache the mounters credentials and make access to the net directories
contingent of the permissions of the mounter of proc.
Show /proc/self/net only if mounter has CAP_NET_ADMIN and if proc is
mounted with subset=pid option.
Signed-off-by: Alexey Gladkov
---
fs/proc/proc_net.c | 8
Allow to mount of procfs with subset=pid option even if the entire
procfs is not fully accessible to the user.
Signed-off-by: Alexey Gladkov
---
fs/namespace.c | 27 ---
fs/proc/root.c | 16 +---
include/linux/fs.h | 1 +
3 files changed, 26 insertion
Hi Matthias,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.9-rc1 next-20200819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as doc
On 8/19/20 2:24 AM, Lorenz Bauer wrote:
Don't go via map->ops to call sock_map_update_elem, since we know
what function to call in bpf_map_update_value. Since
check_map_func_compatibility doesn't allow calling
BPF_FUNC_map_update_elem from BPF context, we can remove
ops->map_update_elem and re
On Wed, 19 Aug 2020 10:29:09 -0700
Jesse Brandeburg wrote:
> What I don't understand in the stack trace is this:
> > > [ 107.654661] Call Trace:
> > > [ 107.657735]
> > > [ 107.663155] ? ftrace_graph_caller+0xc0/0xc0
> > > [ 107.667929] call_timer_fn+0x3b/0x1b0
> > > [ 107.672238] ? ne
The issue with using `-fno-builtin-*` flags was that they were not
retained during an LTO link with LLVM. This was fixed in clang-11 by
https://reviews.llvm.org/D71193
(0508c994f0b14144041f2cfd3ba9f9a80f03de08), which is also the minimum
supported version of clang for LTO. Use `-fno-builtin-bcmp`
We're reverting
commit 5f074f3e192f ("lib/string.c: implement a basic bcmp")
in favor of -fno-builtin-bcmp. Remove the additional definition here,
too.
arch/x86/purgatory/Makefile uses -ffreestanding, so there's no risk of
this libcall optimization occurring for arch/x86/boot/purgatory.ro.
arch/x
On Wed, Aug 19, 2020 at 09:02:32PM +0200, Krzysztof Kozlowski wrote:
> Thanks Mark. Could you provide me with a tag/branch with these to pull
> into samsung-soc?
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are availab
-ffreestanding typically inhibits "libcall optimizations" where calls to
certain library functions can be replaced by the compiler in certain
cases to calls to other library functions that may be more efficient.
This can be problematic for embedded targets that don't provide full
libc implementatio
LLVM implemented a recent "libcall optimization" that lowers calls to
`sprintf(dest, "%s", str)` where the return value is used to
`stpcpy(dest, str) - dest`. This generally avoids the machinery involved
in parsing format strings. This optimization was introduced into
clang-12. Because the kernel d
This reverts commit 5f074f3e192f10c9fade898b9b3b8812e3d83342.
An earlier commit in the series prevents the compiler from emitting
calls to bcmp as part of "libcall optimization," and there are no
explicit callers, so we can now safely remove this interface.
Suggested-by: Nathan Chancellor
Review
A recent "libcall optimization" addition to LLVM will emit libcalls to
stpcpy, which the kernel doesn't provide an implementation, breaking
almost all kernel builds with ToT Clang. Disable it for clang.
We discussed providing an implementation, but the interface is generally
unsafe as it provides
On Tue, Aug 18, 2020 at 8:19 PM Anshuman Khandual
wrote:
>
>
>
> On 08/15/2020 03:17 AM, Atish Patra wrote:
> > ARM64 numa implementation is generic enough that RISC-V can reuse that
> > implementation with very minor cosmetic changes. This will help both
> > ARM64 and RISC-V in terms of maintanac
The ADC is used by twl4030_charger to read voltages. If a dtb contains
the ADC but the module is not build, probing twl4030_charger will be
endlessly deferred, so just enable CONFIG_TWL4030_MADC in the config.
Signed-off-by: Andreas Kemnade
---
arch/arm/configs/omap2plus_defconfig | 1 +
1 file
Hallo
configuring kernel 5.8.x on Fedora 32 via "make xconfig" gives me this:
HOSTCXX scripts/kconfig/qconf.o
scripts/kconfig/qconf.cc: In member function ‘void
ConfigInfoView::clicked(const QUrl&)’:
scripts/kconfig/qconf.cc:1231:3: error: ‘qInfo’ was not declared in this
scope; did you mean ‘
On Wed, Aug 19, 2020 at 07:48:43PM +0100, Matthew Wilcox (Oracle) wrote:
> Provide this functionality from the swap cache. It's useful for
> more than just mincore().
The build bot showed I was missing this for some configs:
diff --git a/mm/swap_state.c b/mm/swap_state.c
index 986b4e3d3bad..92a1
Hi Suzuki,
On Tue, Aug 18, 2020 at 08:29:31PM +0100, Suzuki K Poulose wrote:
> If the specified/hinted sink is not reachable from a subset of the CPUs,
> we could end up unable to trace the event on those CPUs. This
> is the best effort we could do until we support 1:1 configurations.
> Fail grace
I'm now able to reproduce this, looking into it. (The crash looks
actually similar to what was also happening with the next commit,
drm/ttm: make TT creation purely optional v3, but that got reverted
already.)
Roland
Am 19.08.20 um 09:47 schrieb 허종만:
>
> Hi,
>
>
> I'm running Linux guest OS (
On Wed, 19 Aug 2020 07:59:23 -0500
Adam Ford wrote:
> The bandgap sensor can be idled when the processor is too, but it
> isn't currently being done, so the power consumption of OMAP3
> boards can elevated if the bangap sensor is enabled.
>
> This patch attempts to use some additional power mana
On Tue, 18 Aug 2020 18:16:26 +0300 Mike Rapoport wrote:
> From: Mike Rapoport
>
> The only user of memblock_dbg() outside memblock was s390 setup code and it
> is converted to use pr_debug() instead.
> This allows to stop exposing memblock_debug and memblock_dbg() to the rest
> of the kernel.
>
On 8/19/20 12:11 PM, David Fugate wrote:
> On Tue, 2020-08-18 at 07:12 +, Christoph Hellwig wrote:
>> On Tue, Aug 18, 2020 at 10:59:36AM +0530, Kanchan Joshi wrote:
>>> If drive does not support zone-append natively, enable emulation
>>> using
>>> regular write.
>>> Make emulated zone-append cm
On Wed, 19 Aug 2020 at 11:30, Will Deacon wrote:
>
> On Wed, Aug 19, 2020 at 11:01:38AM -0600, Mathieu Poirier wrote:
> > On Tue, 18 Aug 2020 at 11:56, John Garry wrote:
> > > On 17/08/2020 20:31, Mathieu Poirier wrote:
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > index 4e2698cc7e23..f9
On Wed, Aug 19, 2020 at 11:42 AM wrote:
>
> On Wed, Aug 19, 2020 at 10:53:58AM -0700, Kyle Huey wrote:
> > rr, a userspace record and replay debugger[0], has a test suite that
> > attempts to exercise strange corners of the Linux API. One such
> > test[1] began failing after 2bbc68f8373c0631ebf137
On Wed, Aug 19, 2020 at 12:16:53PM -0700, Nick Desaulniers wrote:
> We're reverting
> commit 5f074f3e192f ("lib/string.c: implement a basic bcmp")
> in favor of -fno-builtin-bcmp. Remove the additional definition here,
> too.
>
> arch/x86/purgatory/Makefile uses -ffreestanding, so there's no risk
Removeing BUG/BUG_ON from androind/ion and add error handle to calling
functions
Tomer Samara (2):
staging: android: Remove BUG_ON from ion_page_pool.c
staging: android: Remove BUG from ion_system_heap.c
drivers/staging/android/ion/ion_page_pool.c | 14 ++
drivers/staging/andro
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
Signed-off-by: Adam Ford
diff --git a/arch/arm/boot/d
On Tue, 11 Aug 2020 10:02:36 +0800 wrote:
> From: Abel Wu
>
> The commit below is incomplete, as it didn't handle the add_full() part.
> commit a4d3f8916c65 ("slub: remove useless kmem_cache_debug() before
> remove_full()")
>
> This patch checks for SLAB_STORE_USER instead of kmem_cache_debug
Hi penghao,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sound/for-next]
[also build test ERROR on v5.9-rc1 next-20200819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Wed, Aug 19, 2020 at 03:01:21PM +0200, Lukasz Stelmach wrote:
> It was <2020-08-19 śro 14:39>, when Krzysztof Kozlowski wrote:
> > There is here no commit msg, no explanation.
> As I wrote in the cover letter, this and previous commits make things
> work on Exynos3250 (ARTIK5 precisely). I can
Remove BUG/BUG_ONs from androind/ion allocator and add error handling to
calling functions
Tomer Samara (2):
staging: android: Remove BUG_ON from ion_page_pool.c
staging: android: Remove BUG from ion_system_heap.c
drivers/staging/android/ion/ion_page_pool.c | 14 ++
drivers/sta
BUG_ON() is removed at ion_page_pool.c and add error handleing to
ion_page_pool_shrink
Fixes the following issue:
Avoid crashing the kernel - try using WARN_ON & recovery code ratherthan BUG()
or BUG_ON().
Signed-off-by: Tomer Samara
---
drivers/staging/android/ion/ion_page_pool.c | 14 +++
Remove BUG() at ion_sytem_heap.c and error handling to:
- free_buffer_page
- alloc_buffer_page
this fix the following checkpatch issue:
Avoid crashing the kernel - try using WARN_ON &
recovery code ratherthan BUG() or BUG_ON().
Signed-off-by: Tomer Samara
---
drivers/staging/android/ion/ion_s
On Wed, Aug 19, 2020 at 11:42:27PM +0800, Tzung-Bi Shih wrote:
> But I found struct mfd_cell also contains member .of_compatible. What
> is the difference if we use compatible string (as is) for this device
> instead of falling back to use device name to match?
That's for binding the MFD subdevi
On Wed, Aug 19, 2020 at 11:50:55AM -0700, Linus Torvalds wrote:
> On Wed, Aug 19, 2020 at 12:22 AM wrote:
> >
> > That is, the external serialization comes from the non-atomic
> > test-and-set they both have. This works nicely when there is external
> > state that already serializes things, but to
On 7/9/20 8:48 PM, Florian Fainelli wrote:
> The Broadcom BDC driver did not have a MAINTAINERS entry which made it
> escape review from Al and myself, add an entry so the relevant mailing
> lists and people are copied.
>
> Signed-off-by: Florian Fainelli
Can the USB host or gadget maintainers t
Hi Adam,
On Wed, Aug 19, 2020 at 4:36 PM Adam Ford wrote:
> &hdmi {
> ddc-i2c-bus = <&i2c3>;
> - status = "okay";
> + status = "disabled";
Looks like an unrelated change.
During a context switch the scheduler invokes wq_worker_sleeping() with
disabled preemption. Disabling preemption is needed because it protects
access to `worker->sleeping'. As an optimisation it avoids invoking
schedule() within the schedule path as part of possible wake up (thus
preempt_enable_no
On Wed, Aug 19 2020 at 10:14, Kyle Huey wrote:
> tl;dr: after 27d6b4d14f5c3ab21c4aef87dd04055a2d7adf14 ptracer
> modifications to orig_ax in a syscall entry trace stop are not honored
> and this breaks our code.
My fault and I have no idead why none of the silly test cases
noticed. Fix below.
Tha
On Wed, Aug 19, 2020 at 12:51:27AM +, Peng Fan wrote:
> > Subject: Re: [PATCH 04/10] remoteproc: imx_rproc: make syscon optional
> >
> > Hi Peng,
> >
> > On Fri, Jul 24, 2020 at 04:08:07PM +0800, Peng Fan wrote:
> > > Make syscon optional, since i.MX8QM/QXP/7ULP not have SRC to control
> > M4
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
---
V2: Don't change HDMI
Signed-off-by: Adam Ford
d
Konrad Rzeszutek Wilk writes:
> On Tue, Aug 18, 2020 at 07:11:26PM -0300, Thiago Jung Bauermann wrote:
>> POWER secure guests (i.e., guests which use the Protection Execution
>> Facility) need to use SWIOTLB to be able to do I/O with the hypervisor, but
>> they don't need the SWIOTLB memory to
Hi penghao,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sound/for-next]
[also build test ERROR on v5.9-rc1 next-20200819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Sat, Aug 15, 2020 at 12:26:58PM +0200, Lukas Bulwahn wrote:
> Since commit 53b7f3aa411b ("Add a maintainer entry profile for
> documentation"), the documentation "subsystem" has a maintainer entry
> profile, and it deserves to be mentioned in MAINTAINERS with a suitable
> P: entry.
>
> Signed-o
On Thu, Aug 06, 2020 at 08:20:40PM +0200, Krzysztof Kozlowski wrote:
> From: Arnd Bergmann
>
> The fiq handler needs access to some register definitions that
> should not be used directly by device drivers.
>
> Since this is closely related to the irqchip driver anyway,
> move it into the same p
On Wed, Aug 19, 2020 at 8:31 AM Laurent Pinchart
wrote:
> On Wed, Aug 19, 2020 at 05:21:20PM +0200, Sam Ravnborg wrote:
> > On Wed, Aug 19, 2020 at 01:45:28PM +0200, Mauro Carvalho Chehab wrote:
> > > This patch series port the out-of-tree driver for Hikey 970 (which
> > > should also support Hike
On Fri, Aug 14, 2020 at 05:40:25PM -0700, Stephen Boyd wrote:
> These patches make debug_obj_descr into a const pointer. The second
> patch can be split up into many patches if desired and sent to
> respective susbsytem maintainers.
>
> Stephen Boyd (2):
> debugobjects: Allow debug_obj_descr to
Hi Adam,
On Wed, Aug 19, 2020 at 4:48 PM Adam Ford wrote:
>
> The DTC doesn't like the default PWM settings, because it's expecting
> three cells. This patch reduces adds the extra entry of 0 to the PWM
> reference.
>
> Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
From: Miaohe Lin
Date: Wed, 19 Aug 2020 04:32:08 -0400
> We've been warning about SO_BSDCOMPAT usage for many years. We may remove
> this code completely now.
>
> Suggested-by: David S. Miller
> Signed-off-by: Miaohe Lin
Applied to net-next, thank you.
The bits PF_IO_WORKER and PF_WQ_WORKER are tested together in
sched_submit_work() which is considered to be a hot path.
If the two bits cross the 8 or 16 bit boundary then most architecture
require multiple load instructions in order to create the constant
value. Also, such a value can not be encod
SWP_FS doesn't mean the device is file-backed swap device,
which just means each writeback request should go through fs
by DIO. Or it'll just use extents added by .swap_activate(),
but it also works as file-backed swap device.
So in order to achieve the goal of the original patch,
SWP_BLKDEV shoul
The DTC doesn't like the default PWM settings, because it's expecting
three cells. This patch reduces adds the extra entry of 0 to the PWM
reference.
Fixes: fa28d8212ede ("ARM: dts: imx: default to #pwm-cells = <3> in the SoC
dtsi files")
Reviewed-by: Fabio Estevam
Signed-off-by: Adam Ford
-
sched_submit_work() is considered to be a hot path. The preempt_disable()
instruction is a compiler barrier and forces the compiler to load
task_struct::flags for the second comparison.
By using a local variable, the compiler can load the value once and keep it in
a register for the second comparis
On Wed, 5 Aug 2020, Palmer Dabbelt wrote:
> > I can push linux-next through regression-testing with RISC-V gdbserver
> > and/or native GDB if that would help. This is also used with core dumps,
> > but honestly I don't know what state RISC-V support is in in the BFD/GDB's
> > core dump interpret
From: Christian Brauner
Date: Wed, 19 Aug 2020 12:46:50 +0200
> The old _do_fork() helper is removed in favor of the new kernel_clone()
> helper.
> The latter adheres to naming conventions for kernel internal syscall helpers.
>
> Cc: "David S. Miller"
> Cc: sparcli...@vger.kernel.org
> Signed-
On Thu, 20 Aug 2020 03:56:13 +0800 Gao Xiang wrote:
> SWP_FS doesn't mean the device is file-backed swap device,
> which just means each writeback request should go through fs
> by DIO. Or it'll just use extents added by .swap_activate(),
> but it also works as file-backed swap device.
This is v
Lorenz Bauer wrote:
> Initializing psock->sk_proto and other saved callbacks is only
> done in sk_psock_update_proto, after sk_psock_init has returned.
> The logic for this is difficult to follow, and needlessly complex.
>
> Instead, initialize psock->sk_proto whenever we allocate a new
> psock. A
Hi,
On Thu, Aug 6, 2020 at 9:31 AM Georgi Djakov wrote:
>
> Increase the number of interconnect-cells, as now we can include
> the tag information. The consumers can specify the path tag as an
> additional argument to the endpoints.
>
> Tested-by: Sibi Sankar
> Reviewed-by: Sibi Sankar
> Review
On 8/19/20 12:19 PM, Ronald Warsow wrote:
> Hallo
>
> configuring kernel 5.8.x on Fedora 32 via "make xconfig" gives me this:
>
>
> HOSTCXX scripts/kconfig/qconf.o
> scripts/kconfig/qconf.cc: In member function ‘void
> ConfigInfoView::clicked(const QUrl&)’:
> scripts/kconfig/qconf.cc:1231:3: er
On Tue, Aug 18, 2020 at 4:49 PM kernel test robot wrote:
>
> Hi Darren,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on iio/togreg]
> [also build test WARNING on linux/master linus/master v5.9-rc1 next-20200818]
> [If your patch is applied to the wrong gi
On 20-08-17 15:51:13, Dong Aisheng wrote:
> On Fri, Aug 14, 2020 at 8:13 PM Abel Vesa wrote:
> >
> > The hdmi BLK_CTRL ids have been moved to imx8mp-reset.h
> >
> > Signed-off-by: Abel Vesa
>
> The change seems do not comply with the patch title?
>
Will fix it in the next version.
> Regards
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 18445bf405cb331117bc98427b1ba6f12418ad17
commit: af84b16e3423bd9c1c8d81c44bc0a217f763f6b7 openrisc: uaccess: Use static
inline function in access_ok
date: 11 days ago
config: openrisc-randconfig-r022-20200
Lorenz Bauer wrote:
> Merge the two very similar functions sock_map_update_elem and
> sock_hash_update_elem into one.
>
> Signed-off-by: Lorenz Bauer
> ---
> net/core/sock_map.c | 53 -
> 1 file changed, 9 insertions(+), 44 deletions(-)
>
Fixup the w
On Wed, Aug 19, 2020 at 12:29 PM Arvind Sankar wrote:
>
> On Wed, Aug 19, 2020 at 12:16:53PM -0700, Nick Desaulniers wrote:
> > We're reverting
> > commit 5f074f3e192f ("lib/string.c: implement a basic bcmp")
> > in favor of -fno-builtin-bcmp. Remove the additional definition here,
> > too.
> >
>
On Wed, Aug 19, 2020 at 10:00:25PM +0200, Sebastian Andrzej Siewior wrote:
> sched_submit_work() is considered to be a hot path. The preempt_disable()
> instruction is a compiler barrier and forces the compiler to load
> task_struct::flags for the second comparison.
> By using a local variable, the
On Mon, 10 Aug 2020 07:20:56 +0800 Wei Yang
wrote:
> __vma_unlink_common() and __vma_unlink() are counterparts. Since there is
I assume you meant "__vma_link()" here?
> not function named __vma_unlink(), let's rename it to __vma_unlink() to
> make the code more self-explain and easy for audien
On 8/19/20 2:24 AM, Lorenz Bauer wrote:
The verifier assumes that map values are simple blobs of memory, and
therefore treats ARG_PTR_TO_MAP_VALUE, etc. as such. However, there are
map types where this isn't true. For example, sockmap and sockhash store
sockets. In general this isn't a big pro
Hi Andrew,
On Wed, Aug 19, 2020 at 01:05:06PM -0700, Andrew Morton wrote:
> On Thu, 20 Aug 2020 03:56:13 +0800 Gao Xiang wrote:
>
> > SWP_FS doesn't mean the device is file-backed swap device,
> > which just means each writeback request should go through fs
> > by DIO. Or it'll just use extents
On Sun, Aug 16, 2020 at 02:33:41AM +0200, Joan Bruguera wrote:
> Any feedback?
Hi!
I just happened to see this email. I think this should likely be
directed to the crypto (which also handled compress/decompress APIs)
list and the original author...
Additional notes below...
> - Joan
>
> On 05.
5/gem: Async GPU relocations only")
>
> seems to at least build.
>
> Pavel, does doing those three reverts make things work for you?
Ok, so Chris' patches resulted in (less severe?) crash, let me try this.
pavel@amd:/data/l/linux-next-32$ git reset --hard
8eb858df0a5f6bcd371
(cc Thomas and linux-mm)
On Sat, 8 Aug 2020 13:50:30 +0400 kpark3...@gmail.com wrote:
> From: Sahara
>
> Slab cache flags are exported to sysfs and are allowed to get modified
> from userspace. Some of those may call calculate_sizes function because
> the changed flag can take an effect on s
The call for candidates to serve on the Linux Foundation Technical
Advisory board for the next two years ends after this weekend. If you
would like an opportunity to represent the community to the LF, now is the
time to send in your nomination. Details below; we're looking forward to
hearing from
1 - 100 of 1576 matches
Mail list logo
