8devices Jalapeno is a dual-band SoM, based on Qualcomm
IPQ4018 + QCA8072 platform.
Specification:
QCA IPQ4018, Quad core ARM v7 Cortex A7 717MHz
256 MB of DDR3 RAM
8 MB of SPI NOR flash
128 MB of Winbond SPI NAND flash
WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2
WLAN2: Qualcomm Atheros
On Fri, Jun 26, 2020 at 01:59:43PM -0700, Kees Cook wrote:
> Instead of full GNU diff (which smaller boot environments may not have),
> use "comm" which is more available.
>
> Reported-by: Naresh Kamboju
> Link:
> https://lore.kernel.org/lkml/ca+g9fythp+gg+brr_gkbmxu2ooi-_e9pattpb6tvrswv1g1...
Lets add labels to more commonly used nodes for easier modification in board
DTS files.
Signed-off-by: Robert Marko
Cc: Luka Perkov
---
arch/arm/boot/dts/qcom-ipq4019.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/qcom-ipq4019.dtsi
b/arch/arm/
In the file pci/sh_css_params.c, there are a number of places where
memset+kvfree is used, where kvfree_sensitive could be used instead. Fix
these occurrences.
Issue identified with Coccinelle.
Signed-off-by: Alex Dewar
---
.../staging/media/atomisp/pci/sh_css_params.c | 19 +++
Lets add labels to more commonly used nodes for easier modification in board
DTS files.
Signed-off-by: Robert Marko
Cc: Luka Perkov
---
Changes since v1:
* Drop include that does not exist
arch/arm/boot/dts/qcom-ipq4019.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --
ALFA Network AP120C-AC is a dual-band ceiling AP, based on Qualcomm
IPQ4018 + QCA8075 platform.
Specification:
- Qualcomm IPQ4018 (717 MHz)
- 256 MB of RAM (DDR3)
- 16 MB (SPI NOR) + 128 or 512 MB (SPI NAND) of flash
- 2x Gbps Ethernet, with 802.3af PoE support in one port
- 2T2R 2.4/5 GHz (IPQ40
This patch series adds support for some popular IPQ4019 based
boards.
This patch series depends on:
https://patchwork.kernel.org/patch/11765789/
https://patchwork.kernel.org/patch/11760437/
Signed-off-by: Robert Marko
Cc: Luka Perkov
Robert Marko (4):
arm: dts: qcom: ipq4019: add more labels
8devices Jalapeno is a dual-band SoM, based on Qualcomm
IPQ4018 + QCA8072 platform.
Specification:
QCA IPQ4018, Quad core ARM v7 Cortex A7 717MHz
256 MB of DDR3 RAM
8 MB of SPI NOR flash
128 MB of Winbond SPI NAND flash
WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2
WLAN2: Qualcomm Atheros
8devices Habanero DVK is a dual-band SoM development kit based on Qualcomm
IPQ4019 + QCA8075 platform.
Specs are:
CPU: QCA IPQ4019
RAM: DDR3L 512MB
Storage: 32MB SPI-NOR and optional Parallel SLC NAND(Some boards ship with it
and some without)
WLAN1: 2.4 GHz built into IPQ4019 (802.11n) 2x2
WLAN2
On Wed, 9 Sep 2020 at 20:36, Jonathan Cameron wrote:
>
> On Sat, 29 Aug 2020 08:47:16 +0200
> Krzysztof Kozlowski wrote:
>
> > Common pattern of handling deferred probe can be simplified with
> > dev_err_probe(). Less code and also it prints the error value.
> >
> > Signed-off-by: Krzysztof Kozl
On Wed, Sep 09, 2020 at 11:20:51AM -0700, Luck, Tony wrote:
> Do we think there will be other places where we want this
> MSR-or-die behaviour?
MSR-or-die - I like that. That belongs on a T-shirt. :-)
> If there are, then most of this belongs elsewhere from
> arch/x86/kernel/cpu/mce/core.c
Yeah,
mp;& SCSI_LOWLEVEL [=y] && SCSI [=y] &&
>> SCSI_UFSHCD_PLATFORM [=y] && (ARCH_EXYNOS || COMPILE_TEST [=y])
>>
> Thanks, will post a patch shortly.
Hi Alim,
I am still seeing this in linux-next of 20200909.
Was there a patch posted that I missed and is
fallthrough to a separate case/default label break; isn't very readable.
Convert pseudo-keyword fallthrough; statements to a simple break; when
the next label is case or default and the only statement in the next
label block is break;
Found using:
$ grep-2.5.4 -rP --include=*.[ch] -n
"fallthrou
On Wed, Sep 09, 2020 at 08:53:50PM +0100, Alex Dewar wrote:
> In the file pci/sh_css_params.c, there are a number of places where
> memset+kvfree is used, where kvfree_sensitive could be used instead. Fix
> these occurrences.
This doesn't say *why* the commit is doing it. There are two reasons:
T
On Fri, Sep 4, 2020 at 4:23 AM Mauro Carvalho Chehab
wrote:
>
> Rename hikey970 to hi3670, in order to use a namespace
> similar to hi3660 driver.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> .../bindings/phy/phy-hi3670-usb3.txt | 4 +-
Bindings should be a separate patch.
> driv
On Wed, Sep 09, 2020 at 11:24:14AM -0700, Hugh Dickins wrote:
> After overnight reflection, my own preference would be simply to
> drop this patch. I think we are making altogether too much of a
> fuss here over what was simply correct as plain put_page()
> (and further from correct if we change i
On Wed, Sep 09, 2020 at 08:06:47PM +0200, Borislav Petkov wrote:
> On Thu, Sep 03, 2020 at 08:01:37PM +, Yazen Ghannam wrote:
> > From: Yazen Ghannam
> >
> > AMD systems provide a "NodeId" value that represents a global ID
> > indicating to which "Node" a logical CPU belongs. The "Node" is a
On Thu, 27 Aug 2020 09:20:59 +0200, Arnaud Pouliquen wrote:
> Since commit ad440432d1f9 ("dt-bindings: mfd: Ensure 'syscon' has a
> more specific compatible")
> It is required to provide at least 2 compatibles string for syscon node.
> This patch documents the new compatible for stm32 SoC to suppor
On Thu, Aug 27, 2020 at 09:21:00AM +0200, Arnaud Pouliquen wrote:
> Add new properties description used to attach to a pre-loaded
> firmware according to the commit 9276536f455b3
> ("remoteproc: stm32: Parse syscon that will manage M4 synchronisation")
> which updates the driver part.
>
> Signed-o
On Thu, Aug 27, 2020 at 05:14:39PM +0800, Qiang Zhao wrote:
> From: Zhao Qiang
>
> Add bindings for nxp,rtc-2127
>
> Signed-off-by: Zhao Qiang
> ---
> Documentation/devicetree/bindings/rtc/nxp,rtc-2127.txt | 18
> ++
> 1 file changed, 18 insertions(+)
> create mode 100644 Doc
The cros ec lightbar driver has a check in probe to fail early if the ec
device isn't the cros_ec one or if it can't read the lightbar version
from the EC. Let's move this check to the place where the lightbar
device is registered. This way we don't expose devices that aren't
actually there on devi
On 9/9/20 3:49 PM, Kees Cook wrote:
On Fri, Jun 26, 2020 at 01:59:43PM -0700, Kees Cook wrote:
Instead of full GNU diff (which smaller boot environments may not have),
use "comm" which is more available.
Reported-by: Naresh Kamboju
Link:
https://lore.kernel.org/lkml/ca+g9fythp+gg+brr_gkbmxu2
Hei hei,
On Wed, Sep 09, 2020 at 11:07:36AM +0200, Pavel Machek wrote:
> Hi!
>
> > pwm_init_state(led_data->pwm, &led_data->pwmstate);
> >
> > - ret = devm_led_classdev_register(dev, &led_data->cdev);
> > + if (fwnode) {
> > + init_data.fwnode = fwnode;
> > + ret = d
On 2020-09-09 20:41, Alex Dewar wrote:
Issue identified with Coccinelle.
Hmm, on second thoughts, I'm not sure this memory is so sensitive after
all. Should we just remove the call to memset?
Signed-off-by: Alex Dewar
---
drivers/w1/w1.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions
On Tue, 08 Sep 2020 23:00:45 PDT (-0700), Christoph Hellwig wrote:
On Tue, Sep 08, 2020 at 08:12:16PM -0700, Palmer Dabbelt wrote:
I don't know enough about the block to know if the subtle difference in
register names/offsets means. They look properly jumbled up (ie, not just an
offset), so may
Document the bindings for the IBM Operation Panel, which provides
a simple interface to control a server. It has a display and three
buttons.
Also update MAINTAINERS for the new file.
Signed-off-by: Eddie James
Reviewed-by: Rob Herring
Acked-by: Joel Stanley
---
.../bindings/input/ibm,op-panel
Mask the IRQ status to only the bits that the driver checks. This
prevents excessive driver warnings when operating in slave mode
when additional bits are set that the driver doesn't handle.
Signed-off-by: Eddie James
Reviewed-by: Tao Ren
---
drivers/i2c/busses/i2c-aspeed.c | 2 ++
1 file chang
This series adds support for input from the IBM Operation Panel, which is
a simple controller with three buttons and an LCD display meant for
interacting with a server. It's connected over I2C, typically to a service
processor. This series only supports the input from the panel, in which the
panel
Set I2C bus 0 to multi-master mode and add the panel device that will
register as a slave.
Signed-off-by: Eddie James
Reviewed-by: Joel Stanley
---
arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts
Add a driver to get the button events from the panel and provide
them to userspace with the input subsystem. The panel is
connected with I2C and controls the bus, so the driver registers
as an I2C slave device.
Signed-off-by: Eddie James
Reviewed-by: Joel Stanley
---
MAINTAINERS
Set I2C bus 7 to multi-master mode and add the panel device that will
register as a slave.
Signed-off-by: Eddie James
Reviewed-by: Joel Stanley
---
arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dt
On 9/9/20 15:06, Joe Perches wrote:
> fallthrough to a separate case/default label break; isn't very readable.
>
> Convert pseudo-keyword fallthrough; statements to a simple break; when
> the next label is case or default and the only statement in the next
> label block is break;
>
> Found usi
My name is Reem E. Al-Hashimi, the Emirates Minister of State and Managing
Director of the United Arab Emirates (Dubai) World Expo 2020 Committee. I am
writing to you to stand as my partner to receive my share of gratification from
foreign companies whom I helped during the bidding exercise towa
On Tue, 25 Aug 2020 12:26:17 +0200
Jean-Philippe Brucker wrote:
> On Fri, Aug 21, 2020 at 09:35:15PM -0700, Jacob Pan wrote:
> > Relations among IOASID users largely follow a publisher-subscriber
> > pattern. E.g. to support guest SVA on Intel Scalable I/O
> > Virtualization (SIOV) enabled platfo
On Wed, Sep 9, 2020 at 1:17 AM Ard Biesheuvel wrote:
>
> (+ Atish, Palmer)
>
> On Fri, 4 Sep 2020 at 18:50, Heinrich Schuchardt wrote:
> >
> > In the memory map the regions with the lowest addresses may be of type
> > EFI_RESERVED_TYPE. The reserved areas may be discontinuous relative to the
> >
On Thu, Aug 27, 2020 at 03:28:52PM +0200, Swapnil Jakhade wrote:
> Torrent PHY can be used in different multi-link multi-protocol
> configurations including protocols other than DisplayPort also,
> such as PCIe, USB, SGMII, QSGMII etc. Update the bindings to have
> support for these configurations.
On Tue, 08 Sep 2020 23:55:15 PDT (-0700), Christoph Hellwig wrote:
On Tue, Sep 08, 2020 at 09:59:29PM -0700, Palmer Dabbelt wrote:
The first four patches are general improvements and enablement for all nommu
ports, and might make sense to merge through the above base branch.
Seems like it to
On 2020-09-09 21:06, Dan Carpenter wrote:
On Wed, Sep 09, 2020 at 08:53:50PM +0100, Alex Dewar wrote:
In the file pci/sh_css_params.c, there are a number of places where
memset+kvfree is used, where kvfree_sensitive could be used instead. Fix
these occurrences.
This doesn't say *why* the commit
On 9/09/20 8:23 pm, Wolfram Sang wrote:
> On Wed, Sep 09, 2020 at 08:32:47AM +1200, Evan Nimmo wrote:
>> If something goes wrong (such as the SCL being stuck low) then we need
>> to reset the PCA chip. The issue with this is that on reset we lose all
>> config settings and the chip ends up in a d
On Thu, Jul 23, 2020 at 11:51:52AM +0200, Lukas Wunner wrote:
> On Thu, Jul 23, 2020 at 05:13:06PM +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-9):
> [...]
> > commit: 3233e41d3e8ebcd44e92da47ffed97fd49b84278 ("[PATCH] PCI: pciehp: Fix
> > AB-BA deadlock
On Thu, 27 Aug 2020 11:18:38 -0700, Florian Fainelli wrote:
> The binding is currently incorrectly defining the compatible strings
> from least specific to most specific instead of the converse. Re-order
> them from most specific (left) to least specific (right) and fix the
> examples as well.
>
>
On Fri, Aug 28, 2020 at 02:13:31PM +0300, Robert Chiras (OSS) wrote:
> From: Robert Chiras
>
> Add documentation for a new property: 'fsl,clock-drop-level'.
>
> Signed-off-by: Robert Chiras
> ---
> Documentation/devicetree/bindings/display/bridge/nwl-dsi.yaml | 4
> 1 file changed, 4 inse
From: Rajan Vaja
Currently firmware passes CCF specific flags to ZynqMP clock driver.
So firmware needs to be updated if CCF flags are changed. The firmware
should have its own 'flag number space' that is distinct from the
common clk framework's 'flag number space'. So define and use ZynqMP
speci
Currently firmware is maintaining CCF specific flags and provides to
CCF as it is. But CCF flag numbers may change and that shouldn't mean
that the firmware needs to change. The firmware should have its own
'flag number space' that is distinct from the common clk framework's
'flag number space'. So
From: Rajan Vaja
Use ZynqMP specific mux clock flags instead of using CCF flags.
Signed-off-by: Rajan Vaja
Signed-off-by: Tejas Patel
Signed-off-by: Amit Sunil Dhamne
---
drivers/clk/zynqmp/clk-mux-zynqmp.c | 23 ++-
drivers/clk/zynqmp/clk-zynqmp.h | 8
2 fi
On 2020-09-09 09:15, Mathieu Poirier wrote:
On Wed, Sep 09, 2020 at 02:54:33AM +, Tingwei Zhang wrote:
On Wed, Sep 09, 2020 at 01:53:51AM +0800, Mathieu Poirier wrote:
> Hi Tingwei,
>
> Apologies for the untimely response to this set, I am hoping to get to
> it in the next two weeks.
>
It's
From: Rajan Vaja
Use ZynqMP specific divider clock flags instead of using CCF flags.
Signed-off-by: Rajan Vaja
Signed-off-by: Tejas Patel
Signed-off-by: Amit Sunil Dhamne
---
drivers/clk/zynqmp/clk-zynqmp.h | 9 +
drivers/clk/zynqmp/divider.c| 25 -
2 fil
Hi Alexander,
On 9/9/20 10:29 PM, Alexander Dahl wrote:
Hei hei,
On Wed, Sep 09, 2020 at 11:07:36AM +0200, Pavel Machek wrote:
Hi!
pwm_init_state(led_data->pwm, &led_data->pwmstate);
- ret = devm_led_classdev_register(dev, &led_data->cdev);
+ if (fwnode) {
+ i
In a few places in pci/sh_css_params.c, memset is used to zero memory
immediately before it is freed. As none of these structs appear to
contain sensitive information, just remove the calls to memset.
Suggested-by: Dan Carpenter
Signed-off-by: Alex Dewar
---
drivers/staging/media/atomisp/pci/sh
On Wed, Sep 9, 2020 at 1:26 PM Stephen Boyd wrote:
>
> The cros ec lightbar driver has a check in probe to fail early if the ec
> device isn't the cros_ec one or if it can't read the lightbar version
> from the EC. Let's move this check to the place where the lightbar
> device is registered. This
On Wed, 09 Sep 2020 14:52:04 +0800, Rahul Tanwar wrote:
> PVT controller (MR75203) is used to configure & control
> Moortec embedded analog IP which contains temprature sensor(TS),
> voltage monitor(VM) & process detector(PD) modules.
>
> Add DT bindings schema for PVT controller.
>
> Signed-off-
Hi!
> Many an ethernet PHY (and other chips) supports various HW control modes
> for LEDs connected directly to them.
I guess this should be
"Many ethernet PHYs (and other chips) support various HW control modes
for LEDs connected directly to them."
> This API registers a new private LED trigge
On 9/9/20 1:49 PM, Kees Cook wrote:
On Fri, Jun 26, 2020 at 01:59:43PM -0700, Kees Cook wrote:
Instead of full GNU diff (which smaller boot environments may not have),
use "comm" which is more available.
Reported-by: Naresh Kamboju
Link:
https://lore.kernel.org/lkml/ca+g9fythp+gg+brr_gkbmxu2
On Wed, Sep 09, 2020 at 01:06:39PM -0700, Joe Perches wrote:
> diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
> index eea0f453cfb6..8aac5bc60f4c 100644
> --- a/crypto/tcrypt.c
> +++ b/crypto/tcrypt.c
> @@ -2464,7 +2464,7 @@ static int do_test(const char *alg, u32 type, u32 mask,
> int m, u32 num_m
On Wed, 09 Sep 2020 18:25:46 +0200, Marek Behún wrote:
> Document binding for LEDs connected to and controlled by various chips
> (such as ethernet PHY chips).
>
> Signed-off-by: Marek Behún
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> ---
> .../leds/linux,hw-controlled-leds.yaml
Hi!
> >>> pwm_init_state(led_data->pwm, &led_data->pwmstate);
> >>>- ret = devm_led_classdev_register(dev, &led_data->cdev);
> >>>+ if (fwnode) {
> >>>+ init_data.fwnode = fwnode;
> >>>+ ret = devm_led_classdev_register_ext(dev, &led_data->cdev,
> >>>+
On Wed, Sep 09, 2020 at 08:33:10PM +0200, Marek Behún wrote:
> On Wed, 9 Sep 2020 20:27:30 +0200
> Andrew Lunn wrote:
>
> > On Wed, Sep 09, 2020 at 06:25:46PM +0200, Marek Behún wrote:
> > > Document binding for LEDs connected to and controlled by various
> > > chips (such as ethernet PHY chips).
Quoting Guenter Roeck (2020-09-09 13:48:41)
> On Wed, Sep 9, 2020 at 1:26 PM Stephen Boyd wrote:
> > -static int get_lightbar_version(struct cros_ec_dev *ec,
> > - uint32_t *ver_ptr, uint32_t *flg_ptr)
> > -{
> > - struct ec_params_lightbar *param;
> > - s
On 9/9/2020 1:41 PM, Rob Herring wrote:
On Thu, 27 Aug 2020 11:18:38 -0700, Florian Fainelli wrote:
The binding is currently incorrectly defining the compatible strings
from least specific to most specific instead of the converse. Re-order
them from most specific (left) to least specific (rig
On Wed, 9 Sep 2020, Matthew Wilcox wrote:
> On Wed, Sep 09, 2020 at 11:24:14AM -0700, Hugh Dickins wrote:
> > After overnight reflection, my own preference would be simply to
> > drop this patch. I think we are making altogether too much of a
> > fuss here over what was simply correct as plain put
On Wed, 9 Sep 2020 14:59:23 -0600
Rob Herring wrote:
> >
> > I don't know :) I copied this from other drivers, I once tried setting
> > up environment for doing checking of device trees with YAML schemas,
> > and it was a little painful :)
>
> pip3 install dtschema ?
>
> Can you elaborate on
On Wed, 2020-09-09 at 13:55 -0700, Keith Busch wrote:
> On Wed, Sep 09, 2020 at 01:06:39PM -0700, Joe Perches wrote:
> > diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
> > index eea0f453cfb6..8aac5bc60f4c 100644
> > --- a/crypto/tcrypt.c
> > +++ b/crypto/tcrypt.c
> > @@ -2464,7 +2464,7 @@ static in
From: Wang Hai
Date: Wed, 9 Sep 2020 21:21:09 +0800
> Rename ptp to ptp_info.
>
> Fix W=1 compile warnings (invalid kerneldoc):
>
> drivers/net/ethernet/cavium/common/cavium_ptp.c:94: warning: Excess function
> parameter 'ptp' description in 'cavium_ptp_adjfine'
> drivers/net/ethernet/cavium/c
On Wed, Sep 09, 2020 at 04:29:50PM -0400, Joe Lawrence wrote:
> On 9/9/20 3:49 PM, Kees Cook wrote:
> >
> > On Fri, Jun 26, 2020 at 01:59:43PM -0700, Kees Cook wrote:
> > > Instead of full GNU diff (which smaller boot environments may not have),
> > > use "comm" which is more available.
> > >
> >
From: Alex Elder
Date: Wed, 9 Sep 2020 08:43:44 -0500
> There is exactly one reference here; the "reference" is
> essentially a Boolean flag. So the value is always either
> 0 or 1.
Aha, then why not use a bitmask and test_and_set_bit() et al.?
This is a new interface, the documentation needs to go
into greater detail. I am particularly interested in the user workflow.
This seems like it would work only for kernel modules.
Please describe both in the documentation.
A sample of a user mode driver would be helpful.
Is putting driver_o
On 8/27/2020 11:18 AM, Florian Fainelli wrote:
Hi all,
This patch series fixes incorrectly defined compatible strings for the
Broadcom QSPI controller which resulted in the strings not being
ordered from most to least compatible.
We will need to apply some changes to the spi-bcm-qspi.c drive
09.09.2020 11:31, Georgi Djakov пишет:
> On 8/14/20 03:06, Dmitry Osipenko wrote:
>> Now memory controller is a memory interconnection provider. This allows us
>> to use interconnect API in order to change memory configuration.
>>
>> Signed-off-by: Dmitry Osipenko
>
> Thanks Dmitry! Looks good to
On Wed, Sep 09, 2020 at 06:25:46PM +0200, Marek Behún wrote:
> Document binding for LEDs connected to and controlled by various chips
> (such as ethernet PHY chips).
If they are h/w controlled, then why are they in DT?
>
> Signed-off-by: Marek Behún
> Cc: Rob Herring
> Cc: devicet...@vger.kern
Instead of full GNU diff (which smaller boot environments may not have),
use "comm" which is more available.
Reported-by: Naresh Kamboju
Cc: Shuah Khan
Cc: linux-kselft...@vger.kernel.org
Fixes: f131d9edc29d ("selftests/lkdtm: Don't clear dmesg when running tests")
Signed-off-by: Kees Cook
---
From: Zhang Changzhong
Date: Wed, 9 Sep 2020 22:06:37 +0800
> Because clk_prepare_enable() and clk_disable_unprepare() already checked
> NULL clock parameter, so the additional checks are unnecessary, just
> remove them.
>
> Reported-by: Hulk Robot
> Signed-off-by: Zhang Changzhong
Applied.
From: Zhang Changzhong
Date: Wed, 9 Sep 2020 22:09:00 +0800
> Because clk_prepare_enable() and clk_disable_unprepare() already checked
> NULL clock parameter, so the additional checks are unnecessary, just
> remove them.
>
> Reported-by: Hulk Robot
> Signed-off-by: Zhang Changzhong
Applied.
On Wed, Sep 9, 2020 at 11:24 AM Hugh Dickins wrote:
>
> On Wed, 9 Sep 2020, Alexander Duyck wrote:
> > On Tue, Sep 8, 2020 at 6:01 PM Matthew Wilcox wrote:
> > > On Mon, Aug 24, 2020 at 08:55:04PM +0800, Alex Shi wrote:
> > > > +++ b/mm/vmscan.c
> > > > @@ -1688,10 +1688,13 @@ static unsigned lon
On 9/9/20 2:49 PM, Shuah Khan wrote:
On 9/9/20 1:49 PM, Kees Cook wrote:
On Fri, Jun 26, 2020 at 01:59:43PM -0700, Kees Cook wrote:
Instead of full GNU diff (which smaller boot environments may not have),
use "comm" which is more available.
Reported-by: Naresh Kamboju
Link:
https://lore.ker
On Wed, 9 Sep 2020 22:48:15 +0200
Pavel Machek wrote:
> Hi!
>
> > Many an ethernet PHY (and other chips) supports various HW control modes
> > for LEDs connected directly to them.
>
> I guess this should be
>
> "Many ethernet PHYs (and other chips) support various HW control modes
> for LEDs
On 9/9/20 4:14 PM, David Miller wrote:
From: Alex Elder
Date: Wed, 9 Sep 2020 08:43:44 -0500
There is exactly one reference here; the "reference" is
essentially a Boolean flag. So the value is always either
0 or 1.
Aha, then why not use a bitmask and test_and_set_bit() et al.?
OK I'll go
Hi!
On 2020-09-09 21:57, Krzysztof Kozlowski wrote:
> On Wed, 9 Sep 2020 at 20:36, Jonathan Cameron wrote:
>>
>> On Sat, 29 Aug 2020 08:47:16 +0200
>> Krzysztof Kozlowski wrote:
>>
>>> Common pattern of handling deferred probe can be simplified with
>>> dev_err_probe(). Less code and also it pr
Hi,
On Thu, Sep 3, 2020 at 8:07 AM satya priya wrote:
>
> --- a/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> +++ b/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> @@ -474,32 +474,30 @@
> &qup_uart3_default {
> pinconf-cts {
> /*
> -* Configure a pull-down on 38 (CT
From: Florian Fainelli
Date: Wed, 9 Sep 2020 10:49:31 -0700
> We already maintain an array of VLANs used by the switch so we can
> simply iterate over it to report the occupancy via devlink.
>
> Signed-off-by: Florian Fainelli
Applied.
Hi,
On Thu, Sep 3, 2020 at 8:08 AM satya priya wrote:
>
> diff --git a/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> b/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> index cecac3e..77e3523 100644
> --- a/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> +++ b/arch/arm64/boot/dts/qcom/sc7180-idp.dts
> @@ -507,6 +
The migrate_vma_setup(), migrate_vma_pages(), and migrate_vma_finalize()
API usage by device drivers is not well documented.
Add a description for how device drivers are expected to use it.
Signed-off-by: Ralph Campbell
---
There shouldn't be any merge conflict with my previous patch which
touch
On Wed, Sep 09, 2020 at 11:07:26PM +0200, Marek Behun wrote:
> On Wed, 9 Sep 2020 14:59:23 -0600
> Rob Herring wrote:
>
> > >
> > > I don't know :) I copied this from other drivers, I once tried setting
> > > up environment for doing checking of device trees with YAML schemas,
> > > and it was a
fig
x86_64 randconfig-a004-20200909
x86_64 randconfig-a006-20200909
x86_64 randconfig-a003-20200909
x86_64 randconfig-a001-20200909
x86_64 randconfig-a005-20200909
x86_64 randconfig-a002-20200909
i386 randc
On Wed, Sep 9, 2020 at 11:42 AM Segher Boessenkool
wrote:
>
> It will not work like this in GCC, no. The LLVM people know about that.
> I do not know why they insist on pushing this, being incompatible and
> everything.
Umm. Since they'd be the ones supporting this, *gcc* would be the
incompatib
allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a004-20200909
x86_64 randconfig-a006
On 9/9/20 3:17 PM, Kees Cook wrote:
Instead of full GNU diff (which smaller boot environments may not have),
use "comm" which is more available.
Reported-by: Naresh Kamboju
Cc: Shuah Khan
Cc: linux-kselft...@vger.kernel.org
Fixes: f131d9edc29d ("selftests/lkdtm: Don't clear dmesg when running
I've created phone-de...@vger.kernel.org
Hi!
> > > Many an ethernet PHY (and other chips) supports various HW control modes
> > > for LEDs connected directly to them.
> >
> > I guess this should be
> >
> > "Many ethernet PHYs (and other chips) support various HW control modes
> > for LEDs connected directly to them."
> >
>
> I gues
>
> I've created phone-de...@vger.kernel.org
Thank you!
Pavel
On Wed, 9 Sep 2020 15:31:22 -0600
Rob Herring wrote:
> On Wed, Sep 09, 2020 at 11:07:26PM +0200, Marek Behun wrote:
> > On Wed, 9 Sep 2020 14:59:23 -0600
> > Rob Herring wrote:
> >
> > > >
> > > > I don't know :) I copied this from other drivers, I once tried setting
> > > > up environment f
On Wed, Sep 09, 2020 at 06:25:45PM +0200, Marek Behún wrote:
> Hello Andrew and Pavel,
>
> please review these patches adding support for HW controlled LEDs.
> The main difference from previous version is that the API is now generalized
> and lives in drivers/leds, so that part needs to be reviewe
Vlastimil Babka writes:
- Exit also on other signals such as SIGABRT, SIGTERM? If I write to drop_caches
and think it's too long, I would prefer to kill it by ctrl-c and not just kill
Oh dear, fatal_signal_pending() doesn't consider cases with no more userspace
instructions due to SIG_DFL on T
On Wed, Sep 09, 2020 at 09:21:05AM +0200, Greg KH wrote:
> On Wed, Sep 09, 2020 at 03:47:09PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the driver-core tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > lib/test_firmware.c: In function 'trigg
On Wed, Sep 09, 2020 at 07:59:44PM +0200, Vlastimil Babka wrote:
> - Exit also on other signals such as SIGABRT, SIGTERM? If I write to
> drop_caches
> and think it's too long, I would prefer to kill it by ctrl-c and not just kill
> -9. Dunno if the canonical way of testing for this is if
> (signa
On Wed, Sep 09, 2020 at 10:47:24PM +0100, Chris Down wrote:
> Vlastimil Babka writes:
> > - Exit also on other signals such as SIGABRT, SIGTERM? If I write to
> > drop_caches
> > and think it's too long, I would prefer to kill it by ctrl-c and not just
> > kill
>
> Oh dear, fatal_signal_pending(
Hi Jakub,
Jakub Kicinski writes:
> On Tue, 08 Sep 2020 22:29:21 -0700 syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit:59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' ..
>> git tree: upstream
>> console output: https://syzkaller.appspot.c
Matthew Wilcox writes:
On Wed, Sep 09, 2020 at 10:47:24PM +0100, Chris Down wrote:
Vlastimil Babka writes:
> - Exit also on other signals such as SIGABRT, SIGTERM? If I write to
drop_caches
> and think it's too long, I would prefer to kill it by ctrl-c and not just kill
Oh dear, fatal_signal_p
Introduce an memcg interface to trigger memory reclaim on a memory cgroup.
Use cases:
--
1) Per-memcg uswapd:
Usually applications consists of combination of latency sensitive and
latency tolerant tasks. For example, tasks serving user requests vs
tasks doing data backup for a database a
On Wed, 9 Sep 2020 15:15:52 -0600
Rob Herring wrote:
> On Wed, Sep 09, 2020 at 06:25:46PM +0200, Marek Behún wrote:
> > Document binding for LEDs connected to and controlled by various chips
> > (such as ethernet PHY chips).
>
> If they are h/w controlled, then why are they in DT?
The idea is
Add vivaldi HID driver. This driver allows us to read and report the top
row layout of keyboards which provide a vendor-defined (Google) HID
usage.
Signed-off-by: Sean O'Brien
---
drivers/hid/Kconfig | 9 +++
drivers/hid/Makefile | 1 +
drivers/hid/hid-core.c| 7 ++
drivers
901 - 1000 of 1298 matches
Mail list logo
