get_clean_sp() is only used once in kernel/signal.c .
And GCC is smart enough to see that x & 0x is a nop
calculation on PPC32, no need of a special PPC32 trivial version.
Include the logic from the PPC64 version of get_clean_sp() directly
in get_sigframe()
Signed-off-by: Christophe Lero
For the non VSX version, that's trivial. Just use unsafe_copy_to_user()
instead of __copy_to_user().
For the VSX version, remove the intermediate step through a buffer and
use unsafe_put_user() directly. This generates a far smaller code which
is acceptable to inline, see below:
Standard VSX vers
As this was the last user of put_sigset_t(), remove it as well.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/signal_32.c | 24 ++--
1 file changed, 10 insertions(+), 14 deletions(-)
diff --git a/arch/powerpc/kernel/signal_32.c b/arch/powerpc/kernel/signal_32.c
ind
put_sigset_t() calls copy_to_user() for copying two words.
Because INLINE_COPY_TO_USER is not defined on powerpc,
copy_to_user() doesn't get optimised and falls back to
copy_tofrom_user() with the relevant glue. This is terribly
inefficient for copying two words.
By switching to unsafe_put_user()
On the same model as ptrace_get_reg() and ptrace_put_reg(),
create ptrace_get_fpr() and ptrace_put_fpr() to get/set
the floating points registers.
We move the boundary checkings in them.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/ptrace/Makefile | 1 +
arch/powerpc/kernel/ptr
Some secure elements like NXP's SE050 sit on I2C buses. For OP-TEE to
control this type of cryptographic devices it needs coordinated access
to the bus, so collisions and RUNTIME_PM dont get in the way.
This trampoline driver allow OP-TEE to access them.
Signed-off-by: Jorge Ramirez-Ortiz
---
v
Em Tue, Aug 11, 2020 at 04:27:35PM +0900, Namhyung Kim escreveu:
> On Mon, Aug 10, 2020 at 3:22 PM Alexander Gordeev
> wrote:
> >
> > Cc: Peter Zijlstra
> > Cc: Ingo Molnar
> > Cc: Arnaldo Carvalho de Melo
> > Cc: Mark Rutland
> > Cc: Alexander Shishkin
> > Cc: Jiri Olsa
> > Cc: Namhyung Kim
Today we have:
#ifdef CONFIG_PPC32
index = addr >> 2;
if ((addr & 3) || child->thread.regs == NULL)
#else
index = addr >> 3;
if ((addr & 7))
#endif
sizeof(long) has value 4 for PPC32 and value 8 for PPC64.
Di
Em Mon, Aug 10, 2020 at 08:22:00AM +0200, Alexander Gordeev escreveu:
> Standard benchmark names let users know the tests specifics.
> For example "2x1-bw-process" name tells that two processes
> one thread each are run and the RAM bandwidth is measured.
>
> Several benchmarks names do not corresp
On Wed, 2020-08-12 at 17:37 +0800, Wenbin Mei wrote:
> This patch adds a optional reset management for msdc.
> Sometimes the bootloader does not bring msdc register
> to default state, so need reset the msdc controller.
>
> Signed-off-by: Wenbin Mei
> ---
> drivers/mmc/host/mtk-sd.c | 13 +++
Em Wed, Aug 12, 2020 at 07:46:47AM +0100, Colin King escreveu:
> From: Colin Ian King
>
> There are a couple of spelling mistakes in the text. Fix these.
Thanks, applied.
- Arnaldo
> Signed-off-by: Colin Ian King
> ---
> tools/perf/bench/find-bit-bench.c | 4 ++--
> 1 file changed, 2 insert
On Tue, Aug 11, 2020 at 7:39 AM David Gow wrote:
>
> This patchset contains everything needed to integrate KASAN and KUnit.
>
> KUnit will be able to:
> (1) Fail tests when an unexpected KASAN error occurs
> (2) Pass tests when an expected KASAN error occurs
>
> Convert KASAN tests to KUnit with t
Em Wed, Aug 12, 2020 at 02:59:53PM +0800, Jin Yao escreveu:
> Currently if we run 'perf record -e cycles:u', exclude_guest is 0.
>
> But it doesn't make sense that we request for user-space counting
> but we also get the guest report.
>
> To keep perf semantics consistent and clear, this patch se
在 2020/8/12 下午7:43, Alex Shi 写道:
>>> Sorry, I still can not follow you here. Compound code part is unchanged
>>> and follow the original logical. So would you like to pose a new code to
>>> see if its works?
>> No there are significant changes as you reordered all of the
>> operations. Prior to
Em Tue, Aug 11, 2020 at 03:42:45PM +0900, Namhyung Kim escreveu:
> Hi David,
>
> On Sat, Aug 8, 2020 at 1:48 AM David Ahern wrote:
> >
> > Commit fbd705a0c618 ("sched: Introduce the 'trace_sched_waking' tracepoint")
> > added sched_waking tracepoint which should be preferred over sched_wakeup
> >
Em Mon, Aug 10, 2020 at 02:24:26PM -0700, Kan Liang escreveu:
> The Bitwise-Shift operator (1U << ) is used in the enum
> perf_output_field, which has already reached its capacity (32 items).
> If more items are added, a compile error will be triggered.
>
> Change the U to ULL, which extend the ca
As an effect of changes in Intel, I took resposibility for supporting
Intel TXT in Linux from Ning Sun. This patch also replaces link to
repository, as previous one became outdated.
Signed-off-by: Lukasz Hawrylko
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
Em Mon, Aug 10, 2020 at 03:34:04PM +0200, Vincent Whitchurch escreveu:
> For memcpy, the source pages are memset to zero only when --cycles is
> used. This leads to wildly different results with or without --cycles,
> since all sources pages are likely to be mapped to the same zero page
> without
Enable pre-update addressing mode in __get_user_asm() and __put_user_asm()
Signed-off-by: Christophe Leroy
---
v3: new, splited out from patch 1.
---
arch/powerpc/include/asm/uaccess.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/include/asm/uaccess.h
At the time being, __put_user()/__get_user() and friends only use
D-form addressing, with 0 offset. Ex:
lwz reg1, 0(reg2)
Give the compiler the opportunity to use other adressing modes
whenever possible, to get more optimised code.
Hereunder is a small exemple:
struct test {
On Mon, 10 Aug 2020 12:27:32 +1000
Nicholas Piggin wrote:
> On platforms that define HAVE_ARCH_HUGE_VMAP and support PMD vmaps,
> vmalloc will attempt to allocate PMD-sized pages first, before falling
> back to small pages.
>
> Allocations which use something other than PAGE_KERNEL protections a
The SPMI core complaing with this warning when built with W=1:
drivers/spmi/spmi.c: In function ‘spmi_controller_remove’:
drivers/spmi/spmi.c:548:6: warning: variable ‘dummy’ set but not used
[-Wunused-but-set-variable]
548 | int dummy;
| ^
As th
individul -> individual
Signed-off-by: Mauro Carvalho Chehab
---
drivers/mfd/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index a37d7d171382..e42d11849947 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -493,7
(+cc clang-built-linux)
On Sat, Aug 1, 2020 at 6:21 AM Peter Kalauskas wrote:
>
> Add support for builds that use an output directory different than the
> kernel source tree (e.g. make O=/tmp/kernel-obj). This also introduces
> support for .cmd files that use absolute paths.
>
> Previously, gen_
This patchset introduces support for LiteX SoC Controller
and LiteUART - serial device from LiteX SoC builder
(https://github.com/enjoy-digital/litex).
In the following patchset I will add
a new mor1kx-based (OpenRISC) platform that
uses this device.
Later I plan to extend this platform by
adding
Kees,
> Was a Coccinelle script used for any of these conversions? I wonder if
> it'd be easier to do a single treewide patch for the more mechanical
> changes.
No, I should have written one. Will do it.
> And, actually, I still think the "prepare" patches should just be
> collapsed into the act
Le 08/07/2020 à 06:49, Christophe Leroy a écrit :
Le 07/07/2020 à 21:02, Christophe Leroy a écrit :
Le 07/07/2020 à 14:44, Christophe Leroy a écrit :
Le 30/06/2020 à 03:19, Michael Ellerman a écrit :
Michael Ellerman writes:
Christophe Leroy writes:
Hi Michael,
I see this patch i
From: Filip Kokosinski
Add vendor prefix for LiteX SoC builder.
Signed-off-by: Filip Kokosinski
Signed-off-by: Mateusz Holenko
Acked-by: Rob Herring
---
Notes:
No changes in v10.
No changes in v9.
No changes in v8.
No changes in v7.
No changes in v6.
No changes i
From: Pawel Czarnecki
Add documentation for LiteX SoC Controller bindings.
Signed-off-by: Pawel Czarnecki
Signed-off-by: Mateusz Holenko
Reviewed-by: Rob Herring
---
Notes:
No changes in v10.
Changes in v9:
- fixed the `reg` node notation in the DT example
No changes in
From: Pawel Czarnecki
This commit adds driver for the FPGA-based LiteX SoC
Controller from LiteX SoC builder.
Co-developed-by: Mateusz Holenko
Signed-off-by: Mateusz Holenko
Signed-off-by: Pawel Czarnecki
---
Notes:
Changes in v10:
- added casting to avoid sparse warnings in the SoC
From: Filip Kokosinski
Add documentation for LiteUART devicetree bindings.
Signed-off-by: Filip Kokosinski
Signed-off-by: Mateusz Holenko
Reviewed-by: Rob Herring
---
Notes:
No changes in v10.
No changes in v9.
No changes in v8.
No changes in v7.
Changes in v6:
-
From: Filip Kokosinski
This commit adds driver for the FPGA-based LiteUART serial controller
from LiteX SoC builder.
The current implementation supports LiteUART configured
for 32 bit data width and 8 bit CSR bus width.
It does not support IRQ.
Signed-off-by: Filip Kokosinski
Signed-off-by: M
laurent,
please see the reply inline below.
On Wed, Aug 12, 2020 at 3:24 PM Laurent Pinchart
wrote:
>
> Hi Vinay,
>
> Thank you for the patch.
>
> On Wed, Aug 12, 2020 at 12:55:50PM +0530, Vinay Simha BN wrote:
> > - bus formats read from drm_bridge_state.output_bus_cfg.format
> > and .atomic_
On Wed, Aug 12, 2020 at 1:28 PM Karel Zak wrote:
> The proposal is based on paths and open(), how do you plan to deal
> with mount IDs? David's fsinfo() allows to ask for mount info by mount
> ID and it works well with mount notification where you get the ID. The
> collaboration with notification
Am 12.08.20 um 10:21 schrieb Markus Heiser:
Am 12.08.20 um 09:30 schrieb Salvatore Bonaccorso:
[..]
The problem is actually related to changes happening in Sphinx 3.0.0.
There is the followign issue filled upstream:
https://github.com/sphinx-doc/sphinx/issues/7421
'c_funcptr_sig_re' was rem
Hi Linus,
Please pull the watchdog changes for the v5.2 release cycle.
This series contains:
* f71808e_wdt imporvements
* dw_wdt improvements
* mlx-wdt: support new watchdog type with longer timeout period
* fallthrough pseudo-keyword replacements
* overall small fixes and improvements
The outpu
Em Fri, Aug 07, 2020 at 01:32:41PM -0600, Rob Herring escreveu:
> Fix various typos and inconsistent capitalization of CPU in the libperf
> man pages.
Thanks, applied,
- Arnaldo
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Arnaldo Carvalho de Melo
> Cc: Mark Rutland
> Cc: Alexander Shishkin
Em Fri, Aug 07, 2020 at 01:32:25PM -0600, Rob Herring escreveu:
> Commit 3ce311afb558 ("libperf: Move to tools/lib/perf") moved libperf
> out of tools/perf/, but failed to update MAINTAINERS.
Thanks, applied.
- Arnaldo
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Arnaldo Carvalho de Melo
> C
Hi Avri, Bean,
On Tue, 2020-08-11 at 16:18 +0200, Bean Huo wrote:
> From: Stanley Chu
>
> If somehow no interrupt notification is raised for a completed request
> and its doorbell bit is cleared by host, UFS driver needs to cleanup
> its outstanding bit in ufshcd_abort(). Otherwise, system may b
Hi,
I've repeatedly stared at an SD flag and asked myself "how should that be
set up in the domain hierarchy anyway?". I figured that if we formalize our
flags zoology a bit, we could also do some runtime assertions on them -
this is what this series is all about.
Patches
===
The idea is to
There are some expectations regarding how sched domain flags should be laid
out, but none of them are checked or asserted in
sched_domain_debug_one(). After staring at said flags for a while, I've
come to realize there's two repeating patterns:
- Shared with children: those flags are set from the
SD_PREFER_SIBLING is currently considered in sd_parent_degenerate() but not
in sd_degenerate(). It too hinges on load balancing, and thus won't have
any effect when set on a domain with a single group. Add it to
SD_DEGENERATE_GROUPS_MASK.
Signed-off-by: Valentin Schneider
---
include/linux/sched
This flag was introduced in 2014 by commit
d77b3ed5c9f8 ("sched: Add a new SD_SHARE_POWERDOMAIN for sched_domain")
but AFAIA it was never leveraged by the scheduler. The closest thing I can
think of is EAS caring about frequency domains, and it does that by
leveraging performance domains.
Remo
Even if no mainline topology uses this flag, it is a load balancing flag
just like SD_BALANCE_FORK and requires 2+ groups to have any effect.
Signed-off-by: Valentin Schneider
---
include/linux/sched/sd_flags.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/s
To associate the SD flags with some metadata, we need some more structure
in the way they are declared.
Rather than shove that in a free-standing macro list, move the declaration
in a separate file that can be re-imported with different SD_FLAG
definitions. This is inspired by what is done with th
There would be no point in preserving a sched_domain with a single group
just because it has this flag set. Add it to SD_DEGENERATE_GROUPS_MASK.
Signed-off-by: Valentin Schneider
---
include/linux/sched/sd_flags.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linu
Decoding the output of /proc/sys/kernel/sched_domain/cpu*/domain*/flags has
always been somewhat annoying, as one needs to go fetch the bit -> name
mapping from the source code itself. This encoding can be saved in a script
somewhere, but that isn't safe from flags being added, removed or even
shuf
In preparation of cleaning up the sd_degenerate*() functions, mark flags
used in sd_degenerate() with the new SDF_NEEDS_GROUPS flag. With this,
build a compile-time mask of those SD flags.
Note that sd_parent_degenerate() uses an extra flag in its mask,
SD_PREFER_SIBLING, which remains singled out
Being a load-balancing flag, it requires 2+ groups to have any effect.
Signed-off-by: Valentin Schneider
---
include/linux/sched/sd_flags.h | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/include/linux/sched/sd_flags.h b/include/linux/sched/sd_flags.h
index 6eb30252865
Now that we have some description of what we expect the flags layout to
be, we can use that to assert at runtime that the actual layout is sane.
Reviewed-by: Dietmar Eggemann
Signed-off-by: Valentin Schneider
---
kernel/sched/topology.c | 17 +
1 file changed, 17 insertions(+)
There would be no point in preserving a sched_domain with a single group
just because it has this flag set. Add it to SD_DEGENERATE_GROUPS_MASK.
Signed-off-by: Valentin Schneider
---
include/linux/sched/sd_flags.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/inclu
Leverage SD_DEGENERATE_GROUPS_MASK in sd_degenerate() and
sd_parent_degenerate().
Suggested-by: Peter Zijlstra
Signed-off-by: Valentin Schneider
---
kernel/sched/topology.c | 20
1 file changed, 4 insertions(+), 16 deletions(-)
diff --git a/kernel/sched/topology.c b/kernel
While preparing to port the HiSilicon 6421v600 SPMI driver,
I noticed some coding style issues at the SPMI core.
Address them.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/spmi/spmi.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/spmi/spmi.c b/drivers/spmi/
All SD flags requiring 2+ sched_group to have any effect are now decorated
with the SDF_NEEDS_GROUPS metaflag. This means we can now use the bitwise
negation of SD_DEGENERATE_MASK in sd_degenerate() instead of explicitly
using SD_WAKE_AFFINE (IOW the only flag without SDF_NEEDS_GROUPS).
>From now
The ARM-specific GMC level is meant to be built using the thread sibling
mask, but no devicetree in arch/arm/boot/dts uses the 'thread' cpu-map
binding. With SD_SHARE_POWERDOMAIN gone, this topology level can be
removed, at which point ARM no longer benefits from having a custom defined
topology ta
We currently set this flag *only* on domains whose topology level exactly
match the level where we detect asymmetry (as returned by
asym_cpu_capacity_level()). This is rather problematic.
Say there are two clusters in the system, one with a lone big CPU and the
other with a mix of big and LITTLE C
If there is only a single NUMA node in the system, the only NUMA topology
level that will be generated will be NODE (identity distance), which
doesn't have SD_SERIALIZE.
This means we don't need this special case in sd_parent_degenerate(), as
having the NODE level "naturally" covers it. Thus, remo
A sched_domain can only have overlapping sched_groups if it has more than
one group.
Signed-off-by: Valentin Schneider
---
include/linux/sched/sd_flags.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/sched/sd_flags.h b/include/linux/sched/sd_flags.h
index f8
Em Wed, Aug 12, 2020 at 09:15:04AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Aug 12, 2020 at 02:59:53PM +0800, Jin Yao escreveu:
> > Currently if we run 'perf record -e cycles:u', exclude_guest is 0.
> >
> > But it doesn't make sense that we request for user-space counting
> > but we als
On 2020/8/12 19:32, Paolo Bonzini wrote:
On 12/08/20 13:11, pet...@infradead.org wrote:
x86 does not have a hypervisor privilege level, so it never uses
Arguably it does when Xen, but I don't think we support that, so *phew*.
Yeah, I suppose you could imagine having paravirtualized perf counte
On Wed, Aug 12, 2020 at 12:40:05PM +0200, pet...@infradead.org wrote:
> On Wed, Aug 12, 2020 at 10:56:56AM +0200, Ard Biesheuvel wrote:
> > The module .lds has BYTE(0) in the section contents to prevent the
> > linker from pruning them entirely. The (NOLOAD) is there to ensure
> > that this byte do
syzbot reported this issue where in the vsock_poll() we find the
socket state at TCP_ESTABLISHED, but 'transport' is null:
general protection fault, probably for non-canonical address
0xdc12: [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0090-0x0
Hi Sebastian,
any progress on your side?
Do you think the patch could be applied for the next versions?
Regards,
Thomas
On Fri, 2020-07-10 at 10:59 +, Thomas Graziadei wrote:
> Hi Sebastian,
>
> thanks for looking into this.
>
> We could reproduce the issue with QEMU.
> At runtime you nee
On 2020/8/12 20:15, Arnaldo Carvalho de Melo wrote:
Em Wed, Aug 12, 2020 at 02:59:53PM +0800, Jin Yao escreveu:
Currently if we run 'perf record -e cycles:u', exclude_guest is 0.
But it doesn't make sense that we request for user-space counting
but we also get the guest report.
Please hold t
On Mon, 10 Aug 2020 at 10:06, Marco Elver wrote:
> Remove kcsan_counter_inc/dec() functions, as they perform no other
> logic, and are no longer needed.
>
> This avoids several calls in kcsan_setup_watchpoint() and
> kcsan_found_watchpoint(), as well as lets the compiler warn us about
> potential
This patch fixs eMMC-Access on mt7622/Bpi-64.
Before we got these Errors on mounting eMMC ion R64:
[ 48.664925] blk_update_request: I/O error, dev mmcblk0, sector 204800 op
0x1:(WRITE)
flags 0x800 phys_seg 1 prio class 0
[ 48.676019] Buffer I/O error on dev mmcblk0p1, logical block 0, lost syn
Add description for resets/reset-names.
Signed-off-by: Wenbin Mei
---
Documentation/devicetree/bindings/mmc/mtk-sd.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mtk-sd.txt
b/Documentation/devicetree/bindings/mmc/mtk-sd.txt
index 8a532f4453f2..15
This commit adds reset node for mmc device.
Fixes: 966580ad236e ("mmc: mediatek: add support for MT7622 SoC")
Signed-off-by: Wenbin Mei
Tested-by: Frank Wunderlich
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7
--
2.18.0
On 12/08/20 14:56, Xu, Like wrote:
>
> My proposal is to define:
> the "hypervisor privilege levels" events in the KVM/x86 context as
> all the host kernel events plus /dev/kvm user space events.
What are "/dev/kvm user space events"? In any case, this patch should
be included only in the series
On Wed, Aug 12, 2020 at 9:53 AM Álvaro Fernández Rojas
wrote:
>
> There's no EHCI controller on BCM6348.
>
> Signed-off-by: Álvaro Fernández Rojas
> Acked-by: Florian Fainelli
v3 already reviewed, again:
Reviewed-by: Philippe Mathieu-Daudé
> ---
> v4: no changes.
> v3: no changes.
> v2: no
Thanks for your reply.
I have changed this in v2 patch.
On Wed, 2020-08-12 at 14:03 +0200, Philipp Zabel wrote:
> On Wed, 2020-08-12 at 17:37 +0800, Wenbin Mei wrote:
> > Add description for resets/reset-names.
> >
> > Signed-off-by: Wenbin Mei
> > ---
> > Documentation/devicetree/bindings/mmc/m
On Wed, Aug 12, 2020 at 9:53 AM Álvaro Fernández Rojas
wrote:
>
> BCM6358 SoCs have OHCI and EHCI controllers that share the same USB ports.
> Therefore, the board should also have EHCI enabled.
>
> Signed-off-by: Álvaro Fernández Rojas
> Acked-by: Florian Fainelli
v3 already reviewed, again:
R
On Tue, Aug 11, 2020 at 10:49:30AM -0600, Rob Herring wrote:
> On Tue, Aug 11, 2020 at 4:50 AM Jiri Olsa wrote:
> >
> > On Mon, Aug 10, 2020 at 12:11:23PM -0600, Rob Herring wrote:
> > > On Sat, Aug 8, 2020 at 4:22 AM Jiri Olsa wrote:
> > > >
> > > > On Fri, Aug 07, 2020 at 05:05:17PM -0600, Rob
Miklos Szeredi wrote:
> That presumably means the mount ID <-> mount path mapping already
> exists, which means it's just possible to use the open(mount_path,
> O_PATH) to obtain the base fd.
No, you can't. A path more correspond to multiple mounts stacked on top of
each other, e.g.:
m
On Wed, Aug 12, 2020 at 12:14 PM Karel Zak wrote:
> For example, by fsinfo(FSINFO_ATTR_MOUNT_TOPOLOGY) you get all
> mountpoint propagation setting and relations by one syscall,
That's just an arbitrary grouping of attributes.
You said yourself, that what's really needed is e.g. consistent
sna
On 2020/8/12 21:04, Paolo Bonzini wrote:
On 12/08/20 14:56, Xu, Like wrote:
My proposal is to define:
the "hypervisor privilege levels" events in the KVM/x86 context as
all the host kernel events plus /dev/kvm user space events.
What are "/dev/kvm user space events"? In any case, this patch sh
On Wed, Aug 12, 2020 at 4:42 AM Jessica Yu via Binutils
wrote:
>
> +++ pet...@infradead.org [12/08/20 12:40 +0200]:
> >On Wed, Aug 12, 2020 at 10:56:56AM +0200, Ard Biesheuvel wrote:
> >> The module .lds has BYTE(0) in the section contents to prevent the
> >> linker from pruning them entirely. The
On Wed, 12 Aug 2020 10:21:40 +0200
Markus Heiser wrote:
> @jon, do you have time to implement a patch?
> .. sorry, I'am in a hurry :o
This is on my list ... but life is busy at the moment. I would not be
distressed if somebody beat me to it.
jon
Hi Vinay,
On Wed, Aug 12, 2020 at 06:07:52PM +0530, Vinay Simha B N wrote:
> On Wed, Aug 12, 2020 at 3:24 PM Laurent Pinchart wrote:
> > On Wed, Aug 12, 2020 at 12:55:50PM +0530, Vinay Simha BN wrote:
> > > - bus formats read from drm_bridge_state.output_bus_cfg.format
> > > and .atomic_get_inpu
While testng LTP CVE cve-2017-17053 test case the kernel BUG triggered
on qemu_i386.
Not easily reproducible BUG.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: 4c9b89d8981be3b9032f94d0c4dc7eb9c7967a32
git describe: ne
On Wed, Aug 12, 2020 at 09:01:26PM +0800, Wenbin Mei wrote:
> --
> 2.18.0
I think something is wrong with your subject line :(
On Wed, Aug 12, 2020 at 09:01:28PM +0800, Wenbin Mei wrote:
> This commit adds reset node for mmc device.
>
> Fixes: 966580ad236e ("mmc: mediatek: add support for MT7622 SoC")
> Signed-off-by: Wenbin Mei
> Tested-by: Frank Wunderlich
> ---
> arch/arm64/boot/dts/mediatek/mt7622.dtsi | 2 ++
> 1
Thank you for your reply.
@@ -171,7 +174,9 @@ struct exfat_entry_set_cache {
unsigned int start_off;
int num_bh;
struct buffer_head *bh[DIR_CACHE_SIZE];
- unsigned int num_entries;
+ int num_entries;
+ struct exfat_de_file *de_file;
+ struct exfat_
On Wed, Aug 12, 2020 at 09:01:29PM +0800, Wenbin Mei wrote:
> This patch fixs eMMC-Access on mt7622/Bpi-64.
> Before we got these Errors on mounting eMMC ion R64:
> [ 48.664925] blk_update_request: I/O error, dev mmcblk0, sector 204800 op
> 0x1:(WRITE)
> flags 0x800 phys_seg 1 prio class 0
> [
On Wed, Aug 12, 2020 at 09:01:27PM +0800, Wenbin Mei wrote:
> Add description for resets/reset-names.
>
> Signed-off-by: Wenbin Mei
> ---
> Documentation/devicetree/bindings/mmc/mtk-sd.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/mtk-sd.tx
On 07.08.20 16:17, Sven Van Asbroeck wrote:
Hi,
> I believe you're asking: "how do I associate device tree nodes to
> devices on a dynamically discoverable bus such as USB or PCI" right ?
>
> I believe that already exists. You can describe the _expected_ pci or
> usb topology in the
> devicetree
On Wed, Aug 12, 2020 at 10:32:50AM +0200, Thomas Gleixner wrote:
> Paul,
>
> "Paul E. McKenney" writes:
> > On Wed, Aug 12, 2020 at 02:13:25AM +0200, Thomas Gleixner wrote:
> >> That much I understood, but I somehow failed to figure the why out
> >> despite the elaborate changelog. 2 weeks of 30+
Hi Algea,
On Wed, Aug 12, 2020 at 07:08:10PM +0800, crj wrote:
> 在 2020/8/12 17:33, Laurent Pinchart 写道:
> > On Wed, Aug 12, 2020 at 04:35:43PM +0800, Algea Cao wrote:
> >> Introduce struct dw_hdmi_property_ops in plat_data to support
> >> vendor hdmi property.
> >>
> >> Implement hdmi vendor prop
On Tue, Aug 04, 2020 at 07:44:42PM +0530, Gaurav Kohli wrote:
> In a system where no cpu's implement SSBS, for
> them no need to set pstate. This might help to save
> few cpu cycles during context switch.
>
> Signed-off-by: Gaurav Kohli
>
> diff --git a/arch/arm64/kernel/process.c b/arch/arm64/k
Add regmap_cache to reduce wakeups events of interrupt if regulator is
accessed frequently. This results in saving more power.
Suggested-by: Daniel Kurtz
Signed-off-by: Hsin-Yi Wang
---
drivers/regulator/da9211-regulator.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/driv
Miklos Szeredi wrote:
> You said yourself, that what's really needed is e.g. consistent
> snapshot of a complete mount tree topology. And to get the complete
> topology FSINFO_ATTR_MOUNT_TOPOLOGY and FSINFO_ATTR_MOUNT_CHILDREN are
> needed for *each* individual mount.
That's not entirely true.
On Wed, Aug 12, 2020 at 01:32:58PM +0200, Paolo Bonzini wrote:
> On 12/08/20 13:11, pet...@infradead.org wrote:
> > Right, but we want to tighten the permission checks and not excluding_hv
> > is just sloppy.
>
> I would just document that it's ignored as it doesn't make sense. ARM64
> does that
> From: Stefano Garzarella
> Sent: Wednesday, August 12, 2020 2:56 PM
> To: da...@davemloft.net
> Cc: linux-kernel@vger.kernel.org; Dexuan Cui ;
> net...@vger.kernel.org; Stefan Hajnoczi ; Jakub
> Kicinski ; Jorgen Hansen ;
> Stefano Garzarella
> Subject: [PATCH net v2] vsock: fix potential null
Hey Stephen,
Thanks for taking time to review the
series!
On 2020-08-12 03:08, Stephen Boyd wrote:
Quoting Sibi Sankar (2020-08-11 12:02:51)
diff --git a/include/linux/pm_domain.h b/include/linux/pm_domain.h
index ee11502a575b0..3002a2d68936a 100644
--- a/include/linux/pm_domain.h
+++ b/include
On Tue, Aug 11, 2020 at 09:24:10AM -0500, David Lechner wrote:
> On 8/9/20 1:54 PM, Alex Dewar wrote:
> > This battery appears only to be used by a single board (DA850), so it
> > makes sense to add this to the Kconfig file so that users don't build
> > the module unnecessarily. It currently seems
On Fri, 7 Aug 2020 at 04:02, Konrad Dybcio wrote:
>
> Subject: Re: [PATCH v4] arm64: dts: qcom: Add support for Xiaomi Poco F1
> (Beryllium)
>
> >// This removed_region is needed to boot the device
> > // TODO: Find out the user of this reserved memory
> > removed_regi
On 2020-08-11 06:27, Andrew Morton wrote:
> On Sat, 8 Aug 2020 08:03:38 +0800 kernel test robot wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> master
>> head: 30185b69a2d533c4ba6ca926b8390ce7de495e29
>> commit: 295bcca84916cb5079140a89fccb472bb8d1f6e2
On 8/10/2020 6:47 PM, Peter Zijlstra wrote:
On Mon, Aug 10, 2020 at 06:38:35PM -0400, Liang, Kan wrote:
On 8/10/2020 5:47 PM, Dave Hansen wrote:
It's probably best if we very carefully define up front what is getting
reported here. For instance, I believe we already have some fun cases
wi
Ping? Daniel, Dave any opinion on this?
Christian.
Am 07.08.20 um 15:36 schrieb Christian König:
Hi everybody,
in amdgpu we got the following issue which I'm seeking advise how to cleanly
handle it.
We have a bunch of trace points which are related to the VM subsystem and
executed in either
201 - 300 of 908 matches
Mail list logo
