02.10.2019 02:29, Chanwoo Choi пишет:
> On 19. 8. 12. 오전 6:23, Dmitry Osipenko wrote:
>> Now that all kHz-conversion related bugs are fixed, we can use the kHz
>> uniformly. This makes code cleaner and avoids integer divisions in the
>> code, which is useful in a case of Tegra30 that has Cortex A9
On Wed, Oct 2, 2019 at 6:25 PM John Garry wrote:
> On 02/10/2019 16:43, Arnd Bergmann wrote:
> > On Tue, Oct 1, 2019 at 6:07 PM John Garry wrote:
> >>
> >> Currently the driver will only ever be built for ARM64 because it selects
> >> CONFIG_INDIRECT_PIO, which itself depends on ARM64.
> >>
> >>
On Wed, Oct 02, 2019 at 06:35:26PM +0200, Daniel Bristot de Oliveira wrote:
> ftrace was already batching the updates, for instance, causing 3 IPIs to
> enable
> all functions. The text_poke() batching also works. But because of the limited
> buffer [ see the reply to the patch 2/3 ], it is
On Wed, Oct 02, 2019 at 12:18:54AM -0400, Bruce Ashfield wrote:
> On Tue, Oct 1, 2019 at 10:01 PM Roman Gushchin wrote:
> >
> > On Tue, Oct 01, 2019 at 12:14:18PM -0400, Bruce Ashfield wrote:
> > > Hi all,
> > >
> >
> > Hi Bruce!
> >
> > > The Yocto project has an upcoming release this fall, and
On Thu, Sep 26, 2019 at 7:17 PM Yang Weijiang wrote:
>
> CET MSRs pass through Guest directly to enhance performance.
> CET runtime control settings are stored in MSR_IA32_{U,S}_CET,
> Shadow Stack Pointer(SSP) are stored in MSR_IA32_PL{0,1,2,3}_SSP,
> SSP table base address is stored in
On Thu, Sep 26, 2019 at 01:56:55PM -0700, Kees Cook wrote:
> On Thu, Sep 26, 2019 at 01:06:01PM -0700, Linus Torvalds wrote:
> > (a) why didn't this use the already existing and well-named macro
> > that nobody really had issues with?
>
> That was suggested, but other folks wanted the more
On Thu, Sep 05, 2019 at 02:45:12PM +0200, Miroslav Benes wrote:
> Josh reported a bug:
>
> When the object to be patched is a module, and that module is
> rmmod'ed and reloaded, it fails to load with:
>
> module: x86/modules: Skipping invalid relocation target, existing value is
> nonzero
On Wed, Oct 2, 2019 at 3:27 AM Niklas Cassel wrote:
>
> On Wed, Oct 02, 2019 at 11:19:50AM +0200, Niklas Cassel wrote:
> > On Mon, Sep 30, 2019 at 04:20:15PM -0600, Jeffrey Hugo wrote:
> > > Amit, the merged version of the below change causes a boot failure
> > > (nasty hang, sometimes with RCU
On Wed, Oct 02, 2019 at 11:06:43AM -0700, Linus Torvalds wrote:
> On Wed, Oct 2, 2019 at 6:48 AM Thomas Hellström (VMware)
> wrote:
> >
> > From: Thomas Hellstrom
> >
> > Add two utilities to a) write-protect and b) clean all ptes pointing into
> > a range of an address space.
[...]
> Yes, it's
Hi Chia-Wei,
On 10/1/2019 11:11 PM, Chia-Wei, Wang wrote:
Update the Aspeed PECI driver with the AST2600 compatible string.
A new comptabile string is needed for the extended HW feature of
AST2600.
Chia-Wei, Wang (2):
peci: aspeed: Add AST2600 compatible string
dt-bindings: peci: aspeed:
On Wed, Oct 2, 2019 at 6:48 AM Thomas Hellström (VMware)
wrote:
>
> From: Thomas Hellstrom
>
> Add two utilities to a) write-protect and b) clean all ptes pointing into
> a range of an address space.
This one I still don't exactly love.
I'm not entirely sure what rubs me the wrong way, but
Hi!
> >>>diff --git a/Documentation/ABI/testing/sysfs-class-led
> >>>b/Documentation/ABI/testing/sysfs-class-led
> >>>index 5f67f7a..fdfed3f 100644
> >>>--- a/Documentation/ABI/testing/sysfs-class-led
> >>>+++ b/Documentation/ABI/testing/sysfs-class-led
> >>>@@ -61,3 +61,16 @@ Description:
> >>>
On Tue, Oct 01, 2019 at 09:11:51AM +0200, Christoph Hellwig wrote:
> Use the new iomap writeback code that was copied from XFS to perform
> writeback.
>
> Signed-off-by: Christoph Hellwig
> [darrick: reduce this patch only to convert the xfs writeback code]
> Signed-off-by: Darrick J. Wong
>
On Thu, Sep 26, 2019 at 7:17 PM Yang Weijiang wrote:
>
> CET(Control-flow Enforcement Technology) is an upcoming Intel(R)
> processor feature that blocks Return/Jump-Oriented Programming(ROP)
> attacks. It provides the following capabilities to defend
> against ROP/JOP style control-flow
Hi!
> Reading /sys/class/leds//trigger returns all available LED triggers.
> However, this violates the "one value per file" rule of sysfs.
>
> This series provides a new /sys/devices/virtual/led-trigger/ directory and
> /sys/class/leds//current-trigger. The new api follows the "one value
> per
Hi all.
On 10/2/19 5:21 PM, Gonsolo wrote:
Hi!
Antti has some great suggestions in that thread:
https://lkml.org/lkml/2017/5/24/245
Also note https://lkml.org/lkml/2017/5/26/357 if you have access to a
logic analyser.
I read that thread. Unfortunately I'm not a hardware engineer
Jacek
On 10/2/19 12:46 PM, Jacek Anaszewski wrote:
Dan,
On 10/2/19 5:47 PM, Dan Murphy wrote:
Akinobu
On 10/2/19 10:13 AM, Akinobu Mita wrote:
Reading /sys/class/leds//trigger returns all available LED triggers.
However, this violates the "one value per file" rule of sysfs.
This provides
On Wed, Oct 2, 2019 at 6:47 AM Thomas Hellström (VMware)
wrote:
>
> From: Thomas Hellstrom
>
> For users that want to travers all page table entries pointing into a
> region of a struct address_space mapping, introduce a walk_page_mapping()
> function.
This looks non-offensive to me.
My main
Hi Geert,
On Wed, Oct 02, 2019 at 11:17:26AM +0200, Geert Uytterhoeven wrote:
> > 15 error regressions:
> > + /kisskb/build/tmp/cc1Or5dj.s: Error: can't resolve `_start' {*UND*
> > section} - `L0 ' {.text section}: => 663, 1200, 222, 873, 1420
> > + /kisskb/build/tmp/cc2uWmof.s: Error:
From: KP Singh
Rename asm_goto_workaround.h to asm_workaround.h and add a
workaround for the newly added "asm_inline" in:
commit eb111869301e ("compiler-types.h: add asm_inline definition")
Add missing include for which was removed from
perf-sys.h in:
commit 91854f9a077e ("perf tools:
Dan,
On 10/2/19 5:47 PM, Dan Murphy wrote:
> Akinobu
>
> On 10/2/19 10:13 AM, Akinobu Mita wrote:
>> Reading /sys/class/leds//trigger returns all available LED triggers.
>> However, this violates the "one value per file" rule of sysfs.
>>
>> This provides /sys/class/leds//current-trigger which
After adding the interrupt properties to Exynos5422 DMC bindings
example, the mapped memory region must be big enough to access
performance counters registers.
Fix also syntax errors (semicolons) and adjust indentation.
Signed-off-by: Krzysztof Kozlowski
---
Rebased on top of my for-next
On 02/10/2019 18:26, Masahiro Yamada wrote:
> On Thu, Oct 3, 2019 at 2:24 AM David Miller wrote:
>>
>> From: Guillaume Tucker
>> Date: Wed, 2 Oct 2019 18:21:31 +0100
>>
>>> It seems like this isn't the case on the Raspberry Pi 2b with
>>> bcm2835_defconfig. Here's an example of the kernel
The result variable in prism2_connect() can be used uninitialized on path
!channel --> ... --> is_wep --> sme->key --> sme->key_idx >= NUM_WEPKEYS.
This patch initializes result with 0.
Cc: Greg Kroah-Hartman
Cc: sta...@vger.kernel.org
Signed-off-by: Denis Efremov
---
The driver does not use polling mode of input devices, and this config
option is going away, so let's not reference it.
Signed-off-by: Dmitry Torokhov
---
drivers/platform/x86/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
On Wed, Oct 02, 2019 at 08:04:55AM +0200, Lukasz Luba wrote:
> Introduce a new interrupt driven mechanism for managing speed of the
> memory controller. The interrupts are generated due to performance
> counters overflow. The performance counters might track memory reads,
> writes, transfers, page
On Wed, Oct 02, 2019 at 09:35:51AM -0500, Dinh Nguyen wrote:
> With commit "79bdcb202a35 ARM: 8906/1: drivers/amba: add reset control to
> amba bus probe", the amba bus driver needs to be deferred probe because the
> reset driver is probed later. However with a deferred probe, the call to
>
On 10/2/19 1:43 AM, Michal Hocko wrote:
On Wed 02-10-19 06:16:43, Yang Shi wrote:
The commit 87eaceb3faa59b9b4d940ec9554ce251325d83fe ("mm: thp: make
deferred split shrinker memcg aware") makes deferred split queue per
memcg to resolve memcg pre-mature OOM problem. But, all nodes end up
On Wed, Oct 02, 2019 at 08:04:54AM +0200, Lukasz Luba wrote:
> There is a need to access registers at address offset near 0x1.
> These registers are private DMC performance counters, which might be used
> as interrupt trigger when overflow. Potential usage is to skip polling
> in devfreq
On Thu, Oct 3, 2019 at 2:24 AM David Miller wrote:
>
> From: Guillaume Tucker
> Date: Wed, 2 Oct 2019 18:21:31 +0100
>
> > It seems like this isn't the case on the Raspberry Pi 2b with
> > bcm2835_defconfig. Here's an example of the kernel errors:
>
> This has been fixed upstream I believe, it
On 10/2/19 1:40 AM, Michal Hocko wrote:
On Wed 02-10-19 07:56:50, Yang Shi wrote:
The deferred split THPs may get accumulated with some workloads, they
would get shrunk when memory pressure is hit. Now we use DEFAULT_SEEKS
to determine how many objects would get scanned then split if
On Thu, Sep 26, 2019 at 7:17 PM Yang Weijiang wrote:
>
> The control bits in IA32_XSS MSR are being used for new features,
> but current CPUID(0xd,i) enumeration code doesn't support them, so
> fix existing code first.
>
> The supervisor states in IA32_XSS haven't been used in public
> KVM code,
On Wed, Oct 02, 2019 at 08:04:53AM +0200, Lukasz Luba wrote:
> Add interrupt to Dynamic Memory Controller in Exynos5422 and Odroid
> XU3-family boards. It will be used instead of devfreq polling mode
> governor. The interrupt is connected to performance counters private
> for DMC, which might
From: Guillaume Tucker
Date: Wed, 2 Oct 2019 18:21:31 +0100
> It seems like this isn't the case on the Raspberry Pi 2b with
> bcm2835_defconfig. Here's an example of the kernel errors:
This has been fixed upstream I believe, it was some ARM assembler issue
or something like that.
In any
On Wed, Oct 02, 2019 at 08:04:52AM +0200, Lukasz Luba wrote:
> Add description for optional interrupt lines. It provides a new operation
> mode, which uses internal performance counters interrupt when overflow.
> This is more reliable than using default polling mode implemented in
> devfreq.
>
>
Denis Efremov wrote:
> memcpy() in wmi_set_ie() and wmi_update_ft_ies() is called with
> src == NULL and len == 0. This is an undefined behavior. Fix it
> by checking "ie_len > 0" before the memcpy() calls.
>
> As suggested by GCC documentation:
> "The pointers passed to memmove (and similar
Denis Efremov wrote:
> memcpy() call with "idata == NULL && ilen == 0" results in undefined
> behavior in ar5523_cmd(). For example, NULL is passed in callchain
> "ar5523_stat_work() -> ar5523_cmd_write() -> ar5523_cmd()". This patch
> adds ilen check before memcpy() call in ar5523_cmd() to
On 02/10/2019 11:05, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation has been done
On Mon, Sep 30, 2019 at 08:44:39PM +0800, Zhenzhong Duan wrote:
> Includes asm/hypervisor.h in order to reference x86_hyper_type.
>
> Signed-off-by: Zhenzhong Duan
> Cc: Jonathan Corbet
> Cc: "K. Y. Srinivasan"
> Cc: Haiyang Zhang
> Cc: Stephen Hemminger
> Cc: Sasha Levin
> Cc: Thomas
On Wed, Aug 21, 2019 at 12:43:03PM +0200, Lukasz Luba wrote:
> Enable driver for Exynos5422 Dynamic Memory Controller supporting
> dynamic frequency and voltage scaling in Exynos5422 SoCs.
>
> Signed-off-by: Lukasz Luba
> ---
> arch/arm/configs/exynos_defconfig | 1 +
Thanks, applied.
Best
On Mon, Sep 30, 2019 at 08:44:38PM +0800, Zhenzhong Duan wrote:
> Fix stale description of "xen_nopvspin" as we use qspinlock now.
>
> Signed-off-by: Zhenzhong Duan
> Reviewed-by: Juergen Gross
> Cc: Jonathan Corbet
> Cc: Boris Ostrovsky
> Cc: Juergen Gross
> Cc: Stefano Stabellini
> Cc:
The id pointer can be NULL in rsi_probe(). It is checked everywhere except
for the else branch in the idProduct condition. The patch adds NULL check
before the id dereference in the rsi_dbg() call.
Fixes: 54fdb318c111 ("rsi: add new device model for 9116")
Cc: Amitkumar Karwar
Cc: Siva
On Mon, Sep 30, 2019 at 08:44:37PM +0800, Zhenzhong Duan wrote:
> pr_*() is preferred than printk(KERN_* ...), after change all the print
> in arch/x86/kernel/kvm.c will have "KVM: xxx" style.
>
> No functional change.
>
> Suggested-by: Vitaly Kuznetsov
This wasn't really suggested by Vitaly,
Hello,
Let us repair your phone or gadget right on the spot
visit us today
https://www.justrepair.net
or come into our location
https://goo.gl/maps/k5iRbeJyggiXnZSG6
Give us a nice review and we`ll make you a big discount
Thank you,
Ameer
On Mon, Sep 30, 2019 at 08:44:36PM +0800, Zhenzhong Duan wrote:
> There are cases where a guest tries to switch spinlocks to bare metal
> behavior (e.g. by setting "xen_nopvspin" on XEN platform and
> "hv_nopvspin" on HYPER_V).
>
> That feature is missed on KVM, add a new parameter "nopvspin" to
On 10/2/19 5:40 AM, Marc Zyngier wrote:
> On Tue, 1 Oct 2019 15:48:40 -0700
> Florian Fainelli wrote:
>
>> The root interrupt controller on 7211 is about identical to the one
>> existing on BCM2836, except that the SMP cross call are done through the
>> standard ARM GIC-400 interrupt
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent
for you to fetch changes up to
The kernel command line option efivar_ssdt= allows the name to be
specified of an EFI variable containing an ACPI SSDT table that should
be loaded into memory by the OS, and treated as if it was provided by
the firmware.
Currently, that code will always iterate over the EFI variables and
compare
Hi,
As OpenSSL, we want cryptograhic secure random numbers. Before
getrandom(), Linux never provided a good API for that, both
/dev/random and /dev/urandom have problems. getrandom() fixed
that, so we switched to it were available.
It was possible to combine /dev/random and /dev/urandom, and get
From: Bartosz Golaszewski
There's no need to emit an error message on probe failure unless we're
printing some meaningful info. Otherwise the core driver code will
inform us about a probe error.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-xgene.c | 23 +++
1
From: Bartosz Golaszewski
There's no need to use the nocache variant of ioremap(). Switch to
using devm_platform_ioremap_resource().
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-em.c | 20
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git
On Wed, Oct 02, 2019 at 01:45:30PM +0300, Jarkko Sakkinen wrote:
> As has been seen recently, binding the buffer allocation and tpm_buf
> together is sometimes far from optimal. The buffer might come from the
> caller namely when tpm_send() is used by another subsystem. In addition we
> can
From: Bartosz Golaszewski
There's no need to use the nocache variant of ioremap(). Switch to
using devm_platform_ioremap_resource().
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-xgene.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git
From: Bartosz Golaszewski
There's no need to emit an error message on probe failure unless we're
printing some meaningful info. Otherwise the core driver code will
inform us about a probe error. Also: the driver currently drops info
about errors propagated from called functions by default to
From: Bartosz Golaszewski
There's no need to use the nocache variant of ioremap(). Switch to
using devm_platform_ioremap_resource().
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-htc-egpio.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git
From: Bartosz Golaszewski
There's no need to use the nocache variant of ioremap(). Switch to
using devm_platform_ioremap_resource().
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-ath79.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git
From: Bartosz Golaszewski
According to Arnd Bergmann:
"The only architecture that actually has a difference between
ioremap() and ioremap_nocache() seems to be ia64. I would
generally assume that any driver using ioremap_nocache()
that is not ia64 specific should just use ioremap()."
This
Thanks David,
On Wed, Oct 2, 2019 at 4:22 AM David Sterba wrote:
>
> On Mon, Sep 30, 2019 at 04:01:10PM -0500, Navid Emamdoost wrote:
> > In affs_remount if data is provided it is duplicated into new_opts.
> > The allocated memory for new_opts is only released if pare_options fail.
> > The
On Wed, Oct 02, 2019 at 11:28:37AM -0400, Joel Fernandes (Google) wrote:
> Quite interested in the LKMM, I have submitted patches before and used
> it a lot. I would like to be a part of the maintainers for this project.
>
> Cc: Paul McKenney
> Suggested-by: Alan Stern
> Signed-off-by: Joel
On Wed, Oct 02, 2019 at 01:32:07PM +0800, Kai-Heng Feng wrote:
> On Oct 2, 2019, at 08:07, Bjorn Helgaas wrote:
> > On Mon, Sep 02, 2019 at 10:52:52PM +0800, Kai-Heng Feng wrote:
> >> There's an xHCI device that doesn't wake when a USB 2.0 device gets
> >> plugged to its USB 3.0 port. The
On Tue, Oct 1, 2019 at 5:55 PM Jens Axboe wrote:
>
> On 10/1/19 5:12 PM, Song Liu wrote:
> > On Fri, Sep 20, 2019 at 8:58 AM Eugene Syromiatnikov
> > wrote:
> >>
> >> Hello.
> >>
> >> This is a small fix of a typo (or, more specifically, some remnant of
> >> the old patch version spelling) in
Hi Mika,
> -Original Message-
> From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com]
> Sent: Tuesday, October 01, 2019 4:38 AM
> To: linux-...@vger.kernel.org
> Cc: Andreas Noever ; Jamet, Michael
> ; Mika Westerberg
> ; Yehezkel Bernat
> ; Mani, Rajmohan ;
> Nicholas Johnson ;
On Wednesday 2 October 2019 18:42:14 CEST Greg Kroah-Hartman wrote:
> On Wed, Oct 02, 2019 at 04:29:09PM +, Jerome Pouiller wrote:
[...]
> >
> > Hi Andrew,
> >
> > I did not forget your suggestion. However, if everyone is agree with that,
> > I'd
> > prefer to address it in a next pull
On Tue, Oct 01, 2019 at 05:47:00PM +0800, Zhenzhong Duan wrote:
>
> On 2019/10/1 16:39, Vitaly Kuznetsov wrote:
> >Zhenzhong Duan writes:
> >
> >>On 2019/9/30 23:41, Vitaly Kuznetsov wrote:
> >>>Zhenzhong Duan writes:
> >>>
> There are cases where a guest tries to switch spinlocks to bare
From: Andi Kleen
The original --reltime patch forbid --time with --reltime.
But it turns out --time doesn't really care about --reltime, because
the relative time is only used at final output, while
the time filtering always works earlier on absolute time.
So just remove the check and allow
Hi Giovanni,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option
The device node name should reflect generic class of a device so rename
the "msmram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/keystone-k2e.dtsi | 2 +-
arch/arm/boot/dts/keystone-k2g.dtsi
The device node name should reflect generic class of a device so rename
the "ocmcram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/omap4.dtsi | 2 +-
arch/arm/boot/dts/omap5.dtsi | 2 +-
2
The device node name should reflect generic class of a device so rename
the "ocmcram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/am33xx.dtsi | 2 +-
arch/arm/boot/dts/am4372.dtsi | 2 +-
2
The device node name should reflect generic class of a device so rename
the "sa-sram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/dove.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
The device node name should reflect generic class of a device so rename
the "iram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/tegra20.dtsi | 2 +-
arch/arm/boot/dts/tegra30.dtsi | 2 +-
2
The device node name should reflect generic class of a device so rename
the "sysram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 2 +-
The device node name should reflect generic class of a device so rename
the SysRAM node from "sysram" to "sram". The child nodes stay as before
as "smp-sysram" to match their real purpose. This will be also in sync
with upcoming DT schema. No functional change.
Signed-off-by: Krzysztof
The device node name should reflect generic class of a device so rename
the "iram" node to "sram". This will be also in sync with upcoming DT
schema. No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/imx27.dtsi | 2 +-
arch/arm/boot/dts/imx31.dtsi | 2 +-
Convert generic mmio-sram bindings to DT schema format using
json-schema. Require the address/size cells to be 1, not equal to root
node.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v2:
1. Add Rob as maintainer,
2. Use "contains" for compatible,
3. Fix address and size cells to 1,
4.
Convert Samsung Exynos SYSRAM bindings to DT schema format using
json-schema.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v2:
1. Use sram as name of node in example.
Changes since v1:
1. Indent example with four spaces (more readable).
---
On Wed, Oct 02, 2019 at 04:29:09PM +, Jerome Pouiller wrote:
> On Thursday 19 September 2019 18:34:48 CEST Andrew Lunn wrote:
> > On Thu, Sep 19, 2019 at 10:52:35AM +, Jerome Pouiller wrote:
> > > +static int wfx_sdio_copy_from_io(void *priv, unsigned int reg_id,
> > > +
Chris Chiu writes:
> On Wed, Oct 2, 2019 at 12:29 PM Kalle Valo wrote:
>
>> Failed to apply, please rebase on top of wireless-drivers-next.
>>
>> fatal: sha1 information is lacking or useless
>> (drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h).
>> error: could not build fake ancestor
>>
On 27/08/2019 20:06, Peter Zijlstra wrote:
> Move ftrace over to using the generic x86 text_poke functions; this
> avoids having a second/different copy of that code around.
>
> This also avoids ftrace violating the (new) W^X rule and avoids
> fragmenting the kernel text page-tables, due to no
Hi Peter,
On 27/08/2019 20:06, Peter Zijlstra wrote:
> Adding another text_poke_bp_batch() user made me realize the interface
> is all sorts of wrong. The text poke vector should be internal to the
> implementation.
>
> This then results in a trivial interface:
>
> text_poke_queue() - which
The LED_COLOR_MAX_ID is incorrect. THe MAX_ID should
be the last COLOR_ID in the list. If an array was allocate
with MAX_ID the allocation would be correct but the meaning
is wrong.
So for array allocation the code should use LED_NUM_COLOR_IDS
which will allocate MAX_ID + 1. Whent the code
> On Oct 2, 2019, at 5:04 AM, Ivan Khoronzhuk
> wrote:
>
> The "path" buf is supposed to contain path + printf msg up to 24 bytes.
> It will be cut anyway, but compiler generates truncation warns like:
>
> "
> samples/bpf/../../tools/testing/selftests/bpf/cgroup_helpers.c: In
> function
On Thursday 19 September 2019 18:34:48 CEST Andrew Lunn wrote:
> On Thu, Sep 19, 2019 at 10:52:35AM +, Jerome Pouiller wrote:
> > +static int wfx_sdio_copy_from_io(void *priv, unsigned int reg_id,
> > + void *dst, size_t count)
> > +{
> > + struct wfx_sdio_priv
> On Oct 2, 2019, at 5:04 AM, Ivan Khoronzhuk
> wrote:
>
> Add static to enable_all_controllers() to get rid from annoying warn:
>
> samples/bpf/../../tools/testing/selftests/bpf/cgroup_helpers.c:44:5:
> warning: no previous prototype for ‘enable_all_controllers’
> [-Wmissing-prototypes]
>
On 02/10/2019 16:43, Arnd Bergmann wrote:
On Tue, Oct 1, 2019 at 6:07 PM John Garry wrote:
Currently the driver will only ever be built for ARM64 because it selects
CONFIG_INDIRECT_PIO, which itself depends on ARM64.
Expand build test coverage for the driver to other architectures by only
On Wed, Oct 2, 2019 at 7:27 AM Jason Gunthorpe wrote:
>
> On Tue, Oct 01, 2019 at 11:32:50AM -0700, Alan Mikhak wrote:
> > From: Alan Mikhak
> >
> > Update the description of sg_set_page() to communicate current
> > requirements for the page pointer parameter.
> >
> > Signed-off-by: Alan Mikhak
There were some really old glibc versions that used the system call,
but I believe they have a reasonable fall back, and may not be used
much anymore.
Acked-by: Andi Kleen
-Andi
From: Parth Shah
> Sent: 30 September 2019 11:44
...
> 5> Separating AVX512 tasks and latency sensitive tasks on separate cores
> ( -Tim Chen )
> ===
> Another usecase we are considering is to segregate those workload that
On Wed, Oct 02, 2019 at 08:42:04AM -0700, Jerry Snitselaar wrote:
> On Wed Oct 02 19, Jerry Snitselaar wrote:
> > On Wed Oct 02 19, Sasha Levin wrote:
> > > On Wed, Oct 02, 2019 at 03:57:58PM +0200, Greg KH wrote:
> > > > On Wed, Oct 02, 2019 at 04:14:44PM +0300, Jarkko Sakkinen wrote:
> > > > >
Make the examples in Exynos ADC bindings more readable and bring them
closer to real DTS by using defines for clocks.
Signed-off-by: Krzysztof Kozlowski
---
.../devicetree/bindings/iio/adc/samsung,exynos-adc.yaml | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Include the generic rtc.yaml bindings in Samsung S3C RTC bindings. This
brings the requirement of proper node names and adds parsing of
additional properties.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/rtc/s3c-rtc.yaml | 1 +
1 file changed, 1 insertion(+)
diff
Change the indentation of examples used in json-schema bindings from two
to four spaces as this makes the code easier to read and seems to be
preferred in other files.
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/exynos-chipid.yaml | 4 +-
Make the examples in S3C RTC bindings more readable and bring them
closer to real DTS by using defines for clocks.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/rtc/s3c-rtc.yaml | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
On 10/2/19 3:33 AM, Michal Suchanek wrote:
Now devicetree is supposrted for probing sondwire as well.
typos...
also it'd be simpler to squash the two patches together and add in the
commit message a mention that the s390 builds without ACPI and without OF.
Fixes: a2e484585ad3
> -Original Message-
> From: Yehezkel Bernat
> Sent: Wednesday, October 2, 2019 10:37 AM
> To: Limonciello, Mario
> Cc: Mika Westerberg; linux-...@vger.kernel.org; Andreas Noever; Michael
> Jamet; Rajmohan Mani; nicholas.johnson-opensou...@outlook.com.au; Lukas
> Wunner;
On 10/2/19 17:48, Krzysztof Kozlowski wrote:
> This will create conflicts with conversion to dt-schema (already picked
> up by Rob).
>
> Can you convert this patch to dt-schema format and send it for Rob?
Sure, I will convert the patch.
--
Regards,
Sylwester
śr., 2 paź 2019 o 15:06 kbuild test robot napisał(a):
>
> Hi Bartosz,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on iio/togreg]
> [cannot apply to v5.4-rc1 next-20191002]
> [if your patch is applied to the wrong git tree, please drop us
Several functions in this file are trying to use regmap_read() to
initialize the specific variable, however, if regmap_read() fails,
the variable could be uninitialized but used directly, which is
potentially unsafe. The return value of regmap_read() should be
checked and handled. The same case
On 10/2/19 16:33, Krzysztof Kozlowski wrote:
> On Tue, Sep 10, 2019 at 02:36:13PM +0200, Sylwester Nawrocki wrote:
>> To be squashed with patch "PM / OPP: Support adjusting OPP voltages
>> at runtime".
>>
>> Signed-off-by: Sylwester Nawrocki
>> ---
>>
>> drivers/opp/core.c | 10 --
>>
[CC: +affected coreboot folks, +coreboot mailing list]
Dear Thomas,
More affected people discussed this issue on the coreboot mailing list [1].
On 2019-01-14 18:37, Lendacky, Thomas wrote:
> On 1/14/19 11:09 AM, Paul Menzel wrote:
>> On 01/14/19 18:00, Lendacky, Thomas wrote:
>>> On 1/10/19
401 - 500 of 926 matches
Mail list logo
