* network-basic-tests
* perf
* v4l2-compliance
* kvm-unit-tests
* install-android-platform-tools-r2600
* fwts
Summary
kernel: 4.4.252-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.252-rc1-hikey-20
On Fri, 15 Jan 2021 at 18:02, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.252 release.
> There are 25 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.
>
>
syzbot has found a reproducer for the following issue on:
HEAD commit:f4e087c6 Merge tag 'acpi-5.11-rc4' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=161212d0d0
kernel config:
Sorry.. I see spin_lock is running after preempt_disable.
Sorry to make a noise.
On Fri, Jan 15, 2021 at 11:03 AM Yun Levi wrote:
>
> Hi Peter, Ingo, Will and linux-kernel.
>
> While I read the code of queued_spin_lock_slowpath function,
> I have some questions about an unrelated nesting case
Once we have called device_initialize(), we should
use put_device() to give up the reference on error,
just like what we have done on failure of device_add().
Signed-off-by: Dinghao Liu
---
block/partitions/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 1/12/21 6:12 PM, Finn Thain wrote:
> If you're a museum interested in cultural artifacts from decades past, or
> if you're a business doing data recovery, you're going to need to operate
> those platforms.
Or if you're camping patent expirations and want to be able to point at prior
art for
On Fri, 15 Jan 2021 at 18:04, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.216 release.
> There are 28 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.
>
>
allnoconfig
x86_64 randconfig-a004-20210115
x86_64 randconfig-a006-20210115
x86_64 randconfig-a001-20210115
x86_64 randconfig-a003-20210115
x86_64 randconfig-a005-20210115
x86_64 randconfig-a002
On Thu, Jan 14, 2021 at 11:35 PM Peter Zijlstra wrote:
>
> -void kthread_set_per_cpu(struct task_struct *k, bool set)
> +void kthread_set_per_cpu(struct task_struct *k, int cpu)
> {
> struct kthread *kthread = to_kthread(k);
> if (!kthread)
> return;
>
> -
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: b45e2da6e444280f8661dca439c1e377761b2877
commit: c60b93cd4862d108214a14e655358ea714d7a12a drm/i915: Avoid mixing integer
types during batch copies
date: 4 months ago
compiler: gcc-9 (Debian 9.3.0-15)
Hi Wei,
I love your patch! Yet something to improve:
[auto build test ERROR on linux/master]
[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 documented in
https://git-scm.com/docs/git-format-patch]
url:
On Fri, 15 Jan 2021 at 18:04, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.168 release.
> There are 43 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.
>
>
On Fri, Jan 15, 2021 at 9:05 PM Peter Zijlstra wrote:
>
> On Fri, Jan 15, 2021 at 10:11:51AM +0100, Peter Zijlstra wrote:
> > On Tue, Jan 12, 2021 at 03:53:24PM -0800, Paul E. McKenney wrote:
> > > An SRCU-P run on the new series reproduced the warning below. Repeat-by:
> > >
> > >
v1: https://lore.kernel.org/patchwork/cover/1364392/
v2:
1) Fix checkpatch issues.
2) Remove set_pmd and pmd_populate because it's not necessary.
Nylon Chen (1):
riscv/kasan: add KASAN_VMALLOC support
arch/riscv/Kconfig | 1 +
arch/riscv/mm/kasan_init.c | 57
It references to x86/s390 architecture.
So, it doesn't map the early shadow page to cover VMALLOC space.
Prepopulate top level page table for the range that would otherwise be
empty.
lower levels are filled dynamically upon memory allocation while
booting.
Signed-off-by: Nylon Chen
From: Lai Jiangshan
When we attach a rescuer to a pool, we will set the rescuer's cpumask
to the pool's cpumask. If there is hotplug ongoing, it may cause
the rescuer running on the dying CPU and cause bug or it may cause
warning of setting online&!active cpumask.
So we have to find a reliable
The use of 'struct static_key' and 'static_key_false' is
deprecated. Use the new API.
mmu_audit_key can only be true or false so it would be nice to use
static_branch_enable()/static_branch_disable() for it and not
static_key_slow_inc()/static_key_slow_dec().
Signed-off-by: Cun Li
---
Sorry for my late reply. Several final exams have delayed me these days.
Thank you for your detailed advice!
On 1/15/21 6:25 PM, Sean Christopherson wrote:
Introduce a new Kconfig, AMD_SEV_ES_GUEST, to control the inclusion of
support for running as an SEV-ES guest. Pivoting on AMD_MEM_ENCRYPT for
guest SEV-ES support is undesirable for host-only kernel builds as
AMD_MEM_ENCRYPT is also required to
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1d94330a437a573cfdf848f6743b1ed169242c8a
commit: c6d4a099a240a8742173f8e02db0ba08ffd37ef1 drm/i915: reimplement header
test feature
date: 1 year ago
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the
Several error paths in bind/probe code will only emit
output using dev_dbg. But if we are going to fail the
bind/probe, emit related output with "err" priority.
Signed-off-by: Grant Grundler
---
drivers/net/usb/cdc_ncm.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff
RTL8156 sends notifications about every 32ms.
Only display/log notifications when something changes.
This issue has been reported by others:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832472
https://lkml.org/lkml/2020/8/27/1083
...
[785962.779840] usb 1-1: new
Errors in protocol should be logged when the driver aborts operations.
If the driver can carry on and "humor" the device, then emitting
the message as debug output level is fine.
Signed-off-by: Grant Grundler
---
drivers/net/usb/usbnet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Sat, Jan 16, 2021 at 6:07 AM Sedat Dilek wrote:
>
> On Sat, Jan 16, 2021 at 1:13 AM Nick Desaulniers
> wrote:
> >
> > > On Wed, Jan 13, 2021 at 8:07 PM Nick Desaulniers
> > > wrote:
> > > >
> > > > On Wed, Jan 13, 2021 at 12:55 PM Nathan Chancellor
> > > > wrote:
> > > > >
> > > > >
On Sat, Jan 09, 2021 at 10:11:09PM +, Pavel Begunkov wrote:
> > Does any code actually look at the fields as a pair?
> > Would it even be better to use separate bytes?
> > Even growing the on-stack structure by a word won't really matter.
>
> u8 type, rw;
>
> That won't bloat the struct. I
Hi Wei,
I love your patch! Yet something to improve:
[auto build test ERROR on linux/master]
[also build test ERROR on soc/for-next linus/master v5.11-rc3 next-20210115]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base
On 1/15/21 6:04 PM, Eric Biggers wrote:
> On Fri, Jan 15, 2021 at 04:20:44PM -0800, Dave Hansen wrote:
>> On 1/15/21 4:14 PM, Dey, Megha wrote:
>>> Also, I do not know of any cores that implement PCLMULQDQ and not AES-NI.
>> That's true, bit it's also possible that a hypervisor could enumerate
>>
On 1/15/21 5:07 PM, Chris Wilson wrote:
> Quoting Chris Wilson (2021-01-15 16:56:42)
>> Quoting Jinoh Kang (2021-01-15 16:23:31)
>>> If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
>>> returned only when the object is actually bound.
>>>
>>> The xf86-video-intel userspace
On Sat, Jan 16, 2021 at 1:13 AM Nick Desaulniers
wrote:
>
> > On Wed, Jan 13, 2021 at 8:07 PM Nick Desaulniers
> > wrote:
> > >
> > > On Wed, Jan 13, 2021 at 12:55 PM Nathan Chancellor
> > > wrote:
> > > >
> > > > However, I see an issue with actually using the data:
> > > >
> > > > $ sudo -s
>
On 1/15/2021 5:43 PM, Eric Biggers wrote:
On Fri, Jan 15, 2021 at 04:14:40PM -0800, Dey, Megha wrote:
Hello Megha,
What is the purpose of this separate GHASH module? GHASH is only used
in combination with AES-CTR to produce GCM, and this series already
contains a GCM driver.
Do cores exist
On 1/15/2021 6:39 PM, Rasmus Villemoes wrote:
> mv88e6xxx_port_vlan_join checks whether the VTU already contains an
> entry for the given vid (via mv88e6xxx_vtu_getnext), and if so, merely
> changes the relevant .member[] element and loads the updated entry
> into the VTU.
>
> However, at
On 1/15/2021 6:39 PM, Rasmus Villemoes wrote:
> mv88e6250_g1_vtu_getnext is almost identical to
> mv88e6185_g1_vtu_getnext, except for the 6250 only having 64 databases
> instead of 256. We can reduce code duplication by simply masking off
> the extra two garbage bits when assembling the fid
On 1/15/21 4:12 PM, Matteo Croce wrote:
> On Fri, Jan 15, 2021 at 11:50 PM Jakub Kicinski wrote:
>>
>> On Fri, 15 Jan 2021 19:42:07 +0100 Matteo Croce wrote:
>>> From: Matteo Croce
>>>
>>> Fix two wrong flags in the IPv6 multicast routes created
>>> by the autoconf code.
>>
>> Any chance for
On Sat, Jan 16, 2021 at 12:26 PM Matthew Wilcox wrote:
>
> On Fri, Jan 15, 2021 at 04:31:02PM -0800, Mike Kravetz wrote:
> > +++ b/fs/hugetlbfs/inode.c
> > @@ -735,7 +735,7 @@ static long hugetlbfs_fallocate(struct file *file, int
> > mode, loff_t offset,
> >
> >
On 1/15/21 11:42 AM, Matteo Croce wrote:
> From: Matteo Croce
>
> The ff00::/8 multicast route is created without specifying the fc_protocol
> field, so the default RTPROT_BOOT value is used:
>
> $ ip -6 -d route
> unicast ::1 dev lo proto kernel scope global metric 256 pref medium
>
On Fri, Jan 15, 2021 at 10:43:32PM -0500, Tejun Heo wrote:
> On Fri, Jan 15, 2021 at 02:18:40PM -0800, Vipin Sharma wrote:
> > > * Why is .sev a separate namespace? Isn't the controller supposed to cover
> > > encryption ids across different implementations? It's not like multiple
> > > types
On 15/01/2021 15:57, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:14662050 Merge tag 'linux-kselftest-fixes-5.11-rc4' of git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11a09ed0d0
> kernel config:
On Thu, 14 Jan 2021 21:26:28 +0100 Andrea Parri (Microsoft) wrote:
> For additional robustness in the face of Hyper-V errors or malicious
> behavior, validate all values that originate from packets that Hyper-V
> has sent to the guest. Ensure that invalid values cannot cause indexing
> off the
On Sat, Jan 16, 2021 at 1:13 AM Nick Desaulniers
wrote:
>
> > On Wed, Jan 13, 2021 at 8:07 PM Nick Desaulniers
> > wrote:
> > >
> > > On Wed, Jan 13, 2021 at 12:55 PM Nathan Chancellor
> > > wrote:
> > > >
> > > > However, I see an issue with actually using the data:
> > > >
> > > > $ sudo -s
>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 14 Jan 2021 12:14:56 +0800 you wrote:
> In bictcp_reset(), use memset and offsetof instead of = 0.
>
> Signed-off-by: Yejune Deng
> ---
> net/ipv4/tcp_cubic.c | 11 +--
> 1 file changed, 1 insertion(+),
On Fri, Jan 15, 2021 at 04:31:02PM -0800, Mike Kravetz wrote:
> +++ b/fs/hugetlbfs/inode.c
> @@ -735,7 +735,7 @@ static long hugetlbfs_fallocate(struct file *file, int
> mode, loff_t offset,
>
> mutex_unlock(_fault_mutex_table[hash]);
>
> -
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 14 Jan 2021 18:32:38 -0800 you wrote:
> From: Menglong Dong
>
> Replace some checks for ETH_P_8021Q and ETH_P_8021AD in
> drivers/net/tap.c with eth_type_vlan.
>
> Signed-off-by: Menglong Dong
>
> [...]
Here
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 15 Jan 2021 12:14:53 +0800 you wrote:
> Use the struct member w of the struct urelease_work directly instead of
> casting it.
>
> Signed-off-by: Geliang Tang
> ---
> net/nfc/netlink.c | 4 ++--
> 1 file changed,
On Fri, 15 Jan 2021 at 18:04, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.90 release.
> There are 62 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.
>
>
On Tue, Jan 12, 2021 at 09:19:05AM +0100, Christoph Hellwig wrote:
> sizeof needs to be called on the compat pointer, not the native one.
in #fixes and #for-next now...
On Fri, 15 Jan 2021 at 18:07, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.10.8 release.
> There are 103 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.
>
>
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v5.11-rc3 next-20210115]
[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 documented
On Fri, Jan 15, 2021 at 02:18:40PM -0800, Vipin Sharma wrote:
> > * Why is .sev a separate namespace? Isn't the controller supposed to cover
> > encryption ids across different implementations? It's not like multiple
> > types of IDs can be in use on the same machine, right?
> >
>
> On AMD
On 1/15/21 11:46 AM, David Hildenbrand wrote:
7) There is no easy way to detect if a page really was pinned: we might
have false positives. Further, there is no way to distinguish if it was
pinned with FOLL_WRITE or not (R vs R/W). To perform reliable tracking
we most probably would need more
Add support for the Hisilicon Kunpeng L3 cache controller as used with
Kunpeng506 and Kunpeng509 SoCs.
These Hisilicon SoCs support LPAE, so the physical addresses is wider than
32-bits, but the actual bit width does not exceed 36 bits. When the cache
operation is performed based on the address
The outercache of some Hisilicon SOCs support physical addresses wider
than 32-bits. The unsigned long datatype is not sufficient for mapping
physical addresses >= 4GB. The commit ad6b9c9d78b9 ("ARM: 6671/1: LPAE:
use phys_addr_t instead of unsigned long in outercache functions") has
already
v4 --> v5:
1. Add SoC macro ARCH_KUNPENG50X, and the Kunpeng L3 cache controller only
enabled
on that platform.
2. Require the compatible string of the Kunpeng L3 cache controller must have a
relevant name on a specific SoC. For example:
compatible = "hisilicon,kunpeng509-l3cache",
Add devicetree binding for Hisilicon Kunpeng L3 cache controller.
Signed-off-by: Zhen Lei
---
.../arm/hisilicon/kunpeng-l3cache.yaml| 40 +++
1 file changed, 40 insertions(+)
create mode 100644
Documentation/devicetree/bindings/arm/hisilicon/kunpeng-l3cache.yaml
diff
-by: Randy Dunlap
Reported-by: kernel test robot
Cc: Atish Patra
Cc: Palmer Dabbelt
Cc: Ard Biesheuvel
Cc: Anson Huang
Cc: Daniel Baluta
Cc: Shawn Guo
Cc: Dong Aisheng
---
drivers/firmware/imx/Kconfig |1 +
1 file changed, 1 insertion(+)
--- linux-next-20210115.orig/drivers/firmware/i
Enable support for the Hisilicon Kunpeng506 and Kunpeng509 SoC.
Signed-off-by: Zhen Lei
---
arch/arm/mach-hisi/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
index 2e980f834a6aa1b..c724acc5c642b97 100644
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
head: 767d46ab566dd489733666efe48732d523c8c332
commit: b6724f118d44606fddde391ba7527526b3cad211 [4/5] prctl: Hook L1D flushing
in via prctl
config: i386-randconfig-r026-20210115 (attached as .config)
compiler: gcc-9
Sorry, that test in the end was inverted of course.. it should read
if( (DeviceFD = open( /dev/sdb, O_RDWR )) != ERROR ) {
printf("success\n"); // <== use to work (open R/W)
} else {
printf("failure"); // <== now fails under kernel 5.10
}
[adding linux-scsi mailing list:
Does linux-usb need to added also?]
On 1/15/21 7:03 PM, Michael Katzmann wrote:
> I have USB devices that have a write enable/write protect feature.
> A vendor specific SCSI command write enables a write protected drive.
> In kernels prior to 5.10 I have been able
I have USB devices that have a write enable/write protect feature.
A vendor specific SCSI command write enables a write protected drive.
In kernels prior to 5.10 I have been able to write-enable the drive
(by sending the vendor specific command to the SCSI generic device)
and then change the read
Hi,
On Fri, Jan 15, 2021 at 07:04:31AM +0530, Nava kishore Manne wrote:
> This patch adds support for Xilinx Dynamic Function eXchange(DFX) AXI
> shutdown manager IP. It can be used to safely handling the AXI traffic
> on a Reconfigurable Partition when it is undergoing dynamic reconfiguration
>
mv88e6250_g1_vtu_getnext is almost identical to
mv88e6185_g1_vtu_getnext, except for the 6250 only having 64 databases
instead of 256. We can reduce code duplication by simply masking off
the extra two garbage bits when assembling the fid from VTU op [3:0]
and [11:8].
Signed-off-by: Rasmus
mv88e6xxx_port_vlan_join checks whether the VTU already contains an
entry for the given vid (via mv88e6xxx_vtu_getnext), and if so, merely
changes the relevant .member[] element and loads the updated entry
into the VTU.
However, at least for the mv88e6250, the on-stack struct
mv88e6xxx_vtu_entry
I finally managed to figure out why enabling VLAN filtering on the
6250 broke all (ingressing) traffic,
cf.
https://lore.kernel.org/netdev/6424c14e-bd25-2a06-cf0b-f1a07f9a3...@prevas.dk/
.
The first patch is the minimal fix and for net, while the second one
is a little cleanup for net-next.
Documentation of Encryption IDs controller. This new controller is used
to track and limit usage of hardware memory encryption capabilities on
the CPUs.
Signed-off-by: Vipin Sharma
Reviewed-by: David Rientjes
Reviewed-by: Dionna Glaze
---
.../admin-guide/cgroup-v1/encryption_ids.rst | 1 +
Hardware memory encryption is available on multiple generic CPUs. For
example AMD has Secure Encrypted Virtualization (SEV) and SEV -
Encrypted State (SEV-ES).
These memory encryptions are useful in creating encrypted virtual
machines (VMs) and user space programs.
There are limited number of
Hello,
This patch adds a new cgroup controller, Encryption IDs, to track and
limit the usage of encryption IDs on a host.
AMD provides Secure Encrypted Virtualization (SEV) and SEV with
Encrypted State (SEV-ES) to encrypt the guest OS's memory using limited
number of Address Space Identifiers
On Fri, Jan 15, 2021 at 04:20:44PM -0800, Dave Hansen wrote:
> On 1/15/21 4:14 PM, Dey, Megha wrote:
> > Also, I do not know of any cores that implement PCLMULQDQ and not AES-NI.
>
> That's true, bit it's also possible that a hypervisor could enumerate
> support for PCLMULQDQ and not AES-NI. In
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 15 Jan 2021 07:31:28 -0800 you wrote:
> From: Tom Rix
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix
>
> [...]
Here is the summary with links:
- net:
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Thu, 14 Jan 2021 13:29:17 -0800 you wrote:
> From: Tom Rix
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix
>
> [...]
Here is the summary with links:
-
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 13 Jan 2021 13:56:03 -0800 you wrote:
> From: Tom Rix
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix
>
> [...]
Here is the summary with links:
-
yamllint warns:
./Documentation/devicetree/bindings/pinctrl/microchip,sparx5-sgpio.yaml
102:10 error wrong indentation: expected 10 but found 9 (indentation)
Signed-off-by: Jonathan Neuschäfer
---
.../devicetree/bindings/pinctrl/microchip,sparx5-sgpio.yaml | 4 ++--
1 file changed, 2
Hi Jason,
No worries, thanks!
Linus
> Hey Linus,
>
> My email server has been firewalled from vger.kernel.org until today,
> so I didn't see the original until this v2 was sent today. My
> apologies. I'll review this first thing on Monday.
>
> Jason
>
On 1/15/21 5:12 PM, Song Liu wrote:
On Jan 15, 2021, at 4:55 PM, Yonghong Song wrote:
On 1/15/21 3:34 PM, Song Liu wrote:
On Jan 12, 2021, at 8:53 AM, KP Singh wrote:
On Tue, Jan 12, 2021 at 5:32 PM Yonghong Song wrote:
On 1/11/21 3:45 PM, Song Liu wrote:
On Jan 11, 2021,
On Fri, Jan 15, 2021 at 04:14:40PM -0800, Dey, Megha wrote:
> > Hello Megha,
> >
> > What is the purpose of this separate GHASH module? GHASH is only used
> > in combination with AES-CTR to produce GCM, and this series already
> > contains a GCM driver.
> >
> > Do cores exist that implement
On Thu, Jan 14, 2021 at 11:59 PM Geert Uytterhoeven
wrote:
>
> Hi Atish,
>
> On Thu, Jan 14, 2021 at 10:11 PM Atish Patra wrote:
> > On Thu, Jan 14, 2021 at 11:46 AM Palmer Dabbelt wrote:
> > > On Thu, 14 Jan 2021 10:33:01 PST (-0800), ati...@atishpatra.org wrote:
> > > > On Wed, Jan 13, 2021
The items of the 'maintainers' list are indented with three spaces.
Use the usual two spaces instead, for consistency and to silence
yamllint.
Signed-off-by: Jonathan Neuschäfer
---
.../bindings/sound/mt8192-mt6359-rt1015-rt5682.yaml | 4 ++--
1 file changed, 2 insertions(+), 2
On Fri, Jan 15, 2021 at 11:55 PM Masahiro Yamada wrote:
>
> Yes, I plan to merge scripts/ld-version.sh and scripts/lld-version.sh
> in a similar way, and move the version check as well
> once the following cleanups land in the upstream:
>
>
On Wed, 13 Jan 2021 19:40:28 +0100 Łukasz Stelmach wrote:
> ASIX AX88796[1] is a versatile ethernet adapter chip, that can be
> connected to a CPU with a 8/16-bit bus or with an SPI. This driver
> supports SPI connection.
>
> The driver has been ported from the vendor kernel for ARTIK5[2]
>
On Wed, 2020-12-23 at 14:45 +, Dario Faggioli wrote:
> From: Lorenzo Brescia
>
> On VMX, if we exit and then re-enter immediately without leaving
> the vmx_vcpu_run() function, the kvm_entry event is not logged.
> That means we will see one (or more) kvm_exit, without its (their)
>
From: Lino Sanfilippo
In tpm2_del_space() the sessions are flushed by means of the tpm_chip
operations. However the concerning operations pointer my already be NULL at
this time in case that the chip has been unregistered (see
tpm_chip_unregister() which calls tpm_del_char_device() which sets
From: Lino Sanfilippo
In tpmm_chip_alloc() a resource management action handler is installed to
release the chip->dev in case of error. This will result in the chip being
freed if it was the last reference. If the installation of the handler was
not successful an error is returned to the caller.
From: Lino Sanfilippo
Commit 8979b02aaf1d ("tpm: Fix reference count to main device") tried to
fix a reference count issue which prevented the tpm_chip structure from
being freed in case that no TPM2 was used. The fix was to only get an extra
reference for chip->dev in case of TPM2 which is
From: Lino Sanfilippo
Provide a function tpm_chip_free() as a counterpart to tpm_chip_alloc().
The function hides the internals of freeing a struct tpm_chip instance
by putting the device references which are part of this structure.
Use the new function at the appropriate places.
This patch series fixes some flaws in the TPM code. Most importantly a
reference count issue (patch 2) and a possible NULL pointer access
(patch 3). Patch 1 fixes the error path in tpmm_chip_alloc() and is in
preparation to patch 2 which extends this function. Patch 4 introduces
a new function
Add 'perf irq' to trace/measure the hardware interrupts.
Now three functions are provided:
1. 'perf irq record ' to record the irq handler events.
2. 'perf irq script' to see a detailed trace of the workload that
was recorded.
3. 'perf irq report' to calculate the time consumed by each
Hi,
On 2021/1/15 14:31, Leon Romanovsky wrote:
On Fri, Jan 15, 2021 at 07:49:47AM +0800, Lu Baolu wrote:
Hi Leon,
On 1/14/21 9:26 PM, Leon Romanovsky wrote:
On Thu, Jan 14, 2021 at 09:30:02AM +0800, Lu Baolu wrote:
Some vendor IOMMU drivers are able to declare that it is running in a VM
Add documentation for 'perf irq' command.
Signed-off-by: Bixuan Cui
---
tools/perf/Documentation/perf-irq.txt | 47 +++
tools/perf/command-list.txt | 1 +
2 files changed, 48 insertions(+)
create mode 100644 tools/perf/Documentation/perf-irq.txt
diff --git
When the hardware interrupt processing function is executed, the interrupt and
preemption of current cpu are disabled. As a result, the task is suspended.
The execution of the hardware processing function takes a long time
(for example 5 ms), will affect the task scheduling performance.
This
There are multiple instances of GPIO devictree nodes of the form:
foo {
compatible = "acme,foo";
...
gpio0: gpio0@ {
compatible = "acme,bar";
...
gpio-controller;
};
gpio1: gpio1@ {
> On Jan 15, 2021, at 4:55 PM, Yonghong Song wrote:
>
>
>
> On 1/15/21 3:34 PM, Song Liu wrote:
>>> On Jan 12, 2021, at 8:53 AM, KP Singh wrote:
>>>
>>> On Tue, Jan 12, 2021 at 5:32 PM Yonghong Song wrote:
On 1/11/21 3:45 PM, Song Liu wrote:
>
>
>> On
The general trend is to have devicetree bindings in YAML format, to
allow automatic validation of bindings and devicetrees.
Convert the NPCM SoC family's binding to YAML before it accumulates more
entries.
The nuvoton,npcm750-evb compatible string is introduced to keep the
structure of the
According to the revised binding, the devicetree needs a board-specific
compatible string.
Signed-off-by: Jonathan Neuschäfer
---
v2:
- no changes
---
arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi,
On Fri, Jan 8, 2021 at 4:36 PM Linus Walleij wrote:
>
> Hi Doug,
>
> this is an impressive patch.
>
> We definitely need to touch base with Bjorn on this, preferably also
> Sboyd.
>
> On Fri, Jan 8, 2021 at 6:35 PM Douglas Anderson wrote:
>
> > Fixes: 4b7618fdc7e6 ("pinctrl: qcom: Add
> -Original Message-
> From: Arnd Bergmann
> Sent: Saturday, January 16, 2021 1:05 AM
> To: Ryan Chen
> Cc: John Wang ;
> xuxiao...@bytedance.com; yulei...@bytedance.com; Robert Lippert
> ; moderated list:ARM/ASPEED MACHINE SUPPORT
> ; Greg Kroah-Hartman
> ; Vernon Mauery
> ; open list ;
In arch nds32, build fail with following errors:
lib/dynamic_queue_limits.c: In function 'dql_reset':
lib/dynamic_queue_limits.c:119:2: error: implicit declaration of
function 'memset' [-Werror=implicit-function-declaration]
memset(dql, 0, offsetof(struct dql, lowest_slack));
Add fixes
From: Daeho Jeong
We've added a new mount option "checkpoint=merge", which creates a
kernel daemon and makes it to merge concurrent checkpoint requests as
much as possible to eliminate redundant checkpoint issues. Plus, we
can eliminate the sluggish issue caused by slow checkpoint operation
when
Sorry, ignore this.
I've sent this wrong. :(
2021년 1월 16일 (토) 오전 9:58, Daeho Jeong 님이 작성:
>
> From: Daeho Jeong
>
> Added "ckpt_thread_ioprio" sysfs node to give a way to change checkpoint
> merge daemon's io priority. Its default value is "be,3", which means
> "BE" I/O class and I/O priority
From: Daeho Jeong
Added "ckpt_thread_ioprio" sysfs node to give a way to change checkpoint
merge daemon's io priority. Its default value is "be,3", which means
"BE" I/O class and I/O priority "3". We can select the class between "rt"
and "be", and set the I/O priority within valid range of it.
Hi,
On Fri, Jan 15, 2021 at 12:39 PM Stephen Boyd wrote:
>
> Let's skip printing anything if there's nothing to see. This makes it so
> the file length is 0 instead of 1, for the newline, and helps scripts
> figure out if there's anything to see in these files.
>
> Cc: Sai Prakash Ranjan
> Cc:
On 1/15/21 3:34 PM, Song Liu wrote:
On Jan 12, 2021, at 8:53 AM, KP Singh wrote:
On Tue, Jan 12, 2021 at 5:32 PM Yonghong Song wrote:
On 1/11/21 3:45 PM, Song Liu wrote:
On Jan 11, 2021, at 1:58 PM, Martin Lau wrote:
On Mon, Jan 11, 2021 at 10:35:43PM +0100, KP Singh wrote:
1 - 100 of 1585 matches
Mail list logo
