whoops, you can ignore this actually - I got this mixed up with an Intel issue I
was looking at, this is actually a nouveau issue and you guys don't need to look
at this :)
Kirill-I'll get to this asap, but I've got some other stuff on my plate to go
through first. Could you open up a bug on gitla
On Mon, 2020-11-09 at 13:54 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.9.7 release.
> There are 133 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.
>
From: Zhaoxiu Zeng
This patch does:
1. Cleanup code
2. Use the copy_from_back to copy the matched bytes from the back output buffer
I testd on 5.8.18-300.fc33.x86_64.
The performance of the lzo1x_decompress_safe function is improved by about 5%.
If no CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS featu
From: Sven Van Asbroeck
This driver makes sure the underlying SPI bus is set to "mode 0"
by assigning SPI_MODE_0 to spi->mode. This overwrites all other
SPI mode flags.
In some circumstances, this can break the underlying SPI bus driver.
For example, if SPI_CS_HIGH is set on the SPI bus, the dri
Dear Linux folks,
By mistake I built `XFRM_ESP` into the Linux kernel, resulting in
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
and also the Jitterentropy RNG to be built in.
CRYPTO_JITTERENTROPY=y
So, on the Asus F2A85-M PRO starting Linux 4.10-rc3 with
`initcall_debug`, the
We report a bug (in linux-5.8.13) found by FuzzUSB (a modified version
of syzkaller).
(corrected analysis)
This bug happens while continuing a delayed setup message in mass
storage gadget.
To be specific, composite_setup() sets FSG_STATE_CONFIG_CHANGE via
fsg_set_alt() (line 1793),
and followed by
On Mon, Nov 9, 2020 at 2:22 PM Davidlohr Bueso wrote:
>
> On Sat, 07 Nov 2020, Soheil Hassas Yeganeh wrote:
> >FWIW, I also stress-tested the patch series applied on top of
> >linux-next/master for a couple of hours.
>
> Out of curiosity, what exactly did you use for testing?
That's a good questi
On 11/9/20 7:26 PM, Alexander Lobakin wrote:
> From: Eric Dumazet
> Date: Mon, 9 Nov 2020 18:37:36 +0100
>
>> On 11/9/20 5:56 PM, Alexander Lobakin wrote:
>>> While testing UDP GSO fraglists forwarding through driver that uses
>>> Fast GRO (via napi_gro_frags()), I was observing lots of out-of
From: Zhaoxiu Zeng
This patch does:
1. Cleanup code and reduce branches
2. Use copy_from_back to copy the matched bytes from the back output buffer
I tested on 5.8.18-300.fc33.x86_64.
The performance of function zlib_inflate is improved by about 7%.
If the CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
> From what I see from the docs, this is the only version used
> in MSM8998(silver cores are based on Cortex A53) and it maps
> to r0p4. @Konrad, can you include (rap4 => r0p4) in comment.
Hi,
Thanks for looking into it. Could you perhaps check if it's also the case on
sdm630/636/660?
Konrad
DesignWare core has a TLP digest (TD) override bit in one of the control
registers of ATU. This bit also needs to be programmed for proper ECRC
functionality. This is currently identified as an issue with DesignWare
IP version 4.90a.
Signed-off-by: Vidya Sagar
---
drivers/pci/controller/dwc/pcie
On Mon, Nov 09, 2020 at 08:10:08PM +0100, Michal Suchanek wrote:
> xfs accepts both dax and dax_enum but shows only dax_enum. Show both
> options.
>
> Fixes: 8d6c3446ec23 ("fs/xfs: Make DAX mount option a tri-state")
> Signed-off-by: Michal Suchanek
> ---
> fs/xfs/xfs_super.c | 2 +-
> 1 file ch
On 11/9/20 1:10 PM, Michal Suchanek wrote:
> xfs accepts both dax and dax_enum but shows only dax_enum. Show both
> options.
Should probably indicate why this is needed in the changelog.
> Fixes: 8d6c3446ec23 ("fs/xfs: Make DAX mount option a tri-state")
> Signed-off-by: Michal Suchanek
This se
Hi!
> This is the start of the stable review cycle for the 4.19.156 release.
> There are 71 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 Wed, 11 Nov 2020 12:50:04 +
From: Mike Rapoport
For architectures that enable ARCH_HAS_SET_MEMORY having the ability to
verify that a page is mapped in the kernel direct map can be useful
regardless of hibernation.
Add RISC-V implementation of kernel_page_present(), update its forward
declarations and stubs to be a part of
From: Mike Rapoport
The design of DEBUG_PAGEALLOC presumes that __kernel_map_pages() must never
fail. With this assumption is wouldn't be safe to allow general usage of
this function.
Moreover, some architectures that implement __kernel_map_pages() have this
function guarded by #ifdef DEBUG_PAGE
On Sat, 07 Nov 2020, Soheil Hassas Yeganeh wrote:
FWIW, I also stress-tested the patch series applied on top of
linux-next/master for a couple of hours.
Out of curiosity, what exactly did you use for testing?
Thanks,
Davidlohr
From: Mike Rapoport
When CONFIG_DEBUG_PAGEALLOC is enabled, it unmaps pages from the kernel
direct mapping after free_pages(). The pages than need to be mapped back
before they could be used. Theese mapping operations use
__kernel_map_pages() guarded with with debug_pagealloc_enabled().
The only
From: Mike Rapoport
When DEBUG_PAGEALLOC or ARCH_HAS_SET_DIRECT_MAP is enabled a page may be
not present in the direct map and has to be explicitly mapped before it
could be copied.
Introduce hibernate_map_page() and hibernation_unmap_page() that will
explicitly use set_direct_map_{default,inval
From: Mike Rapoport
Hi,
During recent discussion about KVM protected memory, David raised a concern
about usage of __kernel_map_pages() outside of DEBUG_PAGEALLOC scope [1].
Indeed, for architectures that define CONFIG_ARCH_HAS_SET_DIRECT_MAP it is
possible that __kernel_map_pages() would fail,
In case of an error, call release_mem_region when an error happens
during allocation of resources. Also add error handling for the case
that reset_controller_register fails.
Reported-by: kernel test robot
Reported-by: Dan Carpenter
Signed-off-by: Dinh Nguyen
---
v2: return ret value
---
driver
Everytime I try to start a guest in 5.10 I get something like the
following:
kern.alert: BUG: kernel NULL pointer dereference, address: 00a4
kern.alert: #PF: supervisor read access in kernel mode
kern.alert: #PF: error_code(0x) - not-present page
kern.info: PGD 0 P4D 0
kern.warn:
From: Zhaoxiu Zeng
Copying the matched bytes from the back output buffer is the
key code of the LZ decompression algorithm which used by zlib, lzo, etc.
This patch introduce the optimized copy_from_back function.
The function will be used by later patches in this series.
Optimization for a spec
On Tue, Oct 20, 2020 at 11:37 AM Evan Green wrote:
>
> On Thu, Oct 15, 2020 at 11:28 AM Sibi Sankar wrote:
> >
> > The modem firmware memory requirements vary between 32M/140M on
> > no-lte/lte skus respectively, so fixup the modem memory region
> > to reflect the requirements.
> >
> > Signed-off
Please pull nfsd fixes for 5.10 from
git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.10-1
This is mainly server-to-server copy and fallout from Chuck's 5.10 rpc
refactoring.
--b.
Chuck Lever (3):
NFSD: NFSv3 PATHCONF Reply is improperly formed
SUNRPC: Fix general protection fau
ext4 accepts both dax and dax_always option but shows only dax_always.
Show both options.
Fixes: 9cb20f94afcd ("fs/ext4: Make DAX mount option a tri-state")
Signed-off-by: Michal Suchanek
---
fs/ext4/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/super.c b/fs
On Mon, Nov 9, 2020 at 3:45 PM Tony Lindgren wrote:
> >
> > As discussed on IRC, I think it can still be done in one of these
> > ways, though admittedly none of them are perfect:
> >
> > a) add runtime patching for __my_cpu_offset() when
> > CONFIG_SMP_ON_UP is set. This adds complexity but avo
xfs accepts both dax and dax_enum but shows only dax_enum. Show both
options.
Fixes: 8d6c3446ec23 ("fs/xfs: Make DAX mount option a tri-state")
Signed-off-by: Michal Suchanek
---
fs/xfs/xfs_super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xf
On Thu, Nov 05, 2020 at 03:26:26PM +0800, Alice Guo wrote:
> Add DT Binding doc for the Unique ID of i.MX 8M series.
>
> Signed-off-by: Alice Guo
> ---
> .../devicetree/bindings/arm/fsl.yaml | 33 +++
> 1 file changed, 33 insertions(+)
>
> diff --git a/Documentation/dev
Hello,
after the tristate dax option change some applications fail to detect
pmem devices because the dax option no longer shows in mtab when device
is mounted with -o dax.
At first it might seem stupid to detect pmem by looking at the mount
options.
However, if the application actually wants a
On Mon, Nov 09, 2020 at 12:50:48PM -0500, Lyude Paul wrote:
> Looking at the patches you sent is on my TODO list for this week at least as a
> priority, although I really would have hoped that someone from Intel would
> have looked by now since it's a regression on their end.
What regression are y
On Mon, Nov 9, 2020 at 1:54 PM Eric Dumazet wrote:
>
>
>
> On 11/9/20 7:28 PM, Willem de Bruijn wrote:
> > On Mon, Nov 9, 2020 at 12:37 PM Eric Dumazet wrote:
> >>
> >>
> >>
> >> On 11/9/20 5:56 PM, Alexander Lobakin wrote:
> >>> While testing UDP GSO fraglists forwarding through driver that uses
On Thu, 29 Oct 2020 at 21:35, Aleksandr Nogikh
wrote:
>
> From: Aleksandr Nogikh
>
> Fault injection
> capabilities[Documentation/fault-injection/fault-injection.rst]
> facilitate testing of the stability of the Linux kernel by providing
> means to force a number of kernel interfaces to return e
On Mon, Nov 09, 2020 at 10:53:05AM -0800, Dmitry Torokhov wrote:
> On Mon, Nov 09, 2020 at 07:18:37PM +0100, Lukasz Stelmach wrote:
> > It was <2020-11-09 pon 19:24>, when Andy Shevchenko wrote:
...
> > Probably I have missed something and I will be greatful, if you tell me
> > where I can find m
On 11/8/20 7:18 PM, Punit Agrawal wrote:
Borislav Petkov writes:
On Fri, Nov 06, 2020 at 02:36:46PM +0900, Punit Agrawal wrote:
diff --git a/drivers/firmware/efi/cper-x86.c b/drivers/firmware/efi/cper-x86.c
index 2531de49f56c..438ed9eff6d0 100644
--- a/drivers/firmware/efi/cper-x86.c
+++ b/d
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a004-20201109
i386 randconfig-a006-20201109
i386
On Mon, Nov 09, 2020 at 05:11:21PM +0530, Vinod Koul wrote:
> HI Jonathan,
>
> On 23-09-20, 20:40, Jonathan McDowell wrote:
> > Add the DMA engine driver for the QCOM Application Data Mover (ADM) DMA
> > controller found in the MSM8x60 and IPQ/APQ8064 platforms.
>
> Mostly it looks good, some nit
On Thu, 05 Nov 2020 09:32:41 +0800, xuyuqing wrote:
> Add devicetree bindings for coachz in documentation file
>
> Signed-off-by: xuyuqing
> ---
> .../devicetree/bindings/sound/google,sc7180-trogdor.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring
On 6 Nov 2020, at 13:38, Christoph Hellwig wrote:
You just keep resedning this crap, don't you? Haven't you been told
multiple times to provide a proper kernel API by now?
You do consistently ask for a shim layer, but you haven’t explained
what we gain by diverging from the documented and
On Thu, 05 Nov 2020 02:44:03 +0300, Dmitry Osipenko wrote:
> Document new DVFS OPP table and voltage regulator properties of the
> Tegra EHCI controller.
>
> Signed-off-by: Dmitry Osipenko
> ---
> Documentation/devicetree/bindings/usb/nvidia,tegra20-ehci.txt | 2 ++
> 1 file changed, 2 insertion
On Thu, 05 Nov 2020 02:44:02 +0300, Dmitry Osipenko wrote:
> Document new OPP table and NVIDIA Tegra-specific voltage regulator
> properties.
>
> Signed-off-by: Dmitry Osipenko
> ---
> Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 4
> 1 file changed, 4 insertions(+)
>
Reviewed
On Mon, Nov 09, 2020 at 07:18:37PM +0100, Lukasz Stelmach wrote:
> It was <2020-11-09 pon 19:24>, when Andy Shevchenko wrote:
> > On Mon, Nov 09, 2020 at 06:02:29PM +0100, Lukasz Stelmach wrote:
> >> It was <2019-11-07 czw 20:22>, when Dmitry Torokhov wrote:
...
> >> I am writing a piece that nee
On Thu, 05 Nov 2020 02:44:01 +0300, Dmitry Osipenko wrote:
> Document new DVFS OPP table and voltage regulator properties of the
> video decoder engine.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../devicetree/bindings/media/nvidia,tegra-vde.txt | 12
> 1 file changed, 12 inserti
On Thu, 05 Nov 2020 02:44:00 +0300, Dmitry Osipenko wrote:
> Document new DVFS OPP table and voltage regulator properties of the
> PWM controller.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../devicetree/bindings/pwm/nvidia,tegra20-pwm.txt | 13 +
> 1 file changed, 13 insertions(+)
On Thu, 05 Nov 2020 02:43:59 +0300, Dmitry Osipenko wrote:
> Document new DVFS OPP table and voltage regulator properties of the
> SDHCI controller.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 12
> 1 file changed, 12 insertions(
On Thu, 05 Nov 2020 02:43:58 +0300, Dmitry Osipenko wrote:
> Document new DVFS OPP table and voltage regulator properties of the
> Host1x bus and devices sitting on the bus.
>
> Signed-off-by: Dmitry Osipenko
> ---
> .../display/tegra/nvidia,tegra20-host1x.txt | 56 +++
> 1 fil
Miklos Szeredi writes:
> On Mon, Nov 9, 2020 at 1:48 PM Alexey Gladkov
> wrote:
>>
>> This patch removes one kind of the deadlocks inside the fuse daemon. The
>> problem appear when the fuse daemon itself makes a file operation on its
>> filesystem and receives a fatal signal.
>>
>> This deadlo
On Mon, 9 Nov 2020 11:47:58 -0500 Jarod Wilson wrote:
> On Fri, Nov 6, 2020 at 9:44 PM Jakub Kicinski wrote:
> > On Fri, 6 Nov 2020 15:04:31 -0500 Jarod Wilson wrote:
> > > The bonding driver's use of master and slave, while largely understood
> > > in technical circles, poses a barrier for inc
On 11/9/20 7:28 PM, Willem de Bruijn wrote:
> On Mon, Nov 9, 2020 at 12:37 PM Eric Dumazet wrote:
>>
>>
>>
>> On 11/9/20 5:56 PM, Alexander Lobakin wrote:
>>> While testing UDP GSO fraglists forwarding through driver that uses
>>> Fast GRO (via napi_gro_frags()), I was observing lots of out-of-
On Mon, Nov 09, 2020 at 07:18:37PM +0100, Lukasz Stelmach wrote:
> It was <2020-11-09 pon 19:24>, when Andy Shevchenko wrote:
> > On Mon, Nov 09, 2020 at 06:02:29PM +0100, Lukasz Stelmach wrote:
> >> It was <2019-11-07 czw 20:22>, when Dmitry Torokhov wrote:
> >> > It is possible to store reference
On Sun, Nov 08, 2020 at 10:11:01PM +0800, Muchun Song wrote:
> +static inline int freed_vmemmap_hpage(struct page *page)
> +{
> + return atomic_read(&page->_mapcount) + 1;
> +}
> +
> +static inline int freed_vmemmap_hpage_inc(struct page *page)
> +{
> + return atomic_inc_return_relaxed(&pag
Hi!
> This is the start of the stable review cycle for the 4.4.242 release.
> There are 86 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.
No problems detected by CIP testing:
https://gitlab.com/cip
This short series adds support for the adreno-smmu implementation of the
arm-smmu driver and the device-tree bindings to turn on the implementation
for the sm845 and sc7180 GPUs. These changes are the last ones needed to enable
per-instance pagetables in the drm/msm driver.
v19: Rebase to kernel/g
Every Qcom Adreno GPU has an embedded SMMU for its own use. These
devices depend on unique features such as split pagetables,
different stall/halt requirements and other settings. Identify them
with a compatible string so that they can be identified in the
arm-smmu implementation specific code.
Si
From: Rob Clark
For the Adreno GPU's SMMU, we want SCTLR.HUPCF set to ensure that
pending translations are not terminated on iova fault. Otherwise
a terminated CP read could hang the GPU by returning invalid
command-stream data. Add a hook to for the implementation to modify
the sctlr value if i
Set the qcom,adreno-smmu compatible string for the GPU SMMU to enable
split pagetables and per-instance pagetables for drm/msm.
Signed-off-by: Jordan Crouse
Signed-off-by: Rob Clark
Reviewed-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 9 +
arch/arm64/boot/dts/
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f8394f232b1eab649ce2df5c5f15b0e528c92091
commit: e5fc436f06eef54ef512ea55a9db8eb9f2e76959 sparse: use static inline for
__chk_{user,io}_ptr()
date: 2 months ago
config: arm-randconfig-s031-20201105 (attach
Add a special implementation for the SMMU attached to most Adreno GPU
target triggered from the qcom,adreno-smmu compatible string.
The new Adreno SMMU implementation will enable split pagetables
(TTBR1) for the domain attached to the GPU device (SID 0) and
hard code it context bank 0 so the GPU h
Signed-off-by: Emmanuel Gil Peyrot
---
drivers/staging/media/hantro/hantro_vp8.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/hantro/hantro_vp8.c
b/drivers/staging/media/hantro/hantro_vp8.c
index 0e02d147b189..91ec9a05645b 100644
--- a/drivers/sta
These values will be used by various drivers implementing the VP8
stateless API.
This had been suggested by Ezequiel Garcia for the Cedrus VP8 driver.
Signed-off-by: Emmanuel Gil Peyrot
---
include/media/vp8-ctrls.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/inclu
These values will be used by various drivers implementing the VP8
stateless API.
This had been suggested by Ezequiel Garcia for the Cedrus VP8 driver.
The only driver using this API (until now) has also been updated to use
these new defines.
This is a resend because I forgot to include most main
On 11/6/20 6:09 AM, Borislav Petkov wrote:
On Tue, Nov 03, 2020 at 10:49:52AM -0600, Smita Koralahalli wrote:
diff --git a/arch/x86/kernel/cpu/mce/apei.c b/arch/x86/kernel/cpu/mce/apei.c
index af8d37962586..f56f0bc147e2 100644
--- a/arch/x86/kernel/cpu/mce/apei.c
+++ b/arch/x86/kernel/cpu/mce/a
On Mon, Nov 09, 2020 at 05:28:54PM +0100, Matthieu Baerts wrote:
> Hi Geliang, Dan,
>
> On 09/11/2020 14:59, Geliang Tang wrote:
> > Fix the following Smatch complaint:
>
> Thanks for the report and the patch!
>
> > net/mptcp/pm_netlink.c:213 mptcp_pm_add_timer()
> > warn: variable d
Clang's integrated assembler produces the warning for assembly files:
warning: DWARF2 only supports one section per compilation unit
If -Wa,-gdwarf-* is unspecified, then debug info is not emitted for
assembly sources (it is still emitted for C sources). This will be
re-enabled for newer DWARF v
On Wed, Oct 28, 2020 at 10:09:41PM +, Suzuki K Poulose wrote:
> As per the specification any update to the TRCPRGCTLR must be synchronized
> by a context synchronization event (in our case an explicist ISB) before
> the TRCSTATR is checked.
>
> Cc: Mike Leach
> Cc: Mathieu Poirier
> Signed-o
On Mon, Nov 2, 2020 at 2:25 AM Mansur Alisha Shaik
wrote:
>
> Currently in calculate_inst_freq() video driver is calculating
> macro blocks per frame in steam of macro blocks per second(mpbs).
> Which results frequency is always setting to lower frequency (150MB)
> as per frequency table for sc718
On Mon, Nov 9, 2020 at 12:37 PM Eric Dumazet wrote:
>
>
>
> On 11/9/20 5:56 PM, Alexander Lobakin wrote:
> > While testing UDP GSO fraglists forwarding through driver that uses
> > Fast GRO (via napi_gro_frags()), I was observing lots of out-of-order
> > iperf packets:
> >
> > [ ID] Interval
On Fri, 6 Nov 2020 01:42:39 -0500 menglong8.d...@gmail.com wrote:
> {
> __be16 newlen = htons(skb->len - nhoff);
> struct udphdr *uh = (struct udphdr *)(skb->data + nhoff);
> - int err = -ENOSYS;
> + int err;
> struct sock *sk;
You can also move the err declaration belo
On Wed, Nov 4, 2020 at 10:58 PM Nathan Chancellor
wrote:
>
> On Tue, Nov 03, 2020 at 04:53:41PM -0800, Nick Desaulniers wrote:
> > Clang's integrated assembler produces the warning for assembly files:
> >
> > warning: DWARF2 only supports one section per compilation unit
> >
> > If -Wa,-gdwarf-* i
On Sat, Nov 7, 2020 at 9:49 AM Nick Desaulniers wrote:
>
> Clang is more aggressive about -Wformat warnings when the format flag
> specifies a type smaller than the parameter. It turns out that gsi is an
> int. Fixes:
>
> drivers/acpi/evged.c:105:48: warning: format specifies type 'unsigned
> char
From: Eric Dumazet
Date: Mon, 9 Nov 2020 18:37:36 +0100
> On 11/9/20 5:56 PM, Alexander Lobakin wrote:
>> While testing UDP GSO fraglists forwarding through driver that uses
>> Fast GRO (via napi_gro_frags()), I was observing lots of out-of-order
>> iperf packets:
>>
>> [ ID] Interval T
Hi,
Thanks for the typos corrections. Will be corrected in the next patch
version.
On Sun, Nov 08, 2020 at 08:31:13PM -0800, Randy Dunlap wrote:
>
> So an app could read crash_period_threshold and just do a new fork every
> threshold + 1 time units, right? and not be caught?
Yes, you are right. B
Fixes the following W=1 kernel build warning(s):
drivers/mtd/mtdpart.c:300: warning: Function parameter or member 'mtd' not
described in '__mtd_del_partition'
drivers/mtd/mtdpart.c:300: warning: Excess function parameter 'priv'
description in '__mtd_del_partition'
Cc: Miquel Raynal
Cc: Richa
Fixes the following W=1 kernel build warning(s):
drivers/mtd/spi-nor/controllers/hisi-sfc.c:328: warning: Function parameter or
member 'np' not described in 'hisi_spi_nor_register'
drivers/mtd/spi-nor/controllers/hisi-sfc.c:328: warning: Function parameter or
member 'host' not described in 'hi
Fixes the following W=1 kernel build warning(s):
drivers/mtd/ubi/kapi.c:464: warning: Function parameter or member 'sgl' not
described in 'ubi_leb_read_sg'
drivers/mtd/ubi/kapi.c:464: warning: Excess function parameter 'buf'
description in 'ubi_leb_read_sg'
Cc: Richard Weinberger
Cc: Miquel
On Thu, Nov 5, 2020 at 3:06 AM Maximilian Luz wrote:
>
> Replaces spaces with tabs where spaces have been (inconsistently) used
> for indentation and removes trailing whitespaces.
>
> Signed-off-by: Maximilian Luz
> ---
>
> Was previously: ACPI: Remove trailing whitespace
>
> Changes in v2:
> -
Fixes the following W=1 kernel build warning(s):
drivers/mtd/ubi/build.c:61: warning: Function parameter or member 'ubi_num'
not described in 'mtd_dev_param'
Cc: Richard Weinberger
Cc: Miquel Raynal
Cc: Vignesh Raghavendra
Cc: linux-...@lists.infradead.org
Signed-off-by: Lee Jones
---
driv
Fixes the following W=1 kernel build warning(s):
drivers/mtd/ubi/wl.c:584: warning: Function parameter or member 'nested' not
described in 'schedule_erase'
drivers/mtd/ubi/wl.c:1075: warning: Excess function parameter 'shutdown'
description in '__erase_worker'
Cc: Richard Weinberger
Cc: Miqu
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/spi/toshiba.c:36: warning: Function parameter or member
'write_cache_variants' not described in 'SPINAND_OP_VARIANTS'
drivers/mtd/nand/spi/toshiba.c:36: warning: Function parameter or member '0'
not described in 'SPINAND_OP_VARI
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/omap2.c:191: warning: Function parameter or member 'info'
not described in 'omap_prefetch_enable'
drivers/mtd/nand/raw/omap2.c:221: warning: Function parameter or member 'cs'
not described in 'omap_prefetch_reset'
drivers/m
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/arasan-nand-controller.c:133: warning: Function parameter
or member 'buf' not described in 'anfc_op'
Cc: Naga Sureshkumar Relli
Cc: Miquel Raynal
Cc: Richard Weinberger
Cc: Vignesh Raghavendra
Cc: Choudary Kalluri
Cc: li
Correct 'controller' typo while we're at it.
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/s3c2410.c:172: warning: Function parameter or member
'controller' not described in 's3c2410_nand_info'
drivers/mtd/nand/raw/s3c2410.c:172: warning: Function parameter or member
'
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/cafe_nand.c:372: warning: Function parameter or member
'page' not described in 'cafe_nand_read_page'
drivers/mtd/nand/raw/cafe_nand.c:372: warning: Excess function parameter 'mtd'
description in 'cafe_nand_read_page'
Cc: Mi
'dummy' is never checked (as per the nomenclature) and the use of
'emtpymatch' is currently #if 0'ed out. We could also #if 0 the
declaration, but #ifery is pretty ugly, so I like to keep it to a
minimum.
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/diskonchip.c: In fun
Fixes the following W=1 kernel build warning(s):
drivers/mtd/devices/powernv_flash.c:129: warning: Cannot understand * @mtd:
the device
drivers/mtd/devices/powernv_flash.c:145: warning: Cannot understand * @mtd:
the device
drivers/mtd/devices/powernv_flash.c:161: warning: Cannot understand
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/onenand/onenand_bbt.c:33: warning: Function parameter or
member 'buf' not described in 'check_short_pattern'
drivers/mtd/nand/onenand/onenand_bbt.c:33: warning: Function parameter or
member 'len' not described in 'check_short_pa
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/sunxi_nand.c:250: warning: Function parameter or member
'caps' not described in 'sunxi_nfc'
Cc: Miquel Raynal
Cc: Richard Weinberger
Cc: Vignesh Raghavendra
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Cc: Philipp Zabel
Cc: Boris
Fixes the following W=1 kernel build warning(s):
drivers/mtd/ubi/gluebi.c:446: warning: Function parameter or member 'ns_ptr'
not described in 'gluebi_notify'
drivers/mtd/ubi/gluebi.c:446: warning: Excess function parameter 'ptr'
description in 'gluebi_notify'
Cc: Richard Weinberger
Cc: Miqu
Fixes the following W=1 kernel build warning(s):
drivers/mtd/devices/phram.c:19: warning: Function parameter or member 'fmt'
not described in 'pr_fmt'
Cc: Miquel Raynal
Cc: Richard Weinberger
Cc: Vignesh Raghavendra
Cc: "Jochen Schäuble"
Cc: linux-...@lists.infradead.org
Signed-off-by: Lee
This patch also places the descriptions in the correct order.
Fixes the following W=1 kernel build warning(s):
drivers/mtd/devices/docg3.c:819: warning: bad line:
drivers/mtd/devices/docg3.c:1799: warning: Excess function parameter 'base'
description in 'doc_probe_device'
Cc: Robert Jarzmik
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/brcmnand/brcmnand.c:1854: warning: Function parameter or
member 'host' not described in 'brcmnand_edu_trans'
drivers/mtd/nand/raw/brcmnand/brcmnand.c:1854: warning: Function parameter or
member 'addr' not described in 'brcmn
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/raw/omap_elm.c:102: warning: Function parameter or member
'ecc_steps' not described in 'elm_config'
drivers/mtd/nand/raw/omap_elm.c:102: warning: Function parameter or member
'ecc_step_size' not described in 'elm_config'
driver
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/onenand/onenand_base.c:140: warning: Function parameter or
member 'mtd' not described in 'onenand_ooblayout_32_64_ecc'
drivers/mtd/nand/onenand/onenand_base.c:140: warning: Function parameter or
member 'section' not described in
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
v2 => v3:
- Reworded subject lines
v1 => v2:
- Added tags
- Satisfied Miquel's review comments
Lee Jones (23):
mtd: mtdpart: Fix misdocu
Fixes the following W=1 kernel build warning(s):
drivers/mtd/mtdcore.c:1592: warning: Function parameter or member 'section'
not described in 'mtd_ooblayout_find_eccregion'
drivers/mtd/mtdcore.c:1592: warning: Excess function parameter 'sectionp'
description in 'mtd_ooblayout_find_eccregion'
Fixes the following W=1 kernel build warning(s):
drivers/mtd/nand/onenand/onenand_base.c:140: warning: Function parameter or
member 'mtd' not described in 'onenand_ooblayout_32_64_ecc'
drivers/mtd/nand/onenand/onenand_base.c:140: warning: Function parameter or
member 'section' not described in
Fixes the following W=1 kernel build warning(s):
drivers/mtd/ubi/eba.c:1304: warning: Function parameter or member 'vidb' not
described in 'ubi_eba_copy_leb'
drivers/mtd/ubi/eba.c:1304: warning: Excess function parameter 'vid_hdr'
description in 'ubi_eba_copy_leb'
drivers/mtd/ubi/eba.c:1483:
On Mon, 9 Nov 2020 12:01:56 +0100
Thorsten Leemhuis wrote:
> @Jon: I'd be really appreciate to hear your thoughts on this.
Seems like it's time to post a new version with all of your feedback so
far reflected, and we'll go from there?
Thanks,
jon
+LKML and linux-mm
On Sat, Nov 7, 2020 at 4:38 PM Wei Yang wrote:
>
> Some definitions are left unused, just clean them.
>
> Signed-off-by: Wei Yang
Reviewed-by: Shakeel Butt
Hi!
> commit 7d5553147613b50149238ac1385c60e5c7cacb34 upstream.
>
> As the error capture will compress user buffers as directed to by the
> user, it can take an arbitrary amount of time and space. Break up the
> compression loops with a call to cond_resched(), that will allow other
> processes to
801 - 900 of 2224 matches
Mail list logo
