On 15.07.20 at 04:36:22 CEST, Guenter Roeck wrote
> On Tue, Jul 14, 2020 at 12:52:30PM +0200, Marius Zachmann wrote:
> > I found a project which uses hidraw to communicate with the device.
> > Because I do not want to break any existing userspace code, I
> > changed this to a hid driver, so hidraw
The variable ret has been assigned the value '-EINVAL'. The assignment
in the if() is redundant. We can remove it.
Signed-off-by: Jing Xiangfeng
---
drivers/gpu/drm/drm_auth.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_auth.c b/drivers/gpu/drm/drm_auth.c
index 800ac39
Hi Alexander,
On Tue, Jul 14, 2020 at 10:18 PM Alexander A. Klimov
wrote:
>
> Rationale:
> The way it redirects looks like a fallback from a dead URL to a generic one.
>
> Signed-off-by: Alexander A. Klimov
> ---
> Yes, I noted that some of the links removed by these "CREDITS: remove link:"
>
On Mon, 13 Jul 2020 at 16:06, Christoph Hellwig wrote:
>
> On Fri, Jul 10, 2020 at 08:55:42PM -0700, Palmer Dabbelt wrote:
> > +ssize_t copy_oldmem_page(unsigned long pfn, char *buf,
> > + size_t csize, unsigned long offset,
> > + int userbuf)
> > +{
> > +
On Tue 2020-07-14 11:10:30, Petr Mladek wrote:
> With procfs v3.3.16, the sysctl command doesn't print the set key and
> value on error. This change breaks livepatch selftest test-ftrace.sh,
> that tests the interaction of sysctl ftrace_enabled:
>
> Make it work with all sysctl versions using '-q
On Wed, Jul 15, 2020 at 02:28:03PM +0800, Chen Yu wrote:
> Commit d229290689ae ("PM-runtime: add tracepoints for usage_count changes")
> has added some tracepoints to monitor the change of runtime usage, and
> there is something to improve:
> 1. There are some places that adjust the usage count not
From: Marcin Wojtas
Add IOMMU node for Marvell AP806 based SoCs together with platform
and PCI device Stream ID mapping.
Signed-off-by: Marcin Wojtas
Signed-off-by: Tomasz Nowicki
---
arch/arm64/boot/dts/marvell/armada-7040.dtsi | 28 +
arch/arm64/boot/dts/marvell/armada-8040.dts
The series is meant to support SMMU for AP806 and a workaround
for accessing ARM SMMU 64bit registers is the gist of it.
For the record, AP-806 can't access SMMU registers with 64bit width.
This patches split the readq/writeq into two 32bit accesses instead
and update DT bindings.
The series was
'cfg_probe' hook is called at the very end of configuration probing
procedure and therefore features override and workaround may become
complex like for ID register fixups. In preparation for adding Marvell
errata move 'cfg_probe' a bit earlier to have chance to adjust
the detected features before
From: Hanna Hawa
Due to erratum #582743, the Marvell Armada-AP806 can't access 64bit to
ARM SMMUv2 registers.
Provide implementation relevant hooks:
- split the writeq/readq to two accesses of writel/readl.
- mask the MMU_IDR2.PTFSv8 fields to not use AArch64 format (but
only AARCH32_L) since wi
Add specific compatible string for Marvell usage due to errata of
accessing 64bits registers of ARM SMMU, in AP806.
AP806 SoC uses the generic ARM-MMU500, and there's no specific
implementation of Marvell, this compatible is used for errata only.
Reviewed-by: Rob Herring
Signed-off-by: Hanna Haw
Hi Alexander,
On Tue, Jul 14, 2020 at 10:18 PM Alexander A. Klimov
wrote:
>
> Rationale:
> A completely white page with just an in the .
>
> Signed-off-by: Alexander A. Klimov
> ---
> Yes, I noted that some of the links removed by these "CREDITS: remove link:"
> patches have email addresses w
On Wed, Jul 15, 2020 at 12:48:13AM -0400, B K Karthik wrote:
> fixed a sparse warning by changing the type in
> assignment from void [noderef] __user * to unsigned int *
> (different address space)
>
> Signed-off-by: B K Karthik
> ---
> drivers/staging/comedi/comedi_fops.c | 2 +-
> 1 file chang
On 15-07-20, 07:45, Lee Jones wrote:
> On Wed, 15 Jul 2020, Viresh Kumar wrote:
> > On 14-07-20, 15:50, Lee Jones wrote:
> > > diff --git a/drivers/cpufreq/cpufreq_governor.c
> > > b/drivers/cpufreq/cpufreq_governor.c
> > > index f99ae45efaea7..63f7c219062b9 100644
> > > --- a/drivers/cpufreq/cpuf
On 15-07-20, 07:47, Lee Jones wrote:
> On Wed, 15 Jul 2020, Viresh Kumar wrote:
>
> > On 14-07-20, 15:50, Lee Jones wrote:
> > > -/**
> > > +/*
> > > * cpufreq_remove_dev - remove a CPU device
> >
> > Because cpufreq_add_dev() is part of kernel doc, we better keep it.
> >
> > > *
> > > * R
'bus-width' has been added to px30.dtsi mmc nodes, so now it can be
removed from the dts files that include it.
Signed-off-by: Johan Jonker
---
arch/arm64/boot/dts/rockchip/px30-evb.dts | 3 ---
arch/arm64/boot/dts/rockchip/rk3326-odroid-go2.dts | 1 -
2 files changed, 4 deletions(-)
d
On Wed, Jul 15, 2020 at 08:35:19AM +0800, Qiwu Huang wrote:
> From: Qiwu Huang
>
> Reports the kind of quick charge type based on
> different adapter power. UI will show different
> animation effect for different quick charge type.
>
> Signed-off-by: Qiwu Huang
> ---
> Documentation/ABI/testin
On Wed, Jul 15, 2020 at 08:35:23AM +0800, Qiwu Huang wrote:
> From: Qiwu Huang
>
> Broadcast battery soc with decimal form.
What does "soc" mean?
> soc_decimal is the decimal part of battery soc.
> soc_decimal_rate is update frequency of decimal
> part of battery soc.
> We want to report such
On Wed, Jul 15, 2020 at 3:46 AM Sedat Dilek wrote:
>
> On Wed, Jul 15, 2020 at 2:41 AM Arvind Sankar wrote:
> >
> > The compressed kernel currently contains bogus run-time relocations in
> > the startup code in head_{32,64}.S, which are generated by the linker,
> > but must not actually be proces
On 2020/7/15 13:45, Cong Wang wrote:
> On Tue, Jul 14, 2020 at 6:27 PM Weilong Chen wrote:
>>
>> When vlan_newlink call register_vlan_dev fails, it might return error
>> with dev->reg_state = NETREG_UNREGISTERED. The rtnl_newlink should
>> free the memory. But currently rtnl_newlink only free the
On 15/07/2020 04:56, YueHaibing wrote:
> They are never used, so can remove it.
>
> Signed-off-by: YueHaibing
> ---
> drivers/scsi/sd.h | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/scsi/sd.h b/drivers/scsi/sd.h
> index 3a74f4b45134..27c0f4e9b1d4 100644
> --- a/drivers/s
On Tue, Jul 14, 2020 at 02:39:24PM +0200, Nicolas Saenz Julienne wrote:
> This is my attempt at fixing one of the regressions we've seen[1] after
> the introduction of per-zone atomic pools.
>
> This combined with "dma-pool: Do not allocate pool memory from CMA"[2]
> should fix the boot issues on
We add mechanism to set custom IPI operations so that CLINT driver
from drivers directory can provide custom IPI operations.
Signed-off-by: Anup Patel
---
arch/riscv/include/asm/smp.h | 19
arch/riscv/kernel/sbi.c | 14
arch/riscv/kernel/smp.c | 43 +++
The current RISC-V timer driver is convoluted and implements two
distinct timers:
1. S-mode timer: This is for Linux RISC-V S-mode with MMU. The
clocksource is implemented using TIME CSR and clockevent device
is implemented using SBI Timer calls.
2. M-mode timer: This is for Linux RISC-V
We add DT bindings documentation for CLINT device.
Signed-off-by: Anup Patel
Reviewed-by: Palmer Dabbelt
---
.../bindings/timer/sifive,clint.yaml | 58 +++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/sifive,clint.yaml
di
On 2020-07-14 13:53:26 [-0700], Paul E. McKenney wrote:
> Are you good with giving Ulad a few days to produce his patch?
Yes, why not.
> Thanx, Paul
Sebastian
Right now the RISC-V timer driver is convoluted to support:
1. Linux RISC-V S-mode (with MMU) where it will use TIME CSR for
clocksource and SBI timer calls for clockevent device.
2. Linux RISC-V M-mode (without MMU) where it will use CLINT MMIO
counter register for clocksource and CLINT MMIO
The TIME CSR and SBI calls are not available in RISC-V M-mode so we
separate add CLINT driver for Linux RISC-V M-mode (i.e. RISC-V NoMMU
kernel).
Signed-off-by: Anup Patel
---
drivers/clocksource/Kconfig | 10 ++
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-clint.c
On Wed, Jul 15, 2020 at 07:44:40AM +0800, Zhixu Zhao wrote:
> On Thu, Jun 18, 2020 at 12:11:27AM +0800, Zhixu Zhao wrote:
> > A coding alignment issue is found by checkpatch.pl.
> > Fix it by using a temporary for gasket_dev->bar_data[bar_num].
> >
> > Signed-off-by: Zhixu Zhao
>
> Hi, there~
>
On 2020/7/15 14:54, Daeho Jeong wrote:
> You mean we can support ZEROOUT option only for encrypted files of
> non-multidevice f2fs,
> and return -EOPNOTSUPP in the multidevice case, right now?
Yes, something like:
f2fs_sec_trim_file()
if ((range.flags & F2FS_TRIM_FILE_ZEROOUT) &&
f2fs_en
TLBI RANGE feature instoduces new assembly instructions and only
support by binutils >= 2.30. Add necessary Kconfig logic to allow
this to be enabled and pass '-march=armv8.4-a' to KBUILD_CFLAGS.
Signed-off-by: Zhenyu Ye
---
arch/arm64/Kconfig | 14 ++
arch/arm64/Makefile | 7
ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a
range of input addresses. This patch detect this feature.
Signed-off-by: Zhenyu Ye
Link: https://lore.kernel.org/r/20200710094420.517-2-yezhen...@huawei.com
[catalin.mari...@arm.com: some renaming for consistency]
Signed-off-by:
Add __TLBI_VADDR_RANGE macro and rewrite __flush_tlb_range().
When cpu supports TLBI feature, the minimum range granularity is
decided by 'scale', so we can not flush all pages by one instruction
in some cases.
For example, when the pages = 0xe81a, let's start 'scale' from
maximum, and find right
NOTICE: this series are based on the arm64 for-next/tlbi branch:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/tlbi
ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a
range of input addresses. This series add support for this feature.
--
ChangeList:
v3:
-
On Wed, Jul 15, 2020 at 02:54:07PM +0800, Leo Yan wrote:
> On Wed, Jul 15, 2020 at 07:56:50AM +0200, Ahmed S. Darwish wrote:
> > On Wed, Jul 15, 2020 at 10:05:07AM +0800, Leo Yan wrote:
> > > From: Peter Zijlstra
> > >
> > ...
> > >
> > > Provide struct clock_read_data and two (seqcount) helpers s
On Tue, Jul 14, 2020 at 11:42:15AM -0600, Rob Herring wrote:
> On Tue, Jul 14, 2020 at 11:12 AM Joe Perches wrote:
> >
> > On Tue, 2020-07-14 at 10:21 -0600, Rob Herring wrote:
> > > On Tue, Jul 14, 2020 at 3:41 AM Thierry Reding
> > > wrote:
> > > > From: Thierry Reding
> > > >
> > > > The cur
On Wed, Jul 15, 2020 at 12:26 PM Arvind Sankar wrote:
>
> vmlinux-objs-y is added to targets, which currently means that the EFI
> stub gets added to the targets as well. It shouldn't be added since it
> is built elsewhere.
>
> This confuses Makefile.build which interprets the EFI stub as a target
On Wed, 2020-07-15 at 09:17 +0200, Greg KH wrote:
> On Wed, Jul 15, 2020 at 07:44:40AM +0800, Zhixu Zhao wrote:
> > On Thu, Jun 18, 2020 at 12:11:27AM +0800, Zhixu Zhao wrote:
> > > A coding alignment issue is found by checkpatch.pl.
> > > Fix it by using a temporary for gasket_dev->bar_data[bar_nu
On 14.07.20 21:29, Mark Brown wrote:
On Tue, Jul 14, 2020 at 10:54:15AM +0200, Frieder Schrempf wrote:
It would still be quite nice to benefit from the flexibility of DT overlays
not only for the SPI use case. But before I come up with any custom
solution, for now I will rather have the device
Hi Adrian,
On Wed, Jul 15, 2020 at 1:14 AM John Paul Adrian Glaubitz
wrote:
> However, independent of Christoph's series, the kernels throws two backtraces
> during
> boot which I think should require a git bisect (unless I missed a
> configuration option
> as I trimmed down the kernel a bit to
On Wed, Jul 15, 2020 at 09:06:14AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 15, 2020 at 02:28:03PM +0800, Chen Yu wrote:
> > Commit d229290689ae ("PM-runtime: add tracepoints for usage_count changes")
> > has added some tracepoints to monitor the change of runtime usage, and
> > there is some
add support to update firmware by the devlink flashing API
Signed-off-by: Luo bin
---
V2~V3: add error messages through extack
V1~V2: create separate devlink priv data structure and remove boot_flag
V0~V1: remove the implementation from ethtool to devlink
drivers/net/ethernet/huawei/hinic/Makef
Hi Lee,
On Mon, Jul 13, 2020 at 4:49 PM Lee Jones wrote:
> Some description blocks are void of any description/documentation,
> others are missing 'struct' identifiers, there are also a couple of
> misspellings of function parameter names. Fix all of them.
>
> Fixes the following W=1 kernel buil
On 14-07-20, 15:05, Rafael J. Wysocki wrote:
> On Tue, Jul 14, 2020 at 8:37 AM Viresh Kumar wrote:
> > static u32 get_load(struct cpufreq_cooling_device *cpufreq_cdev, int cpu,
> > int cpu_idx)
> > {
> > - u32 load;
> > - u64 now, now_idle, delta_time, delta_idle;
On Wed, 15 Jul 2020, Viresh Kumar wrote:
> On 15-07-20, 07:45, Lee Jones wrote:
> > On Wed, 15 Jul 2020, Viresh Kumar wrote:
> > > On 14-07-20, 15:50, Lee Jones wrote:
> > > > diff --git a/drivers/cpufreq/cpufreq_governor.c
> > > > b/drivers/cpufreq/cpufreq_governor.c
> > > > index f99ae45efaea7.
On Tue, 14 Jul 2020, Olof Johansson wrote:
> On Tue, Jul 14, 2020 at 11:33 PM Lee Jones wrote:
> >
> > On Tue, 14 Jul 2020, Olof Johansson wrote:
> >
> > > On Tue, Jul 14, 2020 at 7:50 AM Lee Jones wrote:
> > > >
> > > > If function callers and providers do not share the same prototypes the
> >
On Wed, 15 Jul 2020, Viresh Kumar wrote:
> On 15-07-20, 07:32, Lee Jones wrote:
> > On Wed, 15 Jul 2020, Viresh Kumar wrote:
> >
> > > On 14-07-20, 15:50, Lee Jones wrote:
> > > > This set is part of a larger effort attempting to clean-up W=1
> > > > kernel builds, which are currently overwhelmin
The format string of the task descriptor should be "%016llx".
Signed-off-by: Ben Chuang
---
drivers/mmc/host/cqhci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/cqhci.c b/drivers/mmc/host/cqhci.c
index 75934f3c117e..280d64d0b809 100644
--- a/drivers/mmc/h
The vfio_pci_release call will free and clear the error and request
eventfd ctx while these ctx could be in use at the same time in the
function like vfio_pci_request, and it's expected to protect them under
the vdev->igate mutex, which is missing in vfio_pci_release.
This issue is introduced sinc
FYI, this is now generating daily syzbot reports, so I'd love to see
the fix going into Linus' tree ASAP..
Hi Geert!
On 7/15/20 9:27 AM, Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Wed, Jul 15, 2020 at 1:14 AM John Paul Adrian Glaubitz
> wrote:
>> However, independent of Christoph's series, the kernels throws two
>> backtraces during
>> boot which I think should require a git bisect (unless I miss
Hi David,
On 14.07.2020 9:23, David E. Box wrote:
> PMT Telemetry is a capability of the Intel Platform Monitoring Technology.
> The Telemetry capability provides access to device telemetry metrics that
> provide hardware performance data to users from continuous, memory mapped,
> read-only regist
From: Bhanu Prakash Maiya
This patch enables uart transport layer for cros_ec framework.
The cros-ec-uart binds with EC device working on uart transport to
send request and receive response.
Signed-off-by: Bhanu Prakash Maiya
Reported-by: kernel test robot
Change-Id: Icb23b633700f1ef4d123e3f21
From: Bhanu Prakash Maiya
Add DT compatible string in
Documentation/devicetree/bindings/mfd/cros_ec.txt
Series-to: LKML
Series-cc: Raul E Rangel , Furquan Shaikh
, Duncan Laurie , Eric Peers
, Benson Leung , Enric Balletbo i Serra
, Guenter Roeck ,
linux-kernel@vger.kernel.org, Lee Jones ,
The generic netlink is initialized far after the netlink protocol
itself at subsys_initcall. The devlink is initialized at the same
level, but after, as shown by a disassembly of the vmlinux:
[ ... ]
374 8000115f22c0 <__initcall_devlink_init4>:
375 8000115f22c4 <__initcall_genl_init4>:
[ .
Hi Dave,
if you agree with this change, is it possible I merge it through the
thermal tree in order to fix the issue ?
Thanks
-- Daniel
On 15/07/2020 09:41, Daniel Lezcano wrote:
> The generic netlink is initialized far after the netlink protocol
> itself at subsys_initcall. The devlink is
On 7/15/20 9:27 AM, Geert Uytterhoeven wrote:
>> [5.464000] WARNING: CPU: 0 PID: 1 at mm/slab.c:2589
>> cache_alloc_refill+0x216/0x6a0
>> [5.464000] Modules linked in:
>> [5.464000]
>> [5.464000] CPU: 0 PID: 1 Comm: swapper Not tainted
>> 5.8.0-rc5-00026-g22b7a96ece82 #3
>> [5
On Tue, Jul 14, 2020 at 2:57 PM Sedat Dilek wrote:
>
> On Tue, Jul 14, 2020 at 2:53 PM Miklos Szeredi wrote:
> >
> > On Tue, Jul 14, 2020 at 2:40 PM Sedat Dilek wrote:
> >
> > > Did you sent out a new version of your patch?
> > > If yes, where can I get it from?
> >
> > Just pushed a bunch of fi
From: Bhanu Prakash Maiya
This patch enables uart transport layer for cros_ec framework.
The cros-ec-uart binds with EC device working on uart transport to
send request and receive response.
Signed-off-by: Bhanu Prakash Maiya
Reported-by: kernel test robot
Change-Id: Icb23b633700f1ef4d123e3f21
From: Bhanu Prakash Maiya
Add DT compatible string in
Documentation/devicetree/bindings/mfd/cros_ec.txt
Series-to: LKML
Series-cc: Raul E Rangel , Furquan Shaikh
, Duncan Laurie , Eric Peers
, Benson Leung , Enric Balletbo i Serra
, Guenter Roeck ,
linux-kernel@vger.kernel.org, Lee Jones ,
On Mon, Jul 13, 2020 at 11:51 PM Joakim Tjernlund
wrote:
> Did you queue for stable too?
> This bug has been there since day one for jffs2
It will. I just had no chance to re-create my setup after the
infradead.org meltdown. :-)
--
Thanks,
//richard
On 7/15/20 9:46 AM, John Paul Adrian Glaubitz wrote:
> Indeed, it does. This patch should be picked up as well.
>
> Kernel boots without any errors now.
Btw, booting with systemd as init causes a lot of hickups which I didn't see
with 3.16:
[ 25.184000] 9d903e2c
[ 25.184000] 8062124c
[
On Wed, 2020-07-15 at 15:33 +0800, Ben Chuang wrote:
> The format string of the task descriptor should be "%016llx".
There are a lot of these:
$ git grep -P -n '\b0x\d+%'
arch/m68k/include/asm/mmu_context.h:166:pr_info("ksp load failed:
mm=0x%p ksp=0x08%lx\n", mm, mmuar);
arch/powerpc/kv
On Wed, Jul 15, 2020 at 12:41:06AM -0700, Bhanu Prakash Maiya wrote:
> From: Bhanu Prakash Maiya
>
> This patch enables uart transport layer for cros_ec framework.
> The cros-ec-uart binds with EC device working on uart transport to
> send request and receive response.
>
> Signed-off-by: Bhanu P
Looks good,
Reviewed-by: Johannes Thumshirn
On Wed, Jul 15, 2020 at 12:41:31AM -0700, Bhanu Prakash Maiya wrote:
> From: Bhanu Prakash Maiya
>
> Add DT compatible string in
> Documentation/devicetree/bindings/mfd/cros_ec.txt
>
> Series-to: LKML
> Series-cc: Raul E Rangel , Furquan Shaikh
> , Duncan Laurie , Eric Peers
> , Benson Leung
On Wed, Jul 15, 2020 at 12:49:06AM -0700, Bhanu Prakash Maiya wrote:
> From: Bhanu Prakash Maiya
>
> This patch enables uart transport layer for cros_ec framework.
> The cros-ec-uart binds with EC device working on uart transport to
> send request and receive response.
>
> Signed-off-by: Bhanu P
Looks good,
Reviewed-by: Johannes Thumshirn
On Wed, Jul 15, 2020 at 12:24:22AM -0700, Joe Perches wrote:
> On Wed, 2020-07-15 at 09:17 +0200, Greg KH wrote:
> > On Wed, Jul 15, 2020 at 07:44:40AM +0800, Zhixu Zhao wrote:
> > > On Thu, Jun 18, 2020 at 12:11:27AM +0800, Zhixu Zhao wrote:
> > > > A coding alignment issue is found by checkpatch.
On Tue, Jun 09, 2020 at 02:57:36PM +1000, Dmitry Buzdyk wrote:
Hi Laurent,
Please see updated information below
> On Sun, Jun 07, 2020 at 04:07:19AM +0300, Laurent Pinchart wrote:
> > Hi Dmitry,
> >
> > Thank you for the patch.
> >
> > On Fri, May 29, 2020 at 11:05:47AM +1000, Dmitry Buzdyk wro
On 15-07-20, 08:31, Lee Jones wrote:
> I'm not sure what you mean. Kerneldoc headers are designed to be
> extracted and converted into mediums which are easy to read/browse.
> For example, see the online documentation for 'debug_object_init':
>
>
> https://www.kernel.org/doc/html/latest/core-ap
On Tue, Jul 14, 2020 at 01:54:01PM -0700, Eric Biggers wrote:
> On Tue, Jul 14, 2020 at 02:12:49PM +0200, Dominique Martinet wrote:
> >
> > > Fixes: 5643135a2846 ("fs/9p: This patch implements TLCREATE for 9p2000.L
> > > protocol.")
> > > Signed-off-by: Victor Hsieh
> > > Cc: sta...@vger.kernel.
On Tue 14-07-20 06:12:47, Tom Rix wrote:
>
> On 7/14/20 6:10 AM, Matthew Wilcox wrote:
> > On Tue, Jul 14, 2020 at 06:05:09AM -0700, t...@redhat.com wrote:
> >> From: Tom Rix
> >>
> >> clang static analysis flags this error
> >>
> >> inode.c:1083:5: warning: Argument to kfree() is the address of
Hi all,
Changes since 20200714:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings")
The bpf-next tree lost its a build failure.
The block tree gained a build failure for which i reverted a commit
Hi Adrian,
On Wed, Jul 15, 2020 at 9:37 AM John Paul Adrian Glaubitz
wrote:
> On 7/15/20 9:27 AM, Geert Uytterhoeven wrote:
> > On Wed, Jul 15, 2020 at 1:14 AM John Paul Adrian Glaubitz
> > wrote:
> >> However, independent of Christoph's series, the kernels throws two
> >> backtraces during
> >
Hi Adrian,
On Wed, Jul 15, 2020 at 9:46 AM John Paul Adrian Glaubitz
wrote:
> On 7/15/20 9:27 AM, Geert Uytterhoeven wrote:
> >> [5.464000] WARNING: CPU: 0 PID: 1 at mm/slab.c:2589
> >> cache_alloc_refill+0x216/0x6a0
> >> [5.464000] Modules linked in:
> >> [5.464000]
> >> [5.4640
Am Samstag, 11. Juli 2020, 18:32:21 CEST schrieben Sie:
> Am Dienstag, 7. Juli 2020, 08:56:41 CEST schrieben Sie:
> > Am Samstag, 27. Juni 2020, 20:23:35 CEST schrieben Sie:
> > > Dear hacker from the order of the penguins,
> > >
> > > we're facing a disturbing issue here after swapping a motherbo
On 13/07/2020 at 17:45, Claudiu Beznea - M18063 wrote:
> Hi Nicolas,
>
>
> On 13.07.2020 13:05, nicolas.fe...@microchip.com wrote:
>> From: Nicolas Ferre
>>
>> Adapt the Wake-on-Lan feature to the Cadence GEM Ethernet controller.
>> This controller has different register layout and cannot be han
On Wed, Jul 15, 2020 at 10:45:39AM +0800, Robbie Ko wrote:
>
> Kirill A. Shutemov 於 2020/7/14 下午6:19 寫道:
> > On Tue, Jul 14, 2020 at 11:46:12AM +0200, Vlastimil Babka wrote:
> > > On 7/13/20 3:57 AM, Robbie Ko wrote:
> > > > Vlastimil Babka 於 2020/7/10 下午11:31 寫道:
> > > > > On 7/9/20 4:48 AM, robb
Hi Adrian,
On Wed, Jul 15, 2020 at 9:51 AM John Paul Adrian Glaubitz
wrote:
> On 7/15/20 9:46 AM, John Paul Adrian Glaubitz wrote:
> > Indeed, it does. This patch should be picked up as well.
> >
> > Kernel boots without any errors now.
>
> Btw, booting with systemd as init causes a lot of hickup
On Wed, Jul 15, 2020 at 07:56:50AM +0200, Ahmed S. Darwish wrote:
> On Wed, Jul 15, 2020 at 10:05:07AM +0800, Leo Yan wrote:
> > From: Peter Zijlstra
> >
> ...
> >
> > Provide struct clock_read_data and two (seqcount) helpers so that
> > architectures (arm64 in specific) can expose the numbers to
On Wed, Jul 15, 2020 at 10:12:22AM +0200, Peter Zijlstra wrote:
> On Wed, Jul 15, 2020 at 07:56:50AM +0200, Ahmed S. Darwish wrote:
> > On Wed, Jul 15, 2020 at 10:05:07AM +0800, Leo Yan wrote:
> > > From: Peter Zijlstra
> > >
> > ...
> > >
> > > Provide struct clock_read_data and two (seqcount) he
On Wed, 15 Jul 2020, Viresh Kumar wrote:
> On 15-07-20, 08:31, Lee Jones wrote:
> > I'm not sure what you mean. Kerneldoc headers are designed to be
> > extracted and converted into mediums which are easy to read/browse.
> > For example, see the online documentation for 'debug_object_init':
> >
Hello!
On 14.07.2020 15:34, Adam Ford wrote:
Beacon EmbeddedWorks in introducing a development kit based on the
s/in/is/?
Renesas RZ/G2M platform. This patch adds the entry to the bindings
list.
Signed-off-by: Adam Ford
---
V2: New to series
diff --git a/Documentation/devicetree/
Hi Greg,
thanks very much for taking a look,
On Wed, Jul 15, 2020 at 09:06:14AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jul 15, 2020 at 02:28:03PM +0800, Chen Yu wrote:
> > Commit d229290689ae ("PM-runtime: add tracepoints for usage_count changes")
> > has added some tracepoints to monitor the c
On Wed, Jul 15, 2020 at 09:27:28AM +0200, Michal Miroslaw wrote:
> On Wed, Jul 15, 2020 at 09:06:14AM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jul 15, 2020 at 02:28:03PM +0800, Chen Yu wrote:
> > > Commit d229290689ae ("PM-runtime: add tracepoints for usage_count
> > > changes")
> > > has adde
On Tue, Jul 14, 2020 at 9:01 PM Melissa Wen wrote:
>
> On 07/14, Daniel Vetter wrote:
> > On Tue, Jul 14, 2020 at 07:39:42AM -0300, Melissa Wen wrote:
> > > On Tue, Jul 14, 2020 at 7:20 AM Melissa Wen wrote:
> > > >
> > > > On 07/13, Daniel Vetter wrote:
> > > > > On Fri, Jul 10, 2020 at 02:05:33
Hi Mike,
On Tue, Jul 14, 2020 at 04:21:01PM -0700, Mike Kravetz wrote:
> I agree we should only be concerned with N_MEMORY nodes for the CMA
> reservations. However, this patch got me thinking:
> - Do we really have to initiate the CMA reservations from arch specific code?
> - Can we move the cal
From: Bhanu Prakash Maiya
This patch enables uart transport layer for cros_ec framework.
The cros-ec-uart binds with EC device working on uart transport to
send request and receive response.
Signed-off-by: Bhanu Prakash Maiya
Reported-by: kernel test robot
Change-Id: Icb23b633700f1ef4d123e3f21
Hi Greg and Saravana,
On 10.07.2020 15:23, Greg Kroah-Hartman wrote:
> On Mon, Jul 06, 2020 at 03:45:02PM -0700, Saravana Kannan wrote:
>> On Tue, Jun 16, 2020 at 8:45 PM Saravana Kannan wrote:
>>> On Fri, May 29, 2020 at 5:30 AM Greg Kroah-Hartman
>>> wrote:
Looks semi-sane, but it's too c
On Wed 15-07-20 14:05:27, Joonsoo Kim wrote:
> From: Joonsoo Kim
>
> We have well defined scope API to exclude CMA region.
> Use it rather than manipulating gfp_mask manually. With this change,
> we can now use __GFP_MOVABLE for gfp_mask and the ZONE_MOVABLE is also
> searched by page allocator.
Hi Will,
On Wed, Jun 17, 2020 at 09:05:11PM +0800, John Garry wrote:
To allow userspace to identify the specific implementation of the device,
add an "identifier" sysfs file.
Encoding is as follows:
hi1620: 0x0 (aka hip08)
hi1630: 0x30
Signed-off-by: John Garry
I'm struggling a bit to
いつもお世話になります。
この度は、高卒採用に関するオンラインセミナーをご案内申し上げます。
コロナの影響で、今年の高卒採用のスケジュールは
9月の応募開始・採用選考解禁の1ヶ月後ろ倒しが決定しました。
それに伴い、例年は8月に行う職場見学を
9月まで受入が必要になる可能性があります。
企業側が高校生に直接会える場面はそう多くありません。
職場見学は貴重なチャンスです。
ここでの「事前準備」「当日の運営」「事後対応」が
その後の応募率に大きな影響を与えます。
本講座では、2000社を超える企業へのアドバイス経験を元に
50%以上を応募に繋げる職場見学の仕掛け方をご紹介い
On 7/15/20 7:05 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> Currently, preventing cma area in page allocation is implemented by using
> current_gfp_context(). However, there are two problems of this
> implementation.
>
> First, this doesn't work for allocation fastpath. In the fastpath,
From: Bhanu Prakash Maiya
This patch enables uart transport layer for cros_ec framework.
The cros-ec-uart binds with EC device working on uart transport to
send request and receive response.
Signed-off-by: Bhanu Prakash Maiya
Reported-by: kernel test robot
Change-Id: Icb23b633700f1ef4d123e3f21
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: e9919e11e219eaa5e8041b7b1a196839143e9125
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 4 weeks ago
config: arm-randconfig-s031-20200715 (attached
From: Bhanu Prakash Maiya
Add DT compatible string in
Documentation/devicetree/bindings/mfd/cros_ec.txt
Series-to: LKML
Series-cc: Raul E Rangel , Furquan Shaikh
, Duncan Laurie , Eric Peers
, Benson Leung , Enric Balletbo i Serra
, Guenter Roeck ,
linux-kernel@vger.kernel.org, Lee Jones ,
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/cpufreq/freq_table.c:229: warning: Function parameter or member
'policy' not described in 'show_available_freqs'
drivers/cpufreq/freq_table.c:229: warning: Function
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.
After these patches are applied, the build system no longer
complains about any W=0 nor W=1 level warnings in drivers/cpufreq.
Hurrah!
Changelog
Kerneldoc format for attribute descriptions should be '@.*: '.
Fixes the following W=1 kernel build warning(s):
drivers/cpufreq/sti-cpufreq.c:49: warning: cannot understand function
prototype: 'struct sti_cpufreq_ddata '
Cc: Patrice Chotard
Cc: Pal Singh
Signed-off-by: Lee Jones
---
driver
1 - 100 of 1399 matches
Mail list logo
