On Fri, Aug 23, 2019 at 04:26:41PM +0800, Xiaowei Bao wrote:
> Add the PCIe compatible string for LS1028A
>
> Signed-off-by: Xiaowei Bao
> Signed-off-by: Hou Zhiqiang
> Reviewed-by: Rob Herring
> ---
> v2:
> - No change.
> v3:
> - No change.
> v4:
> - No change.
>
>
On 23/08/2019 20:45:53+0800, YueHaibing wrote:
> If WATCHDOG_CORE is not set, build fails:
>
> drivers/rtc/rtc-pcf2127.o: In function `pcf2127_probe.isra.6':
> drivers/rtc/rtc-pcf2127.c:478: undefined reference to
> `devm_watchdog_register_device'
>
> Add WATCHDOG_CORE Kconfig dependency to fix
On 20/08/2019 10:49, Bibby Hsieh wrote:
> add polling function in cmdq helper functions
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: CK Hu
> ---
> drivers/soc/mediatek/mtk-cmdq-helper.c | 28
> include/linux/mailbox/mtk-cmdq-mailbox.h | 1 +
>
On Fri, Aug 23, 2019 at 03:42:47PM +0200, Daniel Vetter wrote:
> I'm assuming the lockdep one will land, so not going to resend that.
I was assuming you'd wake the might_lock_nested() along with the i915
user through the i915/drm tree. If want me to take some or all of that,
lemme know.
Hi,
in this patch, there is one piece that looked better before. (see below)
Removing the 'if (skb)' is fine, but concatening everything in one
statement just to save 2 variables and a few LOC is of no use, IMHO, and
the code is less readable.
just my 2c.
CJ
diff --git
On Fri, Aug 23, 2019 at 04:56:42AM +, Ayush Ranjan wrote:
> Hey Ted!
> Thanks for reviewing! The comment in
> fs/ext4/ext4.h:ext4_group_desc:bg_checksum
> says that the crc16 checksum formula should be crc16(sb_uuid+group+desc). I
> think group over here denotes group number.
>
> Briefly
On Fri, Aug 23, 2019 at 12:35:28PM +0300, Ivan Mikhaylov wrote:
> Set WDT_CLEAR_TIMEOUT_AND_BOOT_CODE_SELECTION into WDT_CLEAR_TIMEOUT_STATUS
> to clear out boot code source and re-enable access to the primary SPI flash
> chip while booted via wdt2 from the alternate chip.
>
> AST2400 datasheet
On 20/08/2019 10:49, Bibby Hsieh wrote:
> GCE cannot know the register base address, this function
> can help cmdq client to get the cmdq_client_reg structure.
>
> Signed-off-by: Bibby Hsieh
> Reviewed-by: CK Hu
> ---
> drivers/soc/mediatek/mtk-cmdq-helper.c | 29 ++
Booting a POWER9 PowerNV system generates a few messages below with
"ptrval" due to the pointers printed without a specifier
extension (i.e unadorned %p) are hashed to prevent leaking information
about the kernel memory layout.
radix-mmu: Initializing Radix MMU
radix-mmu: Partition table
Hi Benjamin,
On 8/23/19 4:25 AM, Benjamin Tissoires wrote:
Hi Pedro,
On Thu, Aug 22, 2019 at 10:19 PM Pedro Vanzella wrote:
Resumitting this after having rebased it against the latest changes.
thanks for resubmitting. Sorry I wasn't able to provide feedback on
the last revision
No
On 23/08/2019 12:45, Zenghui Yu wrote:
> Hi Steven,
>
> On 2019/8/21 23:36, Steven Price wrote:
>> Enable paravirtualization features when running under a hypervisor
>> supporting the PV_TIME_ST hypercall.
>>
>> For each (v)CPU, we ask the hypervisor for the location of a shared
>> page which the
On Thu, Jul 11, 2019 at 10:30:30AM -0700, Nathan Chancellor wrote:
> On Thu, Jul 11, 2019 at 02:18:08PM -0300, Jason Gunthorpe wrote:
> > On Thu, Jul 11, 2019 at 10:16:44AM -0700, Nick Desaulniers wrote:
> > > On Thu, Jul 11, 2019 at 6:39 AM Jason Gunthorpe wrote:
> > > >
> > > > On Thu, Jul 11,
On 23/08/2019 17:57:38+0800, Biwen Li wrote:
> The patch supports flextimer for lx2160a
>
> Signed-off-by: Biwen Li
> ---
> drivers/rtc/rtc-fsl-ftm-alarm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c
> index
On 23/08/2019 11:18:23+0100, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a dev_err error message. Fix it.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/rtc/rtc-fsl-ftm-alarm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
I squashed that in
Le 23/08/2019 à 00:56, Andrew Morton a écrit :
On Tue, 20 Aug 2019 09:47:55 -0700 Kees Cook wrote:
Reply-To: 20190819234111.9019-8-keesc...@chromium.org
Really?
That seems correct, that's the "[PATCH 7/7] bug: Move WARN_ON() "cut
here" into exception handler" from the series at
On 8/22/19 10:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.190 release.
There are 78 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.
Responses should be
> I am not suggesting to remove all comments. Some human readable
> explanation is important as long as the code is developed by humans.
>
> I think that I'll have to accept also the extra comments if you are
> really going to use them to check the consistency by a tool. Or
> if they are really
On Thu, Aug 22, 2019 at 10:17:48AM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.190 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
On Thu, Aug 22, 2019 at 07:22:40PM +0800, Xiaowei Bao wrote:
> Add PCIe EP mode support for ls1088a and ls2088a, there are some
> difference between LS1 and LS2 platform, so refactor the code of
> the EP driver.
>
> Signed-off-by: Xiaowei Bao
> ---
> v2:
> - New mechanism for layerscape EP
On Fri, 23 Aug 2019 08:14:39 +
Parav Pandit wrote:
> Hi Alex,
>
>
> > -Original Message-
> > From: Jiri Pirko
> > Sent: Friday, August 23, 2019 1:42 PM
> > To: Parav Pandit
> > Cc: Alex Williamson ; Jiri Pirko
> > ; David S . Miller ; Kirti
> > Wankhede ; Cornelia Huck ;
> >
On 8/22/19 10:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.140 release.
There are 71 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.
Responses should be
On 8/22/19 10:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.68 release.
There are 85 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.
Responses should be
On Fri, 2019-08-23 at 10:22 -0400, Pedro Vanzella wrote:
> I actually resubmitted by Filipe's request, since the patches weren't
> applying cleanly anymore. The idea was to apply these patches and in the
> future refactor the code to use the feature discovery routines.
Yes, I want to refactor
On 8/22/19 10:05 AM, Sasha Levin wrote:
This is the start of the stable review cycle for the 5.2.10 release.
There are 135 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.
Responses should be made by
On Tue, Aug 13, 2019 at 11:01:44AM +0200, Christoph Hellwig wrote:
> These wrappers don't provide a real benefit over just using
> set_memory_x and set_memory_nx.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/x86/include/asm/set_memory.h | 2 --
> arch/x86/kernel/machine_kexec_32.c | 4
On Fri, Aug 23, 2019 at 03:41:09PM +0200, Richard Genoud wrote:
> Since commit ce59e48fdbad ("serial: mctrl_gpio: implement interrupt
> handling"), the GPIOs interrupts are handled by mctrl_gpio_irq_handle().
Well no, since ce59e48fdbad the mctrl_gpio helper can do all that
interrupt stuff. You
Hello,
syzbot found the following crash on:
HEAD commit:fed07ef3 Merge tag 'mlx5-updates-2019-08-21' of git://git...
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=150102bc60
kernel config: https://syzkaller.appspot.com/x/.config?x=e34a4fe936eac597
On Fri, Aug 23, 2019 at 4:22 PM Pedro Vanzella wrote:
>
> Hi Benjamin,
>
> On 8/23/19 4:25 AM, Benjamin Tissoires wrote:
> > Hi Pedro,
> >
> > On Thu, Aug 22, 2019 at 10:19 PM Pedro Vanzella
> > wrote:
> >>
> >> Resumitting this after having rebased it against the latest changes.
> >
> > thanks
On Fri, Aug 23, 2019 at 03:33:39PM +0800, Hayes Wang wrote:
> v4:
> For patch #2, remove redundant calling of "ocp_reg_write(tp, OCP_EEE_ADV, 0)".
>
> v3:
> For patch #2, fix the mistake caused by copying and pasting.
>
> v2:
> Adjust patch #1. The EEE has been disabled in the beginning of
>
On Fri, Aug 23, 2019 at 11:15:18AM +0200, Vitaly Kuznetsov wrote:
> Sean Christopherson writes:
>
> > Move the stat.mmio_exits update into x86_emulate_instruction(). This is
> > both a bug fix, e.g. the current update flows will incorrectly increment
> > mmio_exits on emulation failure, and a
Hello,
syzbot found the following crash on:
HEAD commit:fed07ef3 Merge tag 'mlx5-updates-2019-08-21' of git://git...
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1256e22e60
kernel config: https://syzkaller.appspot.com/x/.config?x=e34a4fe936eac597
On Fri, Aug 23, 2019 at 01:43:49PM +, Ayan Halder wrote:
> On Tue, Aug 20, 2019 at 03:16:58PM +, Mihail Atanassov wrote:
> > komeda_pipeline_destroy has the matching of_node_put().
> >
> > Fixes: 29e56aec911dd ("drm/komeda: Add DT parsing")
> > Signed-off-by: Mihail Atanassov
> > ---
> >
On 23/08/2019 14:00, Frank Wunderlich wrote:
>> Gesendet: Freitag, 23. August 2019 um 12:04 Uhr
>> Von: "Mark Brown"
>
>> Can you run a git bisect to try to identify the commit that
>> caused things to fail?
>
> i have not figured out, how to rebase linux-next on my current (working)
>
On Fri, Aug 23, 2019 at 04:47:14PM +0300, Liran Alon wrote:
>
>
> > On 23 Aug 2019, at 4:07, Sean Christopherson
> > wrote:
> >
> > Add an explicit emulation type for forced #UD emulation and use it to
> > detect that KVM should unconditionally inject a #UD instead of falling
> > into its
On Fri, 2019-08-23 at 16:32 +0200, Benjamin Tissoires wrote:
> The problem I have with quirks, and that I explained to Filipe on IRC
> is that this is kernel ABI. Even if there is a very low chance we have
> someone using this, re-using the same drv_data bit in the future might
> break someone's
On Wed, Aug 21, 2019 at 12:36 PM wrote:
>
> Qian Cai writes:
>
> > The linux-next commit "sched/fair: Fix low cpu usage with high
> > throttling by removing expiration of cpu-local slices" [1] introduced a
> > few compilation warnings,
> >
> > kernel/sched/fair.c: In function
Hi Jisheng,
On Wed, 21 Aug 2019 02:09:10 +
Jisheng Zhang wrote:
> > > In v2, actually, the arm64 version's kprobe_ftrace_handler() is the same
> > > as x86's, the only difference is comment, e.g
> > >
> > > /* Kprobe handler expects regs->ip = ip + 1 as breakpoint hit */
> > >
> > > while
> -Original Message-
> From: Alex Williamson
> Sent: Friday, August 23, 2019 7:58 PM
> To: Parav Pandit
> Cc: Jiri Pirko ; Jiri Pirko ; David S .
> Miller
> ; Kirti Wankhede ; Cornelia
> Huck ; k...@vger.kernel.org; linux-
> ker...@vger.kernel.org; cjia ; net...@vger.kernel.org
>
On 23/08/2019 05:45, Hsin-Hsiung Wang wrote:
> In order to support different types of irq design, we decide to add
> separate irq drivers for different design and keep mt6397 mfd core
> simple and reusable to all generations of PMICs so far.
>
> Acked-for-mfd-by: Lee Jones
> Signed-off-by:
Add missing documentation of Samsung S5Pv210 SoC based boards bindings.
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/samsung-boards.yaml | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
Convert Samsung S5P and Exynos SoC bindings to DT schema format using
json-schema. This is purely conversion of already documented bindings
so it does not cover all of DTS in the Linux kernel (few S5P/Exynos and
all S3C are missing).
Signed-off-by: Krzysztof Kozlowski
---
If the schema looks
Convert Samsung Exynos System Registers (SYSREG) bindings to DT schema
format using json-schema.
Signed-off-by: Krzysztof Kozlowski
---
Example somehow fails:
Documentation/devicetree/bindings/arm/samsung/pmu.example.dt.yaml:
system-controller@1004: compatible:0: 'samsung,exynos5250-pmu'
Convert Samsung S3C/Exynos Real Time Clock bindings to DT schema format
using json-schema.
Signed-off-by: Krzysztof Kozlowski
---
.../devicetree/bindings/rtc/s3c-rtc.txt | 31 --
.../devicetree/bindings/rtc/s3c-rtc.yaml | 95 +++
2 files changed, 95 insertions(+),
Convert Samsung Exynos Chipid bindings to DT schema format using
json-schema.
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/arm/samsung/exynos-chipid.txt| 12 --
.../bindings/arm/samsung/exynos-chipid.yaml | 24 +++
2 files changed, 24 insertions(+), 12
Add missing documentation of ARMv8 Samsung Exynos7 SoC based boards
bindings.
Signed-off-by: Krzysztof Kozlowski
---
.../devicetree/bindings/arm/samsung/samsung-boards.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git
Convert Samsung Exynos Power Management Unit (PMU) bindings to DT schema
format using json-schema.
Signed-off-by: Krzysztof Kozlowski
---
.../devicetree/bindings/arm/samsung/pmu.txt | 72 --
.../devicetree/bindings/arm/samsung/pmu.yaml | 93 +++
2 files changed,
Convert Samsung Exynos Analog to Digital Converter bindings to DT schema
format using json-schema.
Signed-off-by: Krzysztof Kozlowski
---
.../bindings/iio/adc/samsung,exynos-adc.txt | 107
.../bindings/iio/adc/samsung,exynos-adc.yaml | 159 ++
2 files changed,
The Exynos3250 ADC has its own compatible because of differences from
other Exynos SoCs. Therefore it is not entirely compatible with
samsung,exynos-adc-v2. Remove the samsung,exynos-adc-v2.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos3250.dtsi | 3 +--
1 file changed, 1
On Fri, Aug 23, 2019 at 03:30:11PM +0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 23 Aug 2019 15:15:41 +0200
>
> Adjust jump targets so that a bit of exception handling can be better
> reused at the end of this function.
>
> This issue was detected by using the Coccinelle
On 23/08/2019 14:13, Frank Wunderlich wrote:
> Hi,
>
> this commit breaks mt6323 pmic on BananaPi-R2
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a4872e80ce7d2a1844328176dbf279d0a2b89bdb
>
> resulting in this message in dmesg:
>
> mt6397
Hi,
On Tue, Aug 20, 2019 at 08:17:49AM -0500, Samuel Holland wrote:
> On 8/20/19 3:15 AM, Maxime Ripard wrote:
> > On Mon, Aug 19, 2019 at 10:23:06PM -0500, Samuel Holland wrote:
> >> The A80 SoC contains a message box that can be used to send messages and
> >> interrupts back and forth between
In-Reply-To: 20190819234111.9019-8-keesc...@chromium.org
Le 20/08/2019 à 18:47, Kees Cook a écrit :
The original clean up of "cut here" missed the WARN_ON() case (that
does not have a printk message), which was fixed recently by adding
an explicit printk of "cut here". This had the downside of
Hi Jisheng,
On Thu, 22 Aug 2019 11:25:00 +
Jisheng Zhang wrote:
> KPROBES_ON_FTRACE avoids much of the overhead with regular kprobes as it
> eliminates the need for a trap, as well as the need to emulate or
> single-step instructions.
>
> Tested on berlin arm64 platform.
>
> ~ # mount -t
On 08/23, Chao Yu wrote:
> On 2019/7/12 16:55, Chao Yu wrote:
> > Wrap merge condition into function for readability, no logic change.
> >
> > Signed-off-by: Chao Yu
> > ---
> > v2: remove bio validation check in page_is_mergeable().
> > fs/f2fs/data.c | 40
On Fri, 2019-08-23 at 07:19 -0700, Guenter Roeck wrote:
> >
> > +/* access_cs0 shows if cs0 is accessible, hence the reverted bit */
> > +static ssize_t access_cs0_show(struct device *dev,
> > + struct device_attribute *attr, char *buf)
> > +{
> > + struct aspeed_wdt *wdt =
On Fri, 2019-08-23 at 01:16 -0400, Pankaj Gupta wrote:
> > On Thu, 2019-08-22 at 06:43 -0400, Pankaj Gupta wrote:
> > > > This series provides an asynchronous means of reporting to a hypervisor
> > > > that a guest page is no longer in use and can have the data associated
> > > > with it dropped.
On Fri, Aug 23, 2019 at 12:22:27PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the rdma tree got a conflict in:
>
> drivers/infiniband/hw/mlx5/mlx5_ib.h
>
> between commit:
>
> 0e6613b41edd ("IB/mlx5: Consolidate use_umr checks into single function")
>
> from
The following commit has been merged into the timers/core branch of tip:
Commit-ID: adb87ff4f96c9700718e09c97a804124d5cd61ff
Gitweb:
https://git.kernel.org/tip/adb87ff4f96c9700718e09c97a804124d5cd61ff
Author:Tianyu Lan
AuthorDate:Wed, 14 Aug 2019 20:32:15 +08:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: bd00cd52d5be655a2f217e2ed74b91a71cb2b14f
Gitweb:
https://git.kernel.org/tip/bd00cd52d5be655a2f217e2ed74b91a71cb2b14f
Author:Tianyu Lan
AuthorDate:Wed, 14 Aug 2019 20:32:16 +08:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 3e2d94535adb2df15f3907e4b4c7cd8a5a4c2b5a
Gitweb:
https://git.kernel.org/tip/3e2d94535adb2df15f3907e4b4c7cd8a5a4c2b5a
Author:Vitaly Kuznetsov
AuthorDate:Thu, 22 Aug 2019 10:36:30 +02:00
Fri, Aug 23, 2019 at 04:53:06PM CEST, pa...@mellanox.com wrote:
>
>
>> -Original Message-
>> From: Alex Williamson
>> Sent: Friday, August 23, 2019 7:58 PM
>> To: Parav Pandit
>> Cc: Jiri Pirko ; Jiri Pirko ; David S .
>> Miller
>> ; Kirti Wankhede ; Cornelia
>> Huck ;
On Thu, Aug 22, 2019 at 03:05:48PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> Reads from a PCI device may fail if the device has been turned off (put
> into D3cold), removed, or if some other error occurs. The PCI host bridge
> typically fabricates ~0 data to complete the CPU's read.
Neil Armstrong writes:
[...]
>>> It's for legacy when VPU is initialized from vendor U-Boot, look at commit :
>>> 339cd0ea082287ea8e2b7e7159a5a33665a2cbe3 "soc: amlogic: meson-gx-pwrc-vpu:
>>> fix power-off when powered by bootloader"
>>>
>>> In the case the VPU power domain has been
Hi
Am 23. August 2019 16:43:47 MESZ schrieb Matthias Brugger
:
>On 23/08/2019 14:00, Frank Wunderlich wrote:
>> in working version i only get this message in dmesg which
>> looks like a device-binding:
>>
>> mt6323-regulator mt6323-regulator: Chip ID = 0x2023
>> mt6397 1000d000.pwrap:mt6323:
On Fri, Aug 23, 2019 at 01:27:50PM +, Ghannam, Yazen wrote:
> Yes, sorry I missed that.
Ok, fixed. Version below. So I'm queueing all patches up to and
including this one. I have some more comments for the remaining ones but
they can wait.
Thx.
---
From: Yazen Ghannam
Date: Thu, 22 Aug
On 23/08/2019 05:45, Hsin-Hsiung Wang wrote:
> Some pmics don't need backup interrupt settings, so we change to use
> pm notifier for the pmics which are necessary to store settings.
>
> Acked-for-mfd-by: Lee Jones
> Signed-off-by: Hsin-Hsiung Wang
> ---
> drivers/mfd/mt6397-core.c |
Hi Linus,
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git
tags/modules-for-v5.3-rc6
for you to fetch
Hi Greg,
This is a pull request with interconnect patches for the 5.4 merge window.
The patches have been for a while in linux-next without reported issues. The
details are in the signed tag. Please consider pulling into char-misc-next.
Thanks,
Georgi
The following changes since commit
On Fri, Aug 23, 2019 at 4:06 PM Peter Zijlstra wrote:
> On Fri, Aug 23, 2019 at 03:42:47PM +0200, Daniel Vetter wrote:
> > I'm assuming the lockdep one will land, so not going to resend that.
>
> I was assuming you'd wake the might_lock_nested() along with the i915
> user through the i915/drm
When a platform has an open PCIe slot, not having a device connected to
it doesn't have to result in a dev_err() print saying that the link is
not up but a dev_info() would suffice.
Signed-off-by: Vidya Sagar
---
drivers/pci/controller/dwc/pcie-designware.c | 2 +-
1 file changed, 1
On Fri, Aug 09, 2019 at 03:58:20PM -0700, ira.we...@intel.com wrote:
> From: Ira Weiny
>
> Callers of dax_layout_busy_page() are only rarely operating on the
> entire file of concern.
>
> Teach dax_layout_busy_page() to operate on a sub-range of the
> address_space provided. Specifying 0 -
APIs like devm_regulator_get() and devm_phy_get() have the potential to
return -EPROBE_DEFER when the respective sub-systems are not ready yet.
So avoid printing an error message as .probe() will be tried out again
at a later point of time anyway.
Signed-off-by: Vidya Sagar
---
Am 23. August 2019 16:56:13 MESZ schrieb Matthias Brugger
:
>are you sure that you provide the correct chip_id here? I saw 0x2023
>(if I
>remember correctly), while this switch checks for 0x23, 0x91 and 0x97,
>so I'm
>not sure if the problem really lies here. I didn't dig into the code to
> -Original Message-
> From: linux-edac-ow...@vger.kernel.org On
> Behalf Of Ghannam, Yazen
> Sent: Thursday, August 22, 2019 1:54 PM
> To: Adam Borowski
> Cc: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; b...@alien8.de
> Subject: RE: [PATCH v3 0/8] AMD64 EDAC fixes
>
...
On Fri, Aug 23, 2019 at 4:48 PM Filipe Laíns wrote:
>
> On Fri, 2019-08-23 at 16:32 +0200, Benjamin Tissoires wrote:
> > The problem I have with quirks, and that I explained to Filipe on IRC
> > is that this is kernel ABI. Even if there is a very low chance we have
> > someone using this,
On Thu, 22 Aug 2019, Frederic Weisbecker wrote:
> On Thu, Aug 22, 2019 at 12:33:56AM +0200, Frederic Weisbecker wrote:
> > On Wed, Aug 21, 2019 at 09:08:48PM +0200, Thomas Gleixner wrote:
> > > The code contains three slightly different copies of validating whether a
> > > given clock resolves to
Hi Brendan,
On 8/20/19 5:20 PM, Brendan Higgins wrote:
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and determine whether the code under test behaves as expected; this also
provides a way to group
On Thu, 22 Aug 2019, Frederic Weisbecker wrote:
> On Wed, Aug 21, 2019 at 09:09:04PM +0200, Thomas Gleixner wrote:
> > --- a/include/linux/posix-timers.h
> > +++ b/include/linux/posix-timers.h
> > @@ -62,6 +62,40 @@ static inline int clockid_to_fd(const cl
> > return ~(clk >> 3);
> > }
>
>
> On 23 Aug 2019, at 17:44, Sean Christopherson
> wrote:
>
> On Fri, Aug 23, 2019 at 04:47:14PM +0300, Liran Alon wrote:
>>
>>
>>> On 23 Aug 2019, at 4:07, Sean Christopherson
>>> wrote:
>>>
>>> Add an explicit emulation type for forced #UD emulation and use it to
>>> detect that KVM
On 8/23/19 1:34 AM, Vinod Koul wrote:
On 21-08-19, 13:58, Pierre-Louis Bossart wrote:
This patchset enables debugfs support and corrects all the feedback
provided on an earlier RFC ('soundwire: updates for 5.4')
There is one remaining hard-coded value in intel.c that will need to
be fixed
On 23/08/2019 05:45, Hsin-Hsiung Wang wrote:
> From: Ran Bi
>
> Alarm registers high byte was reserved for other functions.
> This add mask in alarm registers operation functions.
> This also fix error condition in interrupt handler.
>
> Fixes: fc2979118f3f ("rtc: mediatek: Add MT6397 RTC
On 23/08/2019 14:43, Jason Gunthorpe wrote:
> On Thu, Aug 15, 2019 at 11:27:51PM -0700, Christoph Hellwig wrote:
>> On Thu, Aug 08, 2019 at 10:50:37AM -0700, Linus Torvalds wrote:
>>> On Thu, Aug 8, 2019 at 8:42 AM Christoph Hellwig wrote:
this series is based on a patch from Linus to
On 08/19/2019 03:45 PM, Segher Boessenkool wrote:
On Mon, Aug 19, 2019 at 05:05:46PM +0200, Christophe Leroy wrote:
Le 19/08/2019 à 16:37, Segher Boessenkool a écrit :
On Mon, Aug 19, 2019 at 04:08:43PM +0200, Christophe Leroy wrote:
Le 19/08/2019 à 15:23, Segher Boessenkool a écrit :
On
Hi Brendan,
On 8/20/19 5:20 PM, Brendan Higgins wrote:
Add support for aborting/bailing out of test cases, which is needed for
implementing assertions.
An assertion is like an expectation, but bails out of the test case
early if the assertion is not met. The idea with assertions is that you
As far as i understand does old init-function not rely on the chip-id, so it
seems that with this commit a prior bug is shown.
maybe the chip-id (should be 0x23 like constant) is set later after irq-request
or completely missing for mt6323
On Fri, Aug 23, 2019 at 03:28:59PM +, Ghannam, Yazen wrote:
> Boris, Do you think it'd be appropriate to change the return values
> for some cases?
>
> For example, ECC disabled is a hardware configuration. This doesn't
> mean that the module failed any operations in this case.
>
> In other
From: Tudor Ambarus
Signed-off-by: Tudor Ambarus
---
include/linux/mtd/nand.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
index cebc38b6d6f5..0c7483843a32 100644
--- a/include/linux/mtd/nand.h
+++
From: Tudor Ambarus
Remove leftover from nor->cmd_buf.
Signed-off-by: Tudor Ambarus
---
include/linux/mtd/spi-nor.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
index 63560b375168..3075ac73b171 100644
---
On Fri, Aug 23, 2019 at 08:46:18PM +0530, Vidya Sagar wrote:
> When a platform has an open PCIe slot, not having a device connected to
> it doesn't have to result in a dev_err() print saying that the link is
> not up but a dev_info() would suffice.
>
> Signed-off-by: Vidya Sagar
> ---
>
On 8/22/19 6:37 PM, Srinivas Kandagatla wrote:
This patch adds bindings for Soundwire Slave devices that includes how
SoundWire enumeration address and Link ID are used to represented in
SoundWire slave device tree nodes.
Signed-off-by: Srinivas Kandagatla
---
On Fri, Aug 23, 2019 at 08:48:32PM +0530, Vidya Sagar wrote:
> APIs like devm_regulator_get() and devm_phy_get() have the potential to
> return -EPROBE_DEFER when the respective sub-systems are not ready yet.
> So avoid printing an error message as .probe() will be tried out again
> at a later
On Fri, Aug 23, 2019 at 02:24:51PM +0800, Hsin-Yi Wang wrote:
> Introducing a chosen node, rng-seed, which is an entropy that can be
> passed to kernel called very early to increase initial device
> randomness. Bootloader should provide this entropy and the value is
> read from /chosen/rng-seed in
On 23/08/2019 17:26, Frank Wunderlich wrote:
>
>
> Am 23. August 2019 16:56:13 MESZ schrieb Matthias Brugger
> :
>> are you sure that you provide the correct chip_id here? I saw 0x2023
>> (if I
>> remember correctly), while this switch checks for 0x23, 0x91 and 0x97,
>> so I'm
>> not sure if
On Fri, Aug 23, 2019 at 12:31:40PM +0200, Takashi Iwai wrote:
> So, if any, we'd need put a mutex around the fallback loader code.
> And, the mutex should be rather per device, not a global one.
>
> Or we may trick it by appending the second parallel caller into the
> same wait queue, but the
On 8/23/19 4:19 AM, Linus Walleij wrote:
> On Tue, Aug 20, 2019 at 4:58 PM Dinh Nguyen wrote:
>
>> @@ -401,6 +402,26 @@ static int amba_device_try_add(struct amba_device *dev,
>> struct resource *parent)
>> ret = amba_get_enable_pclk(dev);
>> if (ret == 0) {
>>
This patchset add the possibility to provide a reset to the tdm formatter.
Such reset is available on the g12a SoC family and helps solve a random
channel output shift when using more than one output lane.
Changes since v1 [0]:
- Rebased on kevin's tree
[0]:
The clock controller dedicated to audio clocks also provides reset lines
on the g12 SoC family
Reviewed-by: Neil Armstrong
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: b63f20a778c88b6a04458ed6ffc69da953d3a109
Gitweb:
https://git.kernel.org/tip/b63f20a778c88b6a04458ed6ffc69da953d3a109
Author:Sean Christopherson
AuthorDate:Thu, 22 Aug 2019 14:11:22 -07:00
On 8/22/19 6:37 PM, Srinivas Kandagatla wrote:
This patch adds support to parsing device tree based
SoundWire slave devices.
Signed-off-by: Srinivas Kandagatla
---
drivers/soundwire/bus.c | 2 ++
drivers/soundwire/bus.h | 1 +
drivers/soundwire/slave.c | 52
On 19/08/2019 11:21, Mars Cheng wrote:
> Add binding documentation of mediatek,sysirq for mt6779 SoC.
>
> Signed-off-by: Mars Cheng
Reviewed-by: Matthias Brugger
> ---
> .../interrupt-controller/mediatek,sysirq.txt |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
>
1 - 100 of 850 matches
Mail list logo
