drivers/block/loop.c:1729:1: warning: the frame size of 1072 bytes is larger than 1024 bytes

Hi Martijn, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 467f8165a2b0e6accf3d0dd9c8089b1dbde29f7f commit: 3448914e8cc550ba792d4ccc74471d1ca4293aae loop: Add LOOP_CONFIGURE ioctl date: 7 months ago config: arm-ra

tools/power/x86/intel-speed-select: Fixes for regression

One side-effect of fixing the scaling frequency limits using the commit eacc9c5a927e ("cpufreq: intel_pstate: Fix intel_pstate_get_hwp_max() for turbo disabled") causes stale HWP_CAP.GUARANTEED to be used as max. Without processing HWP interrupts, user space needs to be able to update a new max whi

[PATCH 1/2] tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency

When BIOS disables turbo, The scaling_max_freq in cpufreq sysfs will be limited to config level 0 base frequency. But when user selects a higher config levels, this will result in higher base frequency. But since scaling_max_freq is still old base frequency, the performance will still be limited. S

[PATCH 2/2] tools/power/x86/intel-speed-select: Set higher of cpuinfo_max_freq or base_frequency

In some case when BIOS disabled turbo, cpufreq cpuinfo_max_freq can be lower than base_frequency at higher config level. So, in that case set scaling_min_freq to base_frequency. Signed-off-by: Srinivas Pandruvada --- tools/power/x86/intel-speed-select/isst-config.c | 11 +++ 1 file chang

Re: [PATCH] mm/userfaultfd: fix memory corruption due to writeprotect

On Sun, Dec 20, 2020 at 09:39:06PM -0800, Nadav Amit wrote: > > On Dec 20, 2020, at 9:25 PM, Nadav Amit wrote: > > > >> On Dec 20, 2020, at 9:12 PM, Yu Zhao wrote: > >> > >> On Sun, Dec 20, 2020 at 08:36:15PM -0800, Nadav Amit wrote: > On Dec 19, 2020, at 6:20 PM, Andrea Arcangeli >

Re: [PATCH] bcache: Trivial fix to bdput

On 12/21/20 11:17 AM, Yi Li wrote: > Trivial fix to bdput. > > Signed-off-by: Yi Li e Hi Yi, Indeed these two fixes are not that trivial. I suggest to describe more detail about why your fixes are necessary and what problems are fixed by your patches. Thanks. Coly Li > --- > drivers/md/bca

Re: [PATCH 9/9] mfd: sec-irq: Do not enforce (incorrect) interrupt trigger type

Hi Krzysztof, On 18.12.2020 15:22, Krzysztof Kozlowski wrote: > On Fri, Dec 18, 2020 at 02:25:39PM +0100, Marek Szyprowski wrote: >> On 10.12.2020 22:29, Krzysztof Kozlowski wrote: >>> Interrupt line can be configured on different hardware in different way, >>> even inverted. Therefore driver sho

Re: [PATCH] dmaengine: qcom: bam_dma: Add LOCK and UNLOCK flag bit support

On 2020-12-19 09:05, Thara Gopinath wrote: On 12/17/20 9:37 AM, Md Sadre Alam wrote: This change will add support for LOCK & UNLOCK flag bit support on CMD descriptor. If DMA_PREP_LOCK flag passed in prep_slave_sg then requester of this transaction wanted to lock the DMA controller for this tra

Re: [RFC PATCH 0/5] iio: move 'modes' initialization to core

On Sat, Dec 5, 2020 at 8:42 PM Jonathan Cameron wrote: > > On Thu, 3 Dec 2020 12:04:18 +0200 > Alexandru Ardelean wrote: > > > I stumbled over this, while trying to implement some changes to the IIO > > buffer logic. > > Seems that most drivers have a INDIO_DIRECT_MODE, and some have > > INDIO_BU

<    1   2   3   4