defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a004-20210330
x86_64
On Tue, 30 Mar 2021 09:17:19 -0500
David Lechner wrote:
> On 3/30/21 3:08 AM, Carlis wrote:
> > From: Xuezhi Zhang
> >
> > This adds a new module for the ST7789V controller with parameters
> > for the Waveshare 2inch LCD module.
> >
> > Signed-off-by: Xuezhi Zhang
> > ---
> > v2:change compat
This patch supports the HPB 2.0.
The HPB 2.0 supports read of varying sizes from 4KB to 512KB.
In the case of Read (<= 32KB) is supported as single HPB read.
In the case of Read (36KB ~ 512KB) is supported by as a combination of
write buffer command and HPB read command to deliver more PPN.
The wr
This patch changes the read I/O to the HPB read I/O.
If the logical address of the read I/O belongs to active sub-region, the
HPB driver modifies the read I/O command to HPB read. It modifies the UPIU
command of UFS instead of modifying the existing SCSI command.
In the HPB version 1.0, the maxim
This is a patch for managing L2P map in HPB module.
The HPB divides logical addresses into several regions. A region consists
of several sub-regions. The sub-region is a basic unit where L2P mapping is
managed. The driver loads L2P mapping data of each sub-region. The loaded
sub-region is called a
This is a patch for the HPB initialization and adds HPB function calls to
UFS core driver.
NAND flash-based storage devices, including UFS, have mechanisms to
translate logical addresses of IO requests to the corresponding physical
addresses of the flash storage.
In UFS, Logical-address-to-Physica
Changelog:
v31 -> v32
Delete unused parameter of unmap API.
v30 -> v31
Delete unnecessary debug message.
v29 -> v30
1. Add support to reuse bio of pre-request.
2. Delete unreached code in the ufshpb_issue_map_req.
v28 -> v29
1. Remove unused variable that reported by kernel test robot.
v27 ->
From: Pierre-Louis Bossart
If a device lost sync and can no longer ACK a command, it may not be
able to enter a lower-power state but it will still be able to resync
when the clock restarts. In those cases, we want to continue with the
clock stop sequence.
This patch modifies the behavior when -
From: Pierre-Louis Bossart
We sometimes discard -ENODATA when reporting errors and lose all
traces of issues in the console log, add a macro to add use dev_dbg()
in such cases.
Signed-off-by: Pierre-Louis Bossart
Reviewed-by: Rander Wang
Reviewed-by: Guennadi Liakhovetski
Signed-off-by: Bard
If a device lost sync and can no longer ACK a command, it may not be
able to enter a lower-power state but it will still be able to resync
when the clock restarts. In those cases, we want to continue with the
clock stop sequence.
This patch modifies the behavior when -ENODATA is received, with the
Broadcast device is switched to oneshot mode in
tick_switch_to_oneshot() -> tick_broadcast_switch_to_oneshot().
If build broadcast clock event device driver as module, and
install it after system enters oneshot mode, then it will
stay in periodic mode forever.
This patch allows such broadcast dev
On Mon, 15 Mar 2021 03:34:36 +0530, Bhaskar Chowdhury wrote:
> Trivial spelling fixes throughout the file.
Applied to powerpc/next.
[1/1] powerpc: kernel: Trivial spelling fixes throughout the file
head_fsl_booke.S
https://git.kernel.org/powerpc/c/f239873fcd953557ba9a9781d10ca95c0594e2b3
On Mon, 15 Mar 2021 15:24:56 +0800, Yang Li wrote:
> fixed the following coccicheck:
> ./arch/powerpc/sysdev/xive/spapr.c:552:8-9: WARNING: return of 0/1 in
> function 'xive_spapr_match' with return type bool
Applied to powerpc/next.
[1/1] powerpc/xive: use true and false for bool variable
On Wed, 24 Feb 2021 13:25:47 +0530, Bhaskar Chowdhury wrote:
> s/droping/dropping/
Applied to powerpc/next.
[1/1] arch: powerpc: kernel: Change droping to dropping in the file traps.c
https://git.kernel.org/powerpc/c/5c4a4802b9ac8c1acdf2250fad3f8f2d6254f9c7
cheers
On Mon, 22 Mar 2021 08:03:07 +0530, Bhaskar Chowdhury wrote:
> s/filesytem/filesystem/
> s/symantics/semantics/
Applied to powerpc/next.
[1/1] cxl: Fix couple of spellings
https://git.kernel.org/powerpc/c/e23ecdf9fd87c547a3ac55bcebaf7df28df2fab0
cheers
On Fri, 12 Mar 2021 16:55:37 +0530, Bhaskar Chowdhury wrote:
> s/detalis/details/
Applied to powerpc/next.
[1/1] powerpc: mm: book3s64: Fix a typo in the file mmu_context.c
https://git.kernel.org/powerpc/c/7a7d744ffe87ae10ab98004d1a6ca1f691af58e1
cheers
On Fri, 26 Mar 2021 16:03:55 +0100 Borislav Petkov wrote:
> On Fri, Mar 19, 2021 at 08:22:21PM +1300, Kai Huang wrote:
> > From: Sean Christopherson
> >
> > Add a misc device /dev/sgx_vepc to allow userspace to allocate "raw" EPC
> > without an associated enclave. The intended and only known use
On Tue, 2 Mar 2021 13:08:29 -0700, Nathan Chancellor wrote:
> If identical_pvr_fixup() is not inlined, there are two modpost warnings:
>
> WARNING: modpost: vmlinux.o(.text+0x54e8): Section mismatch in reference
> from the function identical_pvr_fixup() to the function
> .init.text:of_get_flat_dt_
On Wed, 17 Mar 2021 14:34:13 +0530, Bhaskar Chowdhury wrote:
> s/procesing/processing/
Applied to powerpc/next.
[1/1] powerpc: kernel: Trivial typo fix in the file kgdb.c
https://git.kernel.org/powerpc/c/89f7d2927ae16ea470d29234447763826e40c6cf
cheers
On Thu, 11 Mar 2021 14:45:38 +0530, Ravi Bangoria wrote:
> As per ISA 3.1, prefixed instruction should not cross 64-byte
> boundary. So don't allow Uprobe on such prefixed instruction.
>
> There are two ways probed instruction is changed in mapped pages.
> First, when Uprobe is activated, it searc
On Thu, 25 Mar 2021 13:08:20 -0700, Randy Dunlap wrote:
> Drop the 'beginning of kernel-doc' notation markers (/**)
> in places that are not in kernel-doc format.
Applied to powerpc/next.
[1/1] selftests: powerpc: unmark non-kernel-doc comments
https://git.kernel.org/powerpc/c/dfc4ae3372182
On Tue, 2 Mar 2021 12:50:14 -0700, Nathan Chancellor wrote:
> If fadump_calculate_reserve_size() is not inlined, there is a modpost
> warning:
>
> WARNING: modpost: vmlinux.o(.text+0x5196c): Section mismatch in
> reference from the function fadump_calculate_reserve_size() to the
> function .init.t
On Wed, 3 Mar 2021 19:13:18 -0800, menglong8.d...@gmail.com wrote:
> Some typos are found out.The information at the end of the file
> does not match the beginning.
Applied to powerpc/next.
[1/1] arch/powerpc/include:fix misspellings in tlbflush.h
https://git.kernel.org/powerpc/c/1a029e0edb
On Fri, 19 Mar 2021 07:44:41 +0800, kernel test robot wrote:
> arch/powerpc/kernel/iommu.c:76:2-16: WARNING: NULL check before some freeing
> functions is not needed.
>
> NULL check before some freeing functions is not needed.
>
> Based on checkpatch warning
> "kfree(NULL) is safe this check
On Wed, 10 Mar 2021 18:44:05 +0100, Laurent Dufour wrote:
> It is better to rely on the API provided by the MM layer instead of
> directly manipulating the mm_users field.
Applied to powerpc/next.
[1/1] cxl: don't manipulate the mm.mm_users field directly
https://git.kernel.org/powerpc/c/2d
On Fri, 5 Mar 2021 13:55:54 +0100, Laurent Dufour wrote:
> This is helpful to read the security flavor from inside the LPAR.
>
> In /sys/kernel/debug/powerpc/security_features it can be seen if
> mitigations are on or off but the level set through the ASMI menu.
> Furthermore, reporting it through
On Mon, 15 Mar 2021 15:35:24 +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warning:
>
> ./arch/powerpc/platforms/maple/pci.c:37:16-17: WARNING comparing pointer
> to 0.
Applied to powerpc/next.
[1/1] powerpc/pci: fix warning comparing pointer to 0
https://git.kernel.org/powerp
On Wed, 3 Mar 2021 12:46:03 +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/tty/hvc/hvc_vio.c:385:13: warning: no previous prototype for
> ‘hvc_vio_init_early’ [-Wmissing-prototypes]
> 385 | void __init hvc_vio_init_early(void)
> | ^~
App
On Tue, 23 Feb 2021 10:53:45 +0100, Geert Uytterhoeven wrote:
> Commit 407d418f2fd4c20a ("powerpc/chrp: Move PHB discovery") moved the
> sole call to hydra_init() to the source file where it is defined, so it
> can be made static.
Applied to powerpc/next.
[1/1] powerpc/chrp: Make hydra_init() sta
On Wed, 24 Feb 2021 15:29:21 +0800, Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./arch/powerpc/kernel/prom_init.c:2986:2-3: Unneeded semicolon.
Applied to powerpc/next.
[1/1] powerpc: remove unneeded semicolon
https://git.kernel.org/powerpc/c/4f46d57cab3b3410411b395a6
On Tue, 16 Mar 2021 00:11:48 -0400, He Ying wrote:
> warning: symbol 'rfi_flush' was not declared.
> warning: symbol 'entry_flush' was not declared.
> warning: symbol 'uaccess_flush' was not declared.
> We found warnings above in arch/powerpc/kernel/setup_64.c by using
> sparse tool.
>
> Define 'e
On Fri, 5 Mar 2021 14:28:07 +0300, Denis Efremov wrote:
> "offsetof(struct pt_regs, msr) == offsetof(struct user_pt_regs, msr)"
> checked in pt_regs_check() twice in a row. Remove the second check.
Applied to powerpc/next.
[1/1] powerpc/ptrace: Remove duplicate check from pt_regs_check()
ht
On Fri, 26 Mar 2021 19:53:56 +0800, dingsen...@163.com wrote:
> Remove unneeded variable: "rc".
Applied to powerpc/next.
[1/1] powerpc: powernv: Remove unneeded variable: "rc"
https://git.kernel.org/powerpc/c/69931cc387cca289e0415c79ce5389119670066d
cheers
On Fri, 12 Mar 2021 12:50:09 + (UTC), Christophe Leroy wrote:
> This series aims at porting interrupt entry/exit in C on PPC32, using
> the work already merged for PPC64.
>
> First patch is an optimisation around unrecoverable_exception() function.
>
> Six following patches do minimal changes
On Mon, 8 Mar 2021 17:59:47 -0800, Davidlohr Bueso wrote:
> A few updates while going through the powerpc port of the qspinlock.
>
> Patches 1 and 2 are straightforward, while patch 3 can be considered
> more of an rfc as I've only tested on a single machine, and there
> could be an alternative wa
On Mon, 15 Mar 2021 14:52:51 + (UTC), Christophe Leroy wrote:
> In fault.c, #ifdef CONFIG_PPC_MEM_KEYS is not needed because all
> functions are always defined, and arch_vma_access_permitted()
> always returns true when CONFIG_PPC_MEM_KEYS is not defined so
> access_pkey_error() will return fal
On Thu, 4 Mar 2021 14:35:09 + (UTC), Christophe Leroy wrote:
> Add architecture specific implementation details for KFENCE and enable
> KFENCE for the ppc32 architecture. In particular, this implements the
> required interface in .
>
> KFENCE requires that attributes for pages from its memory
On Tue, 16 Mar 2021 07:57:13 + (UTC), Christophe Leroy wrote:
> CONFIG_HAVE_RELIABLE_STACKTRACE is applicable to all, no
> reason to limit it to book3s/64le
Applied to powerpc/next.
[1/4] powerpc: Activate HAVE_RELIABLE_STACKTRACE for all
https://git.kernel.org/powerpc/c/accdd093f260bc8
On Wed, 10 Mar 2021 17:56:59 + (UTC), Christophe Leroy wrote:
> Patches 1-3 are cleaning parts of uaccess.h not related
> to put_user/get_user
> Patch 4 removes some usage of consecutives __get_user
> Patches 5 rewrite __patch_instruction to not use uaccess.h internals.
> Patches 6-8 switch som
On Mon, 15 Mar 2021 12:00:09 + (UTC), Christophe Leroy wrote:
> Sparse reports the following problems:
>
> arch/powerpc/math-emu/math.c:228:21: warning: Using plain integer as NULL
> pointer
> arch/powerpc/math-emu/math.c:228:31: warning: Using plain integer as NULL
> pointer
> arch/powerpc/
On Wed, 10 Mar 2021 12:43:12 + (UTC), Christophe Leroy wrote:
> Commit 6ec4476ac825 ("Raise gcc version requirement to 4.9")
> made it impossible to build with gcc 4.8 and under.
>
> Remove related workaround.
Applied to powerpc/next.
[1/1] powerpc/Makefile: Remove workaround for gcc version
On Thu, 18 Mar 2021 17:25:07 + (UTC), Christophe Leroy wrote:
> Commit 92c8c16f3457 ("powerpc/embedded6xx: Remove C2K board support")
> moved the last selector of CONFIG_MV64X60.
>
> As it is not a user selectable config, it can be removed.
Applied to powerpc/next.
[1/1] powerpc/embedded6xx:
On Mon, 29 Mar 2021 10:27:00 +0800, Chen Huang wrote:
> When compiling the powerpc with the SMP disabled, it shows the issue:
>
> arch/powerpc/kernel/watchdog.c: In function ‘watchdog_smp_panic’:
> arch/powerpc/kernel/watchdog.c:177:4: error: implicit declaration of function
> ‘smp_send_nmi_ipi’;
On Sat, 27 Mar 2021 09:49:00 +, Chen Huang wrote:
> When compiling the powerpc with the SMP disabled, it shows the issue:
>
> arch/powerpc/kernel/watchdog.c: In function ‘watchdog_smp_panic’:
> arch/powerpc/kernel/watchdog.c:177:4: error: implicit declaration of function
> ‘smp_send_nmi_ipi’;
On Mon, 15 Mar 2021 11:01:26 + (UTC), Christophe Leroy wrote:
> Commit aac6a91fea93 ("powerpc/asm: Remove unused symbols in
> asm-offsets.c") removed GPR15 to GPR31 but kept GPR14,
> probably because it pops up in a couple of comments when doing
> a grep.
>
> However, it was never used either,
Signed-off-by: Eric Lin
Reported-by: Gustavo A. R. Silva
---
drivers/net/wireless/wl3501.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/wl3501.h b/drivers/net/wireless/wl3501.h
index e98e04ee9a2c..5779ffbe5d0f 100644
--- a/drivers/net/wireless/wl3501.h
Signed-off-by: Eric Lin
Reported-by: Gustavo A. R. Silva
---
drivers/net/ethernet/via/via-velocity.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/via/via-velocity.c
b/drivers/net/ethernet/via/via-velocity.c
index b65767f9e499..fecc4d7b00b0 100644
---
intel_link_probe() could return error and dev_get_drvdata() will return
null in such case. So we have to test link->cdns after
link->cdns = dev_get_drvdata(&ldev->auxdev.dev);
Otherwise, we will meet the "kernel NULL pointer dereference" error.
Signed-off-by: Bard Liao
Reviewed-by: Ranjani Sridha
On Tue, Mar 30, 2021 at 6:53 PM Pablo Neira Ayuso wrote:
> On Sun, Mar 28, 2021 at 08:50:45PM -0400, Paul Moore wrote:
> [...]
> > Netfilter folks, were you planning to pull this via your tree/netdev
> > or would you like me to merge this via the audit tree? If the latter,
> > I would appreciate
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 30 Mar 2021 15:00:24 -0700 you wrote:
> We should not be advertising EEE for modes that we do not support,
> correct that oversight by looking at the PHY device supported linkmodes.
>
> Fixes: 99cec8a4dda2 ("net: phy: b
Two minor fixes/cleanups for the TDP MMU, found by inspection.
Sean Christopherson (2):
KVM: x86/mmu: Remove spurious clearing of dirty bit from TDP MMU SPTE
KVM: x86/mmu: Simplify code for aging SPTEs in TDP MMU
arch/x86/kvm/mmu/tdp_mmu.c | 6 ++
1 file changed, 2 insertions(+), 4 delet
Use a basic NOT+AND sequence to clear the Accessed bit in TDP MMU SPTEs,
as opposed to the fancy ffs()+clear_bit() logic that was copied from the
legacy MMU. The legacy MMU uses clear_bit() because it is operating on
the SPTE itself, i.e. clearing needs to be atomic. The TDP MMU operates
on a loc
Don't clear the dirty bit when aging a TDP MMU SPTE (in response to a MMU
notifier event). Prematurely clearing the dirty bit could cause spurious
PML updates if aging a page happened to coincide with dirty logging.
Note, tdp_mmu_set_spte_no_acc_track() flows into __handle_changed_spte(),
so the
From: Rander Wang
When stream config is failed, master runtime will release all
slave runtime in the slave_rt_list, but slave runtime is not
added to the list at this time. This patch frees slave runtime
in the config error path to fix the memory leak.
Fixes: bbe7379d8040a ("soundwire: Add suppo
Ray Chi wrote:
> Currently, when dwc3 handles request cancelled, dwc3 just returns
> -ECONNRESET for all requests. It will cause USB function drivers
> can't know if the requests are cancelled by other reasons.
>
> This patch will replace DWC3_REQUEST_STATUS_CANCELLED with the
> reasons below.
>
On Tue, 2021-03-30 at 08:39 -0500, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 05:05:28PM +0800, zhiyong tao wrote:
> > On Mon, 2021-03-29 at 14:21 -0500, Rob Herring wrote:
> > > On Mon, 29 Mar 2021 19:30:59 +0800, Zhiyong Tao wrote:
> > > > The commit adds mt8195 compatible node in binding docum
Hi all,
After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/acpi/processor_idle.c: In function 'acpi_idle_play_dead':
drivers/acpi/processor_idle.c:542:15: warning: extra tokens at end of #ifdef
directive
542 | #ifdef defined(CONFIG_X86) &&
On Tue, Mar 30, 2021 at 2:10 PM Johannes Weiner wrote:
>
[...]
> > The main concern I have with *just* reparenting LRU pages is that for
> > the long running systems, the root memcg will become a dumping ground.
> > In addition a job running multiple times on a machine will see
> > inconsistent me
On 3/30/21 4:29 PM, Nathan Chancellor wrote:
> Hi Jian,
>
> On Tue, Mar 30, 2021 at 04:02:49PM -0700, Jian Cai wrote:
>> This fixes the mismatch of alignments between csd and its use as an
>> argument to smp_call_function_single_async, which causes build failure
>> when -Walign-mismatch in Clang i
On Wed, 17 Mar 2021 23:08:13 PDT (-0700), greentime...@sifive.com wrote:
Signed-off-by: Greentime Hu
---
arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 34 ++
1 file changed, 34 insertions(+)
diff --git a/arch/riscv/boot/dts/sifive/fu740-c000.dtsi
b/arch/riscv/boot/dts/sifiv
On Mon, 29 Mar 2021 20:36:12 PDT (-0700), greentime...@sifive.com wrote:
Stephen Boyd 於 2021年3月30日 週二 上午3:14寫道：
Quoting Greentime Hu (2021-03-17 23:08:09)
> diff --git a/drivers/reset/Kconfig b/drivers/reset/Kconfig
> index 71ab75a46491..f094df93d911 100644
> --- a/drivers/reset/Kconfig
> +++
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 13:41:10 +0300 you wrote:
> Use act_simple to verify that action created with 'tc actions change'
> command exists after command returns. The goal is to verify internal action
> API reference counting to
Hi Miklos,
On Mon, 29 Mar 2021 11:28:10 +0200 Miklos Szeredi wrote:
>
> On Mon, Mar 29, 2021 at 11:14 AM Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the overlayfs tree, today's linux-next build (htmldocs)
>
> I think you mixed up drivers/of/overlay.c with fs/overlay/.
Yo
On Tue, Mar 30, 2021 at 06:53:30PM +0200, Christoph Hellwig wrote:
> On Tue, Mar 23, 2021 at 04:14:39PM +0800, Ming Lei wrote:
> > blktrace may allocate lots of memory, if the process is terminated
> > by user or OOM, we need to provide one chance to remove the trace
> > buffer, otherwise memory le
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 17:51:30 +0800 you wrote:
> Fix the following whitescan warning:
>
> Calling "zlib_inflateEnd(&state->strm)" is only useful for its return
> value, which is ignored.
>
> Reported-by: Abaci Robot
> Sig
Hi Jason,
On Tue, 30 Mar 2021 10:43:13 -0300, Jason Gunthorpe wrote:
> > If two mdevs from the same PF dev are assigned to two VMs, the PASID
> > table will be shared. IOASID set ensures one VM cannot program another
> > VM's PASIDs. I assume 'secure context' is per VM when it comes to host
> >
From: Lv Yunlong
Date: Tue, 30 Mar 2021 03:16:02 -0700
> @@ -348,7 +348,7 @@ struct rds_message *rds_message_map_pages(unsigned long
> *page_addrs, unsigned in
> rm->data.op_sg = rds_message_alloc_sgs(rm, num_sgs);
> if (IS_ERR(rm->data.op_sg)) {
> rds_message_put(rm);
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 30 Mar 2021 15:02:43 +0800 you wrote:
> It is mentioned in the official documents of the Linux Foundation and WIKI
> that you can participate in its development according to the TODO files of
> each module.
>
> Bu
-20210330
x86_64 randconfig-a003-20210330
x86_64 randconfig-a002-20210330
x86_64 randconfig-a001-20210330
x86_64 randconfig-a005-20210330
x86_64 randconfig-a006-20210330
i386 randconfig-a004-20210330
i386
Lockdep warns mm/vmscan.c: suspicious rcu_dereference_protected() usage!
when free_shrinker_info() is called from mem_cgroup_css_free(): there it
is called with no locking, whereas alloc_shrinker_info() calls it with
down_write of shrinker_rwsem - which seems appropriate. Rearrange that
so free_sh
Hi Geert,
On Tue, 30 Mar 2021 09:36:57 +0200 Geert Uytterhoeven
wrote:
>
> On Mon, Mar 29, 2021 at 4:16 AM Stephen Rothwell
> wrote:
> > Today's linux-next merge of the drm tree got a conflict in:
> >
> > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> >
> > between commits:
> >
> > 9adb125dd
The percpu_ref to gate whether cxl_memdev_ioctl() is free to use the
driver context (@cxlm) to issue I/O is overkill, implemented incorrectly
(missing a device reference before accessing the percpu_ref), and the
complexities of shutting down a percpu_ref contributed to a bug in the
error unwind in
While device_add() will happen to catch dev_set_name() failures it is a
broken pattern to follow given that the core may try to fall back to a
different name.
Add explicit checking for dev_set_name() failures to be cleaned up by
put_device(). Skip cdev_device_add() and proceed directly to
put_devi
There is no power management of cxl virtual devices, disable
device-power-management and runtime-power-management to prevent
userspace from growing expectations of those attributes appearing. They
can be added back in the future if needed.
Reviewed-by: Ben Widawsky
Signed-off-by: Dan Williams
--
While none the CXL sysfs attributes are threatening to overrun a
PAGE_SIZE of output, it is good form to use the recommended helpers.
Fixes: b39cb1052a5c ("cxl/mem: Register CXL memX devices")
Reported-by: Jason Gunthorpe
Reviewed-by: Ben Widawsky
Reviewed-by: Jason Gunthorpe
Link:
https://lor
Changes since v2: [1]
- switch from non-idiomatic srcu synchronization of the device
registration state to rwsem protection of the cxlmd->cxlm pointer.
(Jason)
[1]:
http://lore.kernel.org/r/161707245893.2072157.6743322596719518693.st...@dwillia2-desk3.amr.corp.intel.com
---
A collection of
On Wed, 17 Mar 2021 19:10:28 PDT (-0700), l...@jiuyang.me wrote:
Thanks for the review!
I see, after skimming related codes, and implementation of other architecture,
I also agree this method is too heavy to implement. And there is a potential
bug, that my patch may introduce two SFENCE.VMA in t
On Tue, Mar 30, 2021 at 03:13:04PM -0500, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 12:33 PM Daniel Walker wrote:
> >
> > On Thu, Mar 25, 2021 at 05:29:44PM -0600, Rob Herring wrote:
> > > On Thu, Mar 25, 2021 at 2:00 PM Daniel Walker wrote:
> > > >
> > > > On Thu, Mar 25, 2021 at 01:03:55PM +
On Tue, Mar 30, 2021 at 2:26 PM Daniel Borkmann wrote:
>
> On 3/30/21 10:39 PM, Andrii Nakryiko wrote:
> > On Sun, Mar 28, 2021 at 1:11 AM Kumar Kartikeya Dwivedi
> > wrote:
> >> On Sun, Mar 28, 2021 at 10:12:40AM IST, Andrii Nakryiko wrote:
> >>> Is there some succinct but complete enough docume
On Tue, Mar 30, 2021 at 1:55 PM Peter Xu wrote:
>
> On Mon, Mar 29, 2021 at 04:41:31PM -0700, Axel Rasmussen wrote:
> > Previously, we shared too much of the code with COPY and ZEROPAGE, so we
> > manipulated things in various invalid ways:
> >
> > - Previously, we unconditionally called shmem_ino
Hi Jian,
On Tue, Mar 30, 2021 at 04:02:49PM -0700, Jian Cai wrote:
> This fixes the mismatch of alignments between csd and its use as an
> argument to smp_call_function_single_async, which causes build failure
> when -Walign-mismatch in Clang is used.
>
> Link:
> http://crrev.com/c/1193732
>
> S
On Tue, Mar 30, 2021 at 10:34:25AM -0700, Sagi Grimberg wrote:
>
> > > It is, but in this situation, the controller is sending a second
> > > completion that results in a use-after-free, which makes the
> > > transport irrelevant. Unless there is some other flow (which is
> > > unclear
> > > to me
On Tue, Mar 30, 2021 at 1:28 PM Andrii Nakryiko
wrote:
> >
> > In the other thread you've proposed to copy paste hash implemenation
> > into pahole. That's not ideal. If we had libbpfutil other projects
> > could have used that without copy-paste.
>
> I know it's not ideal. But I don't think libbp
On Tue, 30 Mar 2021 at 22:39, Rob Herring wrote:
>
> On Mon, Mar 29, 2021 at 07:23:37PM -0500, Zev Weiss wrote:
> > Update DT bindings documentation for the new incarnation of the
> > aspeed,sirq-polarity-sense property.
>
> Why?
>
> This isn't a compatible change.
We want to depreciate support f
On Tue, Mar 30, 2021 at 02:49:13PM -0500, Rob Herring wrote:
> On Tue, Mar 30, 2021 at 12:57 PM Daniel Walker wrote:
> >
> > It looks like there's some seepage of cmdline stuff into
> > the generic device tree code. This conflicts with the
> > generic cmdline implementation so I remove it in the c
On Tue, Mar 30, 2021 at 3:54 PM Pedro Tammela wrote:
>
> BPF_CALL_2(bpf_ringbuf_submit, void *, sample, u64, flags)
> {
> + if (unlikely(flags & ~(BPF_RB_NO_WAKEUP | BPF_RB_FORCE_WAKEUP)))
> + return -EINVAL;
> +
> bpf_ringbuf_commit(sample, flags, false /* discard */
The reasons behind IFF_TX_SKB_NO_LINEAR are:
- most drivers expect skb with the linear space;
- most drivers expect hard header in the linear space;
- many drivers need some headroom to insert custom headers
and/or pull headers from frags (pskb_may_pull() etc.).
With some bits of overhead, w
The VirtIO TC has adopted a new feature in virtio-blk enabling
discovery of lifetime information.
This commit adds support for the VIRTIO_BLK_T_LIFETIME command
to the virtio_blk driver, and adds two new attributes to the
sysfs entry for virtio_blk:
* pre_eol_info
* life_time
which are defined in
There are a few moments that are known for sure at the moment of
copying:
- allocated skb is fully linear;
- its linear space is long enough to hold the full buffer data.
So, the out-of-line skb_put(), skb_store_bits() and the check for
a retcode can be replaced with plain memcpy(__skb_put()) wi
This series is based on the exceptional generic zerocopy xmit logics
initially introduced by Xuan Zhuo. It extends it the way that it
could cover all the sane drivers, not only the ones that are capable
of xmitting skbs with no linear space.
The first patch is a random while-we-are-here improvemen
On Tue, Mar 30, 2021 at 04:02:49PM -0700, Jian Cai wrote:
> This fixes the mismatch of alignments between csd and its use as an
> argument to smp_call_function_single_async, which causes build failure
> when -Walign-mismatch in Clang is used.
>
> Link:
> http://crrev.com/c/1193732
That link does
> On Mar 30, 2021, at 3:37 PM, Pedro Tammela wrote:
>
> The current code only checks flags in 'bpf_ringbuf_output()'.
>
> Signed-off-by: Pedro Tammela
Acked-by: Song Liu
On Wed, Mar 31, 2021 at 12:44 AM Alexandre TORGUE
wrote:
>
>
>
> On 3/30/21 10:58 AM, dillon.min...@gmail.com wrote:
> > From: dillon min
> >
> > This patch is intend to add support stm32h750 value line,
> > just add stm32h7-pinctrl.dtsi for extending, with following changes:
> >
> > - rename stm
Probing of EMC drivers may be deferred and in this case we get duplicated
info messages during kernel boot. Use dev_info_once() helper to silence
the duplicated messages.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra124-emc.c | 12 ++--
drivers/memory/tegra/tegra20-emc.c
Convert Tegra20 External Memory Controller binding to schema.
Signed-off-by: Dmitry Osipenko
---
.../memory-controllers/nvidia,tegra20-emc.txt | 130
.../nvidia,tegra20-emc.yaml | 294 ++
2 files changed, 294 insertions(+), 130 deletions(-)
delete mode
Hi,
This series replaces the raw voltage regulator with a power domain that
will be managing SoC core voltage. The core power domain patches are still
under review, but it's clear at this point that this is the way we will
implement the DVFS support.
The remaining Tegra20 memory bindings are conv
Power domain fits much better than a voltage regulator in regards to
a proper hardware description and from a software perspective as well.
Hence replace the core regulator with the power domain. Note that this
doesn't affect any existing DTBs because we haven't started to use the
regulator yet, an
Convert Tegra20 Memory Controller binding to schema.
Signed-off-by: Dmitry Osipenko
---
.../memory-controllers/nvidia,tegra20-mc.txt | 40 --
.../memory-controllers/nvidia,tegra20-mc.yaml | 79 +++
2 files changed, 79 insertions(+), 40 deletions(-)
delete mode 100644
D
Power domain fits much better than a voltage regulator in regards to
a proper hardware description and from a software perspective as well.
Hence replace the core regulator with the power domain. Note that this
doesn't affect any existing DTBs because we haven't started to use the
regulator yet, an
Power domain fits much better than a voltage regulator in regards to
a proper hardware description and from a software perspective as well.
Hence replace the core regulator with the power domain. Note that this
doesn't affect any existing DTBs because we haven't started to use the
regulator yet, an
201 - 300 of 1516 matches
Mail list logo
