On Wed, 14 Aug 2019 10:21:39 +0100, Charles Keepax wrote:
> Add the 3 input clock sources for the chip into the device tree binding
> document.
>
> Signed-off-by: Charles Keepax
> ---
>
> No changes since v1.
>
> Thanks,
> Charles
>
> Documentation/devicetree/bindings/mfd/madera.txt | 8 +
On Tue, 27 Aug 2019, Thomas Gleixner wrote:
> On Tue, 27 Aug 2019, Ming Lei wrote:
> > +/*
> > + * Update average irq interval with the Exponential Weighted Moving
> > + * Average(EWMA)
> > + */
> > +static void irq_update_interval(void)
> > +{
> > +#define IRQ_INTERVAL_EWMA_WEIGHT 128
> > +#defi
Tony
On 8/27/19 11:04 AM, Tony Lindgren wrote:
* Dan Murphy [190827 13:02]:
Hello
On 8/27/19 7:44 AM, Dan Murphy wrote:
Tony
On 8/27/19 7:18 AM, Pavel Machek wrote:
On Mon 2019-08-26 15:44:37, Tony Lindgren wrote:
* Pavel Machek [190826 22:14]:
On Mon 2019-08-26 14:58:22, Tony Lindgren
On Wed, 14 Aug 2019 20:46:10 +0800, Baolin Wang wrote:
> Add Spreadtrum PWM controller documentation.
>
> Signed-off-by: Baolin Wang
> ---
> Changes from v2:
> - Fix some typos.
> - Move assigned-clocks to be optional.
>
> Changes from v1:
> - Use assigned-clock-parents and assigned-clocks to
Hi Suman,
Acked-by:Arnaud POULIQUEN
Thanks,
Arnaud
On 8/10/19 12:20 AM, Suman Anna wrote:
This patch adds a sysfs interface that provides the name of the
remote processor to userspace. This allows the userspace to identify
a remote processor as the remoteproc devices themselves are created
ba
On 8/27/2019 9:17 PM, Andrew Murray wrote:
On Mon, Aug 26, 2019 at 01:01:43PM +0530, Vidya Sagar wrote:
Add support to get regulator information of 3.3V and 12V supplies of a PCIe
slot from the respective controller's device-tree node and enable those
supplies. This is required in platforms like
On Tue, 27 Aug 2019 16:13:27 +
Parav Pandit wrote:
> > -Original Message-
> > From: Alex Williamson
> > Sent: Tuesday, August 27, 2019 8:59 PM
> > To: Cornelia Huck
> > Cc: Parav Pandit ; Jiri Pirko ;
> > kwankh...@nvidia.com; da...@davemloft.net; k...@vger.kernel.org; linux-
> > ke
On 27/08/2019 16:36:56+0200, Bruno Thomsen wrote:
> Disable watchdog registation when kernel is build without
> watchdog functionality, and enable watchdog core otherwise.
> This removes compile errors like the one below:
>
> drivers/rtc/rtc-pcf2127.o: in function `pcf2127_probe.constprop.3':
> rt
On Thu, 15 Aug 2019 16:37:14 +0800, Xiaowei Bao wrote:
> Add the pf-offset property for multiple PF.
>
> Signed-off-by: Xiaowei Bao
> ---
> Documentation/devicetree/bindings/pci/designware-pcie.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Wed, Aug 21, 2019 at 07:47:08PM +0200, Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 21 Aug 2019 19:30:09 +0200
>
> The dev_kfree_skb() function performs also input parameter validation.
> Thus the test around the shown calls is not needed.
>
> This issue was detected by using the
On Tue, Aug 20, 2019 at 8:58 PM Alexandre Belloni
wrote:
>
> On 19/08/2019 13:09:03+0200, Karel Zak wrote:
> > On Wed, Aug 14, 2019 at 11:32:08AM +0200, Alexandre Belloni wrote:
> > > On 14/08/2019 11:09:36+0200, Lennart Poettering wrote:
> > > > On Mi, 14.08.19 10:31, Arnd Bergmann (a...@arndb.de
On Fri, 16 Aug 2019 19:44:16 +0800, Baolin Wang wrote:
> From: Freeman Liu
>
> This patch adds the binding documentation for Spreadtrum eFuse controller.
>
> Signed-off-by: Freeman Liu
> Signed-off-by: Baolin Wang
> ---
> .../devicetree/bindings/nvmem/sprd-efuse.txt | 39
> ++
On 27/08/2019 18:27:32+0200, Arnd Bergmann wrote:
> On Tue, Aug 20, 2019 at 8:58 PM Alexandre Belloni
> wrote:
> >
> > On 19/08/2019 13:09:03+0200, Karel Zak wrote:
> > > On Wed, Aug 14, 2019 at 11:32:08AM +0200, Alexandre Belloni wrote:
> > > > On 14/08/2019 11:09:36+0200, Lennart Poettering wrot
On Sun, 18 Aug 2019 00:17:54 -0500, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> Document the devicetree bindings for Socionext Milbeaut HDMAC
> controller. Controller has upto 8 floating channels, that need
> a predefined slave-id to work from a set of slaves.
>
> Signed-off-by: Jassi
The REFCOUNT_FULL implementation uses a different saturation point than
the x86 implementation, which means that the shared refcount code in
lib/refcount.c (e.g. refcount_dec_not_one()) needs to be aware of the
difference.
Rather than duplicate the definitions from the lkdtm driver, instead
move t
On Sun, 18 Aug 2019 00:22:24 -0500, jassisinghb...@gmail.com wrote:
> From: Jassi Brar
>
> Document the devicetree bindings for Socionext Milbeaut XDMAC
> controller. Controller only supports Mem->Mem transfers. Number
> of physical channels are determined by the number of irqs registered.
>
> S
Hi all,
This is version two of the patches I previously posted here:
https://lkml.kernel.org/r/20190802101000.12958-1-w...@kernel.org
Changes since v1 include:
* Avoid duplicate WARNs when incrementing from zero
* Some crude lktdm perf results to motivate the change:
# perf stat -r 3
The definitions of REFCOUNT_MAX and REFCOUNT_SATURATED are the same,
regardless of CONFIG_REFCOUNT_FULL, so consolidate them into a single
pair of definitions.
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Elena Reshetova
Cc: Peter Zijlstra
Cc: Ard Biesheuvel
Signed-off-by: Will Deacon
---
include/linu
The full-fat refcount implementation is exposed via a set of functions
suffixed with "_checked()", the idea being that code can choose to use
the more expensive, yet more secure implementation on a case-by-case
basis.
In reality, this hasn't happened, so with a grand total of zero users,
let's rem
Rewrite the generic REFCOUNT_FULL implementation so that the saturation
point is moved to INT_MIN / 2. This allows us to defer the sanity checks
until after the atomic operation, which removes many uses of cmpxchg()
in favour of atomic_fetch_{add,sub}().
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Elena R
In preparation for changing the saturation point of REFCOUNT_FULL to
INT_MIN / 2, change the type of integer operands passed into the API
from 'unsigned int' to 'int' so that we can avoid casting during
comparisons when we don't want to fall foul of C integral conversion
rules for signed and unsign
On Fri, Aug 16, 2019 at 10:34 AM Aaro Koskinen wrote:
> On Wed, Aug 14, 2019 at 12:36:40PM +0200, Arnd Bergmann wrote:
> > On Wed, Aug 14, 2019 at 9:49 AM Tony Lindgren wrote:
> > > * Arnd Bergmann [190813 19:34]:
> > > > -#define OMAP1_IO_OFFSET0x0100 /* Virtual IO
> >
On 8/27/19 12:41 AM, Borislav Petkov wrote:
>> #define DISABLED_MASK_BIT_SET(feature_bit) \
>> @@ -104,7 +103,6 @@ extern const char * const x86_bug_flags[NBUGINTS*32];
>> CHECK_BIT_IN_MASK_WORD(DISABLED_MASK, 16, feature_bit) ||\
>> CHECK_BIT_IN_MASK_W
On Sun, 18 Aug 2019 15:55:59 +0200, Frank Wunderlich wrote:
> paths in dt-bindings should be relative as suggested by Lee Johnes
>
> Suggested-By: Lee Jones
> Signed-off-by: Frank Wunderlich
> ---
> changes since v5: splitted from dt-bindings: add powercontroller
> ---
> Documentation/devicetre
In an effort to improve performance of the REFCOUNT_FULL implementation,
move the bulk of its functions into linux/refcount.h. This allows them
to be inlined in the same way as if they had been provided via
CONFIG_ARCH_HAS_REFCOUNT.
Cc: Kees Cook
Cc: Ingo Molnar
Cc: Elena Reshetova
Cc: Peter Zi
> On Tue, Aug 27, 2019 at 1:23 AM Seunghun Han wrote:
> > If the regions allocated in the NVS region need to be handled by a
> > driver, the callback mechanism is good for it. However, this case
> > doesn't need it because the regions allocated in NVS are just I/O
> > regions.
> >
> > In my opinio
On Tue, 27 Aug 2019, Arnd Bergmann wrote:
> On Tue, Aug 27, 2019 at 4:52 PM Enric Balletbo i Serra
> wrote:
> >
> > Hi,
> >
> > On 23/8/19 14:53, Enric Balletbo i Serra wrote:
> > > Recently we refactored the CrOS EC drivers moving part of the code from
> > > the MFD subsystem to the platform chr
On Mon, Aug 26, 2019 at 04:51:52AM -0700, Christoph Hellwig wrote:
> On Wed, Aug 21, 2019 at 01:57:02PM -0400, Vivek Goyal wrote:
> > From: Stefan Hajnoczi
> >
> > Although struct dax_device itself is not tied to a block device, some
> > DAX code assumes there is a block device. Make block devic
Building an x86 64 bit kernel:
lkdtm/bugs.c:94:2: error: format '%d' expects argument of type 'int', but
argument 2 has type 'long unsigned int' [-Werror=format=]
pr_info("Calling function with %d frame size to depth %d ...\n",
^
Fixes: 24cccab42c419 ("lkdtm/bugs: Adjust recursion test to av
On 27/08/2019 09:52, Jiaxun Yang wrote:
> This controller appeared on Loongson-3 family of chips as the primary
> package interrupt source.
>
> Signed-off-by: Jiaxun Yang
> ---
> drivers/irqchip/Kconfig | 9 ++
> drivers/irqchip/Makefile | 1 +
> drivers/irqchip/irq-ls3-ioin
* Dan Murphy [190827 16:20]:
> Tony
>
> On 8/27/19 11:04 AM, Tony Lindgren wrote:
> > * Dan Murphy [190827 13:02]:
> > > Hello
> > >
> > > On 8/27/19 7:44 AM, Dan Murphy wrote:
> > > > Tony
> > > >
> > > > On 8/27/19 7:18 AM, Pavel Machek wrote:
> > > > > On Mon 2019-08-26 15:44:37, Tony Lindg
On Sun, 18 Aug 2019 15:56:00 +0200, Frank Wunderlich wrote:
> From: Josef Friedl
>
> add mt6323 to rtc-bindings
>
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
> ---
> changes since v5: splitted from "dt-bindings: add powercontroller"
> ---
> Documentation/devicetree/binding
On Sun, 18 Aug 2019 15:56:01 +0200, Frank Wunderlich wrote:
> From: Josef Friedl
>
> - add powercontroller-section to existing binding-document
> - add mt6323-pwrc bindings-document with example
>
> Suggested-by: Frank Wunderlich
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
On Sun, 18 Aug 2019 15:56:02 +0200, Frank Wunderlich wrote:
> From: Josef Friedl
>
> add missing devicetree-binding document for mt6397 rtc
> in later patch driver is extended with mt6323 chip
>
> Suggested-By: Alexandre Belloni
> Signed-off-by: Josef Friedl
> Signed-off-by: Frank Wunderlich
On Mon, 19 Aug 2019 17:21:34 +0800, Mars Cheng wrote:
> Add binding documentation of mediatek,sysirq for mt6779 SoC.
>
> Signed-off-by: Mars Cheng
> ---
> .../interrupt-controller/mediatek,sysirq.txt |1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Tue, 27 Aug 2019 15:35:10 +0200
Cornelia Huck wrote:
> On Tue, 27 Aug 2019 11:57:07 +
> Parav Pandit wrote:
>
> > > -Original Message-
> > > From: Cornelia Huck
> > > Sent: Tuesday, August 27, 2019 5:11 PM
> > > To: Parav Pandit
> > > Cc: alex.william...@redhat.com; Jiri Pirko
On Mon, 19 Aug 2019 17:21:39 +0800, Mars Cheng wrote:
> From: mtk01761
>
> This patch adds the binding documentation for
> apmixedsys, audiosys, camsys, imgsys, ipesys,
> infracfg, mfgcfg, mmsys, topckgen, vdecsys,
> and vencsys for Mediatek MT6779.
>
> Signed-off-by: mtk01761
> ---
> .../bind
On Mon, 19 Aug 2019 17:21:40 +0800, Mars Cheng wrote:
> From: mtk01761
>
> Add MT6779 clock dt-bindings, include topckgen, apmixedsys,
> infracfg, and subsystem clocks.
>
> Signed-off-by: mtk01761
> ---
> include/dt-bindings/clock/mt6779-clk.h | 436
>
> 1 fi
On Mon, 19 Aug 2019 13:53:06 +0200, Krzysztof Wilczynski wrote:
> Fix misspelled words in include/linux/pci.h, drivers/pci/Kconfig,
> and in the documentation for Freescale i.MX6 and Marvell Armada 7K/8K
> PCIe interfaces. No functional change intended.
>
> Related commit 96291d565550 ("PCI: Fix
The option for the ast2400/2500 to get access to CS0 at runtime.
Signed-off-by: Ivan Mikhaylov
---
.../ABI/testing/sysfs-class-watchdog | 34 +++
1 file changed, 34 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-watchdog
b/Documentation/ABI/testing/sy
ASPEED SoCs support dual-boot feature for SPI Flash.
When strapped appropriately, the SoC starts wdt2 (/dev/watchdog1)
and if within a minute it is not disabled, it goes off and reboots
the SoC from an alternate SPI Flash chip by changing CS0 controls
to actually drive CS1 line.
When booted from a
Jacek
OK finally getting back to this.
On 7/29/19 3:45 PM, Jacek Anaszewski wrote:
Hi Dan,
Thank you for the v4.
I have a bunch of comments below. Please take a look.
On 7/25/19 8:28 PM, Dan Murphy wrote:
Add a documentation of LED Multicolor LED class specific
sysfs attributes.
Signed-off
Adds secondary SPI flash chip into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index 2ee26c86a3
On Tue, Aug 27, 2019 at 9:04 AM Vitaly Kuznetsov wrote:
>
> It was discovered that after commit 65efa61dc0d5 ("selftests: kvm: provide
> common function to enable eVMCS") hyperv_cpuid selftest is failing on AMD.
> The reason is that the commit changed _vcpu_ioctl() to vcpu_ioctl() in the
> test an
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 says:
"In the 2nd flash booting mode, all the address mapping to CS0# would
Adds wdt2 section with 'alt-boot' option into dts for vesnin.
Signed-off-by: Ivan Mikhaylov
---
arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
b/arch/arm/boot/dts/aspeed-bmc-opp-vesnin.dts
index 0b9
IS_ERR, IS_ERR_OR_NULL, IS_ERR_VALUE already contain unlikely optimization
internally. Thus, there is no point in calling these functions under
likely/unlikely.
This check is based on the coccinelle rule developed by Enrico Weigelt
https://lore.kernel.org/lkml/1559767582-11081-1-git-send-email-i..
Hi Shuah,
Thank you for the patch.
On Tue, Aug 20, 2019 at 03:18:41PM -0600, Shuah Khan wrote:
> vimc uses Component API to split the driver into functional components.
> The real hardware resembles a monolith structure than component and
> component structure added a level of complexity making i
On Mon, Aug 26, 2019 at 5:53 AM Borislav Petkov wrote:
>
> + if (!changed) {
> + pr_emerg(
> +"RDRAND gives funky smelling output, might consider not using it by booting
> with \"nordrand\"");
> + WARN_ON_ONCE(1);
> + }
Side note: I'd suggest
if (
Hi João,
On 8/12/19 6:57 PM, Benjamin Tissoires wrote:
> Hi João,
>
> On Thu, Aug 8, 2019 at 10:35 PM João Moreno wrote:
>>
>> Hi Benjamin,
>>
>> On Mon, 8 Jul 2019 at 22:35, João Moreno wrote:
>>>
>>> Hi Benjamin,
>>>
>>> No worries, also pretty busy over here. Didn't mean to press.
>>>
>>> On
On Tue, Aug 27, 2019 at 9:04 AM Vitaly Kuznetsov wrote:
>
> Since commit 5158917c7b019 ("KVM: x86: nVMX: Allow nested_enable_evmcs to
> be NULL") the code in x86.c is prepared to see nested_enable_evmcs being
> NULL and in VMX case it actually is when nesting is disabled. Remove the
> unneeded stu
Unlike standard powerpc, Powerpc 8xx doesn't have SPRN_DABR, but
it has a breakpoint support based on a set of comparators which
allow more flexibility.
Commit 4ad8622dc548 ("powerpc/8xx: Implement hw_breakpoint")
implemented breakpoints by emulating the DABR behaviour. It did
this by setting one
On Tue, 20 Aug 2019 07:28:43 +, "Z.q. Hou" wrote:
> From: Hou Zhiqiang
>
> The num-lanes is not a mandatory property, e.g. on FSL
> Layerscape SoCs, the PCIe link training is completed
> automatically base on the selected SerDes protocol, it
> doesn't need the num-lanes to set-up the link wid
Most 8xx registers have specific names, so just include
reg_8xx.h all the time in reg.h in order to have them defined
even when CONFIG_PPC_8xx is not selected. This will avoid
the need for #ifdefs in C code.
Guard SPRN_ICTRL in an #ifdef CONFIG_PPC_8xx as this register
has same name but different
at 23:25, Takashi Iwai wrote:
On Tue, 27 Aug 2019 15:47:55 +0200,
Kai-Heng Feng wrote:
A driver may want to know the existence of _PR3, to choose different
runtime suspend behavior. A user will be add in next patch.
This is mostly the same as nouveau_pr3_present().
Then it'd be nice to clea
On Tue, Aug 27, 2019 at 10:08:30AM -0500, Josh Poimboeuf wrote:
> On Mon, Aug 26, 2019 at 04:38:29PM -0700, Nathan Chancellor wrote:
> > Looks like that comes from tune_qsfp, which gets inlined into
> > tune_serdes but I am far from an objtool expert so I am not
> > really sure what kind of issues
Hi Oleg,
On 8/27/19 3:00 PM, Oleg Nesterov wrote:
[..]
> But to remind, there is another problem with in_ia32_syscall() && uprobes.
>
> get_unmapped_area() paths use in_ia32_syscall() and this is wrong in case
> when the caller is xol_add_vma(), in this case TS_COMPAT won't be set.>
> Usually the
On Tue, 20 Aug 2019 11:46:24 +0200, Jerome Brunet wrote:
> SM1 SoC family adds two new audio FIFOs with the related arb reset lines
>
> Signed-off-by: Jerome Brunet
> ---
> .../devicetree/bindings/reset/amlogic,meson-axg-audio-arb.txt | 3 ++-
> include/dt-bindings/reset/amlogic,meson-axg-audio
On Tue, Aug 27, 2019 at 06:07:04PM +0200, Daniel Mack wrote:
> Hi Greg,
>
> On 15/8/2019 11:28 PM, Daniel Mack wrote:
> > When probed via DT, the uio_pdrv_genirq driver currently uses the name
> > of the node and exposes that as name of the UIO device to userspace.
> >
> > This doesn't work for s
On Tue, Aug 27, 2019 at 04:10:16PM +0200, Michal Hocko wrote:
> On Sat 24-08-19 23:23:07, Thomas Backlund wrote:
> > Den 24-08-2019 kl. 22:57, skrev Andrew Morton:
> > > On Sat, 17 Aug 2019 19:15:23 + Roman Gushchin wrote:
> > >
> > > > > > Fixes: 766a4c19d880 ("mm/memcontrol.c: keep local VM
On 8/27/19 5:59 AM, Kirill A. Shutemov wrote:
On Tue, Aug 27, 2019 at 03:17:39PM +0300, Kirill A. Shutemov wrote:
On Tue, Aug 27, 2019 at 02:09:23PM +0200, Michal Hocko wrote:
On Tue 27-08-19 14:01:56, Vlastimil Babka wrote:
On 8/27/19 1:02 PM, Kirill A. Shutemov wrote:
On Tue, Aug 27, 201
On Tue, 20 Aug 2019 16:11:40 +0200, Michal Simek wrote:
> Using optional "label" property is adding an option to user to use better
> name for device identification.
>
> Signed-off-by: Michal Simek
> ---
>
> Documentation/devicetree/bindings/hwmon/ina2xx.txt | 2 ++
> 1 file changed, 2 insertio
On Tue, Aug 27, 2019 at 9:04 AM Vitaly Kuznetsov wrote:
>
> If kvm_intel is loaded with nested=0 parameter an attempt to perform
> KVM_GET_SUPPORTED_HV_CPUID results in OOPS as nested_get_evmcs_version hook
> in kvm_x86_ops is NULL (we assign it in nested_vmx_hardware_setup() and
> this only happe
On 8/27/19 3:43 AM, Michal Hocko wrote:
If there are no objection to the patch I will post it as a standalong
one.
On Mon 26-08-19 12:55:21, Michal Hocko wrote:
From 59d128214a62bf2d83c2a2a9cde887b4817275e7 Mon Sep 17 00:00:00 2001
From: Michal Hocko
Date: Mon, 26 Aug 2019 12:43:15 +0200
S
On Tue, Aug 27, 2019 at 09:54:17PM +0530, Vidya Sagar wrote:
> On 8/27/2019 9:17 PM, Andrew Murray wrote:
> > On Mon, Aug 26, 2019 at 01:01:43PM +0530, Vidya Sagar wrote:
> > > Add support to get regulator information of 3.3V and 12V supplies of a
> > > PCIe
> > > slot from the respective controll
On Wed, Aug 21, 2019 at 4:11 AM Sibi Sankar wrote:
>
> Add bindings for Operating State Manager (OSM) L3 interconnect provider
> on SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> .../bindings/interconnect/qcom,osm-l3.yaml| 56 +++
> .../dt-bindings/interconnect/qcom,osm-
On Wed, Aug 21, 2019 at 08:26:24AM +0530, Manivannan Sadhasivam wrote:
> Add devicetree YAML binding for Actions Semi Owl SoC's SD/MMC/SDIO
> controller.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> .../devicetree/bindings/mmc/owl-mmc.yaml | 62 +++
> 1 file changed, 62
On Tue, Aug 27, 2019 at 09:33:11AM -0700, Dave Hansen wrote:
> The point was that there are 5 files in the code that need to be changed
> if you change NCAPINTS:
>
> 1. arch/x86/include/asm/required-features.h
> 2. arch/x86/include/asm/disabled-features.h
> 3. tools/arch/x86/include/asm/disabled-f
On Tue, 2019-08-27 at 19:55 +0300, Denis Efremov wrote:
> IS_ERR, IS_ERR_OR_NULL, IS_ERR_VALUE already contain unlikely optimization
> internally. Thus, there is no point in calling these functions under
> likely/unlikely.
>
> This check is based on the coccinelle rule developed by Enrico Weigelt
On Wed, 21 Aug 2019 15:06:51 +0800, Rahul Tanwar wrote:
> Convert the existing DT binding document for Lantiq SoC ASC serial controller
> from txt format to YAML format.
>
> Signed-off-by: Rahul Tanwar
> ---
> .../devicetree/bindings/serial/lantiq,asc.yaml | 55
> ++
> .
On Wed, 21 Aug 2019 15:06:52 +0800, Rahul Tanwar wrote:
> Intel Lightning Mountain(LGM) reuses Lantiq ASC serial controller IP.
> Update the dt bindings to support LGM as well.
>
> Signed-off-by: Rahul Tanwar
> ---
> .../devicetree/bindings/serial/lantiq,asc.yaml | 35
>
On Tue, Aug 27, 2019 at 07:54:25PM +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 sa
On Tue, Aug 27, 2019 at 09:50:05AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.141 release.
> There are 62 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On Tue, Aug 27, 2019 at 09:49:39AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.69 release.
> There are 98 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
Thomas and I seem to have become the "unofficial" maintainers for these
files and questions about SPDX things. So let's make it official.
Reported-by: "Darrick J. Wong"
Cc: Thomas Gleixner
Signed-off-by: Greg Kroah-Hartman
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9234,6 +9234,17 @@ F: in
On Wed, 21 Aug 2019 15:25:20 +0200, Martin Kepplinger wrote:
> Signed-off-by: Martin Kepplinger
> ---
> Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Tue, Aug 27, 2019 at 09:48:48AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.2.11 release.
> There are 162 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Tue, Aug 27, 2019 at 10:48:24PM +1000, Nicholas Piggin wrote:
> Christophe Leroy's on August 27, 2019 6:13 pm:
> > +#define wrtee(val) asm volatile("wrtee %0" : : "r" (val) : "memory")
> > +#define wrteei(val)asm volatile("wrteei %0" : : "i" (val) :
> > "memory")
>
> Can you implement
Hi David,
On Tue, Aug 27, 2019 at 4:17 PM David Laight wrote:
> From: Geert Uytterhoeven
> > Sent: 19 August 2019 18:15
> ...
> > > I think a cast to unsigned long is rather more common.
> > >
> > > uintptr_t is used ~1300 times in the kernel.
> > > I believe a cast to unsigned long is much more
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, sec 4.5.1, table 4-6, Error Disconnect
Recover (EDR) support allows OS to handle error recovery and
clearing Error Registers even in FF mode. So remove FF mode checks in
p
From: Kuppuswamy Sathyanarayanan
As per ACPI specification v6.3, sec 5.6.6, Error Disconnect Recover
(EDR) notification used by firmware to let OS know about the DPC event
and permit OS to perform error recovery when processing the EDR
notification. Also, as per PCI firmware specification r3.2 Do
From: Kuppuswamy Sathyanarayanan
Commit bdb5ac85777d ("PCI/ERR: Handle fatal error recovery") uses
reset_link() to recover from fatal errors. But, if the reset is
successful there is no need to continue the rest of the error recovery
checks. Also, during fatal error recovery, if the initial value
On 8/27/19 8:21 PM, Joe Perches wrote:
> On Tue, 2019-08-27 at 19:55 +0300, Denis Efremov wrote:
>> IS_ERR, IS_ERR_OR_NULL, IS_ERR_VALUE already contain unlikely optimization
>> internally. Thus, there is no point in calling these functions under
>> likely/unlikely.
>>
>> This check is based on the
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, sec 4.5.1, OS must implement following steps
to enable/use EDR feature.
1. OS can use bit 7 of _OSC Control Field to negotiate control over
Downstream Port Containment (D
From: Kuppuswamy Sathyanarayanan
Currently, in native mode, DPC driver is configured to trigger DPC only
for FATAL errors and hence it only supports port recovery for FATAL
errors. But with Error Disconnect Recover (EDR) support, DPC
configuration is done by firmware, and hence we should expect D
From: Kuppuswamy Sathyanarayanan
As per ACPI specification r6.3, sec 5.6.6, when firmware owns Downstream
Port Containment (DPC), its expected to use the "Error Disconnect
Recover" (EDR) notification to alert OSPM of a DPC event and if OS
supports EDR, its expected to handle the software state in
From: Kuppuswamy Sathyanarayanan
As per PCI firmware specification r3.2 Downstream Port Containment
Related Enhancements ECN, OS is responsible for clearing the AER
registers in EDR mode. So clear AER registers in dpc_process_error()
function.
Signed-off-by: Kuppuswamy Sathyanarayanan
Acked-by
From: Kuppuswamy Sathyanarayanan
With Error Disconnect Recover (EDR) support, we need to support
processing DPC event either from DPC IRQ or ACPI EDR event. So create
a wrapper function dpc_process_error() and move common error handling
code in to it. It will be used to process the DPC event in b
From: Kuppuswamy Sathyanarayanan
This patchset adds support for following features:
1. Error Disconnect Recover (EDR) support.
2. _OSC based negotiation support for DPC.
You can find EDR spec in the following link.
https://members.pcisig.com/wg/PCI-SIG/document/12614
Changes since v7:
* Upda
On Tue, 2019-08-27 at 12:35 +0200, Pablo Neira Ayuso wrote:
> On Wed, Aug 21, 2019 at 11:15:06AM -0300, Leonardo Bras wrote:
> > If IPv6 is disabled on boot (ipv6.disable=1), but nft_fib_inet ends up
> > dealing with a IPv6 package, it causes a kernel panic in
> > fib6_node_lookup_1(), crashing in
lkdtm/bugs.c:94:2: error: format '%d' expects argument of type 'int', but
argument 2 has type 'long unsigned int' [-Werror=format=]
pr_info("Calling function with %d frame size to depth %d ...\n",
^
THREAD_SIZE is defined as a unsigned long, cast CONFIG_FRAME_WARN to
unsigned long as well.
Fi
Le 27/08/2019 à 19:29, Segher Boessenkool a écrit :
On Tue, Aug 27, 2019 at 10:48:24PM +1000, Nicholas Piggin wrote:
Christophe Leroy's on August 27, 2019 6:13 pm:
+#define wrtee(val) asm volatile("wrtee %0" : : "r" (val) : "memory")
+#define wrteei(val)asm volatile("wrteei %0" : : "
On Tue 27-08-19 19:06:18, Greg KH wrote:
> On Tue, Aug 27, 2019 at 04:10:16PM +0200, Michal Hocko wrote:
> > On Sat 24-08-19 23:23:07, Thomas Backlund wrote:
> > > Den 24-08-2019 kl. 22:57, skrev Andrew Morton:
> > > > On Sat, 17 Aug 2019 19:15:23 + Roman Gushchin wrote:
> > > >
> > > > > > >
On Tue, Aug 27, 2019 at 09:55:08AM -0700, Linus Torvalds wrote:
> Side note: I'd suggest
>
> if (WARN_ON_ONCE(!changed))
> pr_emerg("RDRAND gives funky smelling output, might
> consider not using it by booting with \"nordrand\"");
>
> instead.
Done, final result with a pr
On Tue, Aug 27, 2019 at 07:29:52PM +0200, Geert Uytterhoeven wrote:
> Hi David,
>
> On Tue, Aug 27, 2019 at 4:17 PM David Laight wrote:
> > From: Geert Uytterhoeven
> > > Sent: 19 August 2019 18:15
> > ...
> > > > I think a cast to unsigned long is rather more common.
> > > >
> > > > uintptr_t is
2019-08-15 12:03+0800, Wanpeng Li:
> From: Wanpeng Li
>
> Even if for realtime CPUs, cache line bounces, frequency scaling, presence
> of higher-priority RT tasks, etc can still cause different response. These
> interferences should be considered and periodically revaluate whether
> or not the
On Tue, Aug 27, 2019 at 10:40 AM Borislav Petkov wrote:
>
> Do you want it this weekend, after some smoke testing on boxes or should
> I leave it a couple of weeks in tip until the merge window opens, and
> then queue it for 5.4 for longer exposure in linux-next?
No hurry, and I don't care deeply
On Tue, 27 Aug 2019 13:11:17 +
Parav Pandit wrote:
> Hi Alex, Cornelia,
>
> > -Original Message-
> > From: kvm-ow...@vger.kernel.org On Behalf
> > Of Parav Pandit
> > Sent: Tuesday, August 27, 2019 2:11 AM
> > To: alex.william...@redhat.com; Jiri Pirko ;
> > kwankh...@nvidia.com; co
On Wed, Aug 28, 2019 at 01:36:30AM +0900, Seunghun Han wrote:
> I got your point. Is there any problem if some regions which don't
> need to be handled in NVS area are saved and restored? If there is a
> problem, how about adding code for ignoring the regions in NVS area to
> the nvs.c file like J
Previously KUnit assumed that printk would always be present, which is
not a valid assumption to make. Fix that by ifdefing out functions which
directly depend on printk core functions similar to what dev_printk
does.
Reported-by: Randy Dunlap
Link:
https://lore.kernel.org/linux-kselftest/0352fa
901 - 1000 of 1477 matches
Mail list logo
