In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warning:
drivers/net/ethernet/qlogic/qed/qed_cxt.c:2126:4: warning: this statement may
fall through [-Wimplicit-fallthrough=]
Warning level 3 was used:
Hi Suravee,
On Tue, Jan 22, 2019 at 03:53:18PM +, Suthikulpanit, Suravee wrote:
> Thanks for the detail. Alright then, let's just go with the version you
> sent on 1/16/19. Do you want me to resend V3 with that changes, or
> would you be taking care of that?
Please send me a v3 based on the
From: Frieder Schrempf
This adds support for the Macronix MX25V8035F, a 8Mb SPI NOR chip.
Signed-off-by: Frieder Schrempf
---
drivers/mtd/spi-nor/spi-nor.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index
From: Frieder Schrempf
This adds support for the EON EN25Q80A, a 8Mb SPI NOR chip.
Signed-off-by: Frieder Schrempf
---
drivers/mtd/spi-nor/spi-nor.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/net/ethernet/brocade/bna/bfa_ioc.c:790:3: warning: this statement may
fall through [-Wimplicit-fallthrough=]
From: Joerg Roedel
The mtk_iommu_add_device() function keeps the fwspec in an
on-stack pointer and calls mtk_iommu_create_mapping(), which
might change its source, dev->iommu_fwspec. This causes the
on-stack pointer to be obsoleted and the device
initialization to fail. Update the on-stack
Add pvpanic driver framework. Follow-up patches will split the original
pvpanic acpi/of driver as the two seperate files and modify code to
adapt the framework.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic/pvpanic.c | 171 ++---
1 file changed, 39
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/net/ethernet/3com/3c509.c:1265:8: warning: this statement may fall
through [-Wimplicit-fallthrough=]
From: Thara Gopinath
This patch replaces jiffies based accounting for runtime_active_time
and runtime_suspended_time with ktime-based accounting. This makes the
runtime debug counters inline with genpd and other PM subsytems which
use ktime-based accounting.
Timekeeping is initialized before
Initializing accounting_timestamp to something different from 0 during
pm_runtime_init() doesn't make sense and put useless ordering constraint between
timekeeping_init() and pm_runtime_init().
PM runtime should start accounting time only when it is enable and discard
the period when disabled.
Set
Move pm_runtime accounted time to raw nsec. The subject of the patchset
has changed as 1st patch o the previous versions has been queued by
Rafael.
Patch 1 set accounting_timestamp to 0 in pm_runtime_init and update it when
enable.
So we remove ordering constraint between timekeeping_init and
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/net/ethernet/intel/igb/e1000_82575.c:636:6: warning: this statement may
fall through [-Wimplicit-fallthrough=]
-Original Message-
From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
Sent: 23 January 2019 13:11
To: Ariel Elior ; Sudarsana Kalluru
; everest-linux...@cavium.com; David S. Miller
; Siva Reddy Kallam ; Prashant
Sreedharan ; Michael Chan
Cc: net...@vger.kernel.org;
On Tue, 22 Jan 2019 at 16:23, Greg Kroah-Hartman
wrote:
>
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
Doesn't this boils done to whether we want to care
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
net/bluetooth/rfcomm/core.c:479:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
net/bluetooth/l2cap_core.c:4223:6: warning:
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.c:6336:6: warning: this
statement may fall through [-Wimplicit-fallthrough=]
On 1/22/19 4:14 PM, Greg Kroah-Hartman wrote:
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Jesper Nilsson
Cc: Lars Persson
Cc: Herbert Xu
Cc: "David
On Wed, Jan 23, 2019 at 11:47:26PM +0800, Peng Hao wrote:
> Make pvpanic acpi driver as seperate file and modify code
> in order to adapt the framework.
>
> Signed-off-by: Peng Hao
> ---
> drivers/misc/pvpanic/Kconfig| 9 +
> drivers/misc/pvpanic/Makefile | 1 +
>
On Wed, 23 Jan 2019 07:34:27 +0100
Greg Kroah-Hartman wrote:
> On Wed, Jan 23, 2019 at 07:33:05AM +0100, Greg Kroah-Hartman wrote:
> > On Wed, Jan 23, 2019 at 09:11:41AM +0900, Masami Hiramatsu wrote:
> > > On Tue, 22 Jan 2019 16:21:44 +0100
> > > Greg Kroah-Hartman wrote:
> > >
> > > > When
On 22/01/19 9:56 PM, Sowjanya Komatineni wrote:
> Below are the supported DMA types in Host Control1 Register
> with Version 4 enable
> b'00 - SDMA
> b'01 - Not Used
> b'10 - ADMA2
> b'11 - ADMA2 or ADMA3
>
> ADMA3 uses Command Descriptor to issue an SD command.
> A multi-block data transfer is
Hi Mike,
On 2019-01-23 06:54, Mike Rapoport wrote:
...
> Resending it as a formal patch now, I took a liberty to add your Tested-by.
>
> >From a847ca684db29a3c09e4dd2a8a008b35cf36e52f Mon Sep 17 00:00:00 2001
> From: Mike Rapoport
> Date: Wed, 23 Jan 2019 07:38:50 +0200
> Subject: [PATCH] of:
From: Martin Kepplinger
The st1232 driver gains support for the ST1633 controller too; update
the bindings doc accordingly.
Signed-off-by: Martin Kepplinger
---
.../bindings/input/touchscreen/sitronix-st1232.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
From: Martin Kepplinger
Add support for the Sitronix ST1633 touchscreen controller to the st1232
driver.
Signed-off-by: Martin Kepplinger
---
drivers/input/touchscreen/Kconfig | 6 +-
drivers/input/touchscreen/st1232.c | 130 +
2 files changed, 98 insertions(+),
Hello,
syzbot found the following crash on:
HEAD commit:787a3b432276 Merge branch 'for-linus' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104f80c0c0
kernel config: https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
On 1/23/19 1:23 AM, Dominique Martinet wrote:
> Gustavo A. R. Silva wrote on Wed, Jan 23, 2019:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>> where we are expecting to fall through.
>>
>> This patch fixes the following warning:
>>
>> net/9p/trans_xen.c:514:6:
Preparing for pvpanic driver framework. Create a pvpanic driver
directory and move current driver file to new directory.
Signed-off-by: Peng Hao
---
drivers/misc/Kconfig | 9 +
drivers/misc/Makefile| 2 +-
drivers/misc/pvpanic/Kconfig | 7 +++
Add pvpanic_add/remove_device API. Follow-up patches will use them to
add/remove specific drivers into framework.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic/pvpanic.c | 32
drivers/misc/pvpanic/pvpanic.h | 14 ++
2 files changed, 46
Make pvpanic mmio driver as seperate file and modify code
in order to adapt the framework.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic/Kconfig | 4 +++
drivers/misc/pvpanic/Makefile | 1 +
drivers/misc/pvpanic/pvpanic-of.c | 53 +++
3 files
Make pvpanic acpi driver as seperate file and modify code
in order to adapt the framework.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic/Kconfig| 9 +
drivers/misc/pvpanic/Makefile | 1 +
drivers/misc/pvpanic/pvpanic-acpi.c | 77 +
3
Gustavo A. R. Silva wrote on Wed, Jan 23, 2019:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> net/9p/trans_xen.c:514:6: warning: this statement may fall through
>
Add new pvpanic pci driver to pvpanic driver framework.
Signed-off-by: Peng Hao
---
drivers/misc/pvpanic/Kconfig | 5
drivers/misc/pvpanic/Makefile | 1 +
drivers/misc/pvpanic/pvpanic-pci.c | 56 ++
3 files changed, 62 insertions(+)
create
QEMU community requires additional PCI devices to simulate PVPANIC
devices so that some architectures can not occupy precious less than 4G
of memory space.
Previously, I added PCI driver directly to the original version of the driver,
which made the whole driver file look a bit cluttered. So
On Wed, Jan 23, 2019 at 07:47:47AM +1100, Stephen Rothwell wrote:
> Hi Christoph,
>
> In commit
>
> 702e8ed37bed ("arm64/xen: fix xen-swiotlb cache flushing")
>
> Fixes tag
>
> Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")
>
> has these problem(s):
>
> - SHA1
We may delete a bunch of directory entries, operating such as:
getdents(), unlink(), getdents()..., until the end of the directory.
jffs2 handles f_pos on the directory merely as the position on the
f->dents list. So, the next getdents() may skip some entries
before f_pos, if we remove some
> On Jan 23, 2019, at 7:51 AM, Bjorn Helgaas wrote:
>
> On Tue, Jan 22, 2019 at 02:45:44PM +0800, Kai-Heng Feng wrote:
>> There are some e1000e devices can only be woken up from D3 one time, by
>> plugging ethernet cable. Subsequent cable plugging does set PME bit
>> correctly, but it still
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warning:
net/9p/trans_xen.c:514:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
Warning level 3 was used: -Wimplicit-fallthrough=3
On 22-01-19, 16:21, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Viresh Kumar
> Cc: Nishanth Menon
> Cc: Stephen Boyd
On 2019-01-23 01:59, Mark Brown wrote:
On Tue, Jan 22, 2019 at 12:03:34PM +0530, Alok Chauhan wrote:
Get the interconnect paths for SPI based Serial Engine device
and vote accordingly based on maximum supported SPI frequency.
Still not seeing anything except this patch here in my inbox -
On Tue, Jan 22, 2019 at 10:07:07PM +0100, Ard Biesheuvel wrote:
> Yes, so much was clear. And the reason this breaks on some arm64
> systems is because
> a) non-snooped PCIe TLP attributes may be ignored, and
> b) non-x86 CPUs do not snoop the caches when accessing uncached mappings.
>
> I don't
On Tue, Jan 22, 2019 at 11:59:31AM -0800, Stefano Stabellini wrote:
> > if (!virtio_has_iommu_quirk(vdev))
> > return true;
> >
> > @@ -260,7 +262,7 @@ static bool vring_use_dma_api(struct virtio_device
> > *vdev)
> > * the DMA API if we're a Xen guest, which at least
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
net/tipc/link.c:1125:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
net/tipc/socket.c:736:6: warning: this statement may
On Tue, Jan 22, 2019 at 05:30:55PM -0500, Antoine Robertson wrote:
> Fix coding style issues
That is really vague, you need to say exactly what type of coding style
fixes you made here.
And if you made more than one "type" of fix, then you need to break the
patch up into a series, only doing one
Fix a static code checker warning:
drivers/spi/spi-bcm2835aux.c:460
bcm2835aux_spi_probe() warn: passing zero to 'PTR_ERR'
In case of error, the function devm_clk_get() returns ERR_PTR()
and not returns NULL.
Signed-off-by: YueHaibing
---
drivers/spi/spi-bcm2835aux.c | 2 +-
1 file changed, 1
From: Ramneek Mehresh
USB erratum-A006918 workaround tries to start internal PHY inside
uboot (when PLL fails to lock). However, if the workaround also
fails, then USB initialization is also stopped inside Linux.
Erratum-A006918 workaround failure creates "fsl,erratum_a006918"
node in
From: Nikhil Badola
Set USB_EN bit to select ULPI phy for USB controller version 2.5
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
Change in v3:
Code base already has patch[5/6], so remove it.
drivers/usb/host/ehci-fsl.c |6 ++
1 files changed, 6
From: Suresh Gupta
PHY_CLK_VALID bit for UTMI PHY in USBDR does not set even
if PHY is providing valid clock. Workaround for this
involves resetting of PHY and check PHY_CLK_VALID bit
multiple times. If PHY_CLK_VALID bit is still not set even
after 5 retries, it would be safe to deaclare that
From: Nikhil Badola
Remove USB errata checking code from driver. Applicability of erratum
is retrieved by reading corresponding property in device tree.
This property is written during device tree fixup.
Signed-off-by: Ramneek Mehresh
Signed-off-by: Nikhil Badola
Signed-off-by: Yinbo Zhu
---
From: Yinbo Zhu
This patch is to add member has_fsl_erratum_a006918 in platform data
Signed-off-by: Yinbo Zhu
---
include/linux/fsl_devices.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/fsl_devices.h b/include/linux/fsl_devices.h
index
On 1/23/2019 11:24 AM, Mike Rapoport wrote:
On Tue, Jan 22, 2019 at 03:12:54PM +0100, Marc Gonzalez wrote:
On 22/01/2019 15:02, Marc Gonzalez wrote:
On 21/01/2019 18:42, Mike Rapoport wrote:
If I understood correctly, the trouble comes from no-map range allocated in
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
net/wireless/wext-compat.c:1327:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
net/wireless/wext-compat.c:1341:6: warning:
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
Add the wrapper to support for interconnect path voting
from GENI QUP. This wrapper provides the functionalities
to individual Serial Engine device to get the interconnect
path and to vote for bandwidth based on their need.
This wrapper
Sparse reported warnings about non-static symbols. For the variables
a simple static attribute is fine - for the functions referenced by
livepatch via klp_func the symbol-names must be unmodified in the
symbol table and the patchable code has to be emitted. The resolution
is to attach __used
In case DOC_CHIPID_G3, mtd->name should be freed in the
err handling path, which is alloced by kasprintf.
Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
Signed-off-by: YueHaibing
---
drivers/mtd/devices/docg3.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Fix a static code checker warning:
drivers/mtd/devices/docg3.c:1875
doc_probe_device() warn: passing zero to 'ERR_PTR'
Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
Signed-off-by: YueHaibing
---
drivers/mtd/devices/docg3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Add PMIC configurations for backup battery charger, which
is a constant voltage and constant current style charger
with a series output resistance.
The max77620 register CNFGBBC(addr: 0x04) defines the
parameters of backup battery charger. This patch adds
support for it.
Signed-off-by: Laxman
This patch adds PMIC configurations for low-battery
monitoring by handling max77620 register CNFGGLBL1.
Signed-off-by: Laxman Dewangan
Signed-off-by: Venkat Reddy Talla
Signed-off-by: Mark Zhang
---
drivers/mfd/max77620.c | 57 +-
1 file changed, 56
On Tue, Jan 22, 2019 at 10:06:54PM +, Gary R Hook wrote:
> On 1/22/19 9:14 AM, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do something different based on
Fix a static code checker warning:
drivers/crypto/chelsio/chcr_algo.c:3681
chcr_aead_op() warn: passing zero to 'PTR_ERR'
Fixes: 2debd3325e55 ("crypto: chcr - Add AEAD algos.")
Signed-off-by: YueHaibing
---
drivers/crypto/chelsio/chcr_algo.c | 4 ++--
1 file changed, 2 insertions(+), 2
On 2019/1/23 上午11:49, Michael S. Tsirkin wrote:
On Wed, Jan 23, 2019 at 11:08:04AM +0800, Jason Wang wrote:
On 2019/1/23 上午1:03, Tiwei Bie wrote:
This patch introduces the support for VIRTIO_F_ORDER_PLATFORM.
When this feature is negotiated, driver will use the barriers
suitable for hardware
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
Add interconnect ports for GENI QUPs to set bus
capabilities.
Signed-off-by: Alok Chauhan
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
On Wed, Jan 23, 2019 at 11:15:16AM +0900, Masami Hiramatsu wrote:
> On Tue, 22 Jan 2019 16:21:46 +0100
> Greg Kroah-Hartman wrote:
>
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
Get the interconnect paths for Uart based Serial Engine device
and vote accordingly based on maximum supported Uart frequency.
Signed-off-by: Alok Chauhan
---
drivers/tty/serial/qcom_geni_serial.c | 27 ++-
1 file
Document the bindings used by the Renesas R-Car Gen3 RPC-IF controller.
Signed-off-by: Mason Yang
---
.../devicetree/bindings/spi/spi-renesas-rpc.txt| 46 ++
1 file changed, 46 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-renesas-rpc.txt
On 2019-01-22 14:43, Peter Rosin wrote:
On 2019-01-22 07:33, Alok Chauhan wrote:
Get the interconnect paths for I2C based Serial Engine device
and vote accordingly based on maximum supported I2C frequency.
Signed-off-by: Alok Chauhan
---
drivers/i2c/busses/i2c-qcom-geni.c | 13 +
Add a driver for Renesas R-Car Gen3 RPC-IF SPI controller.
Signed-off-by: Mason Yang
Signed-off-by: Sergei Shtylyov
---
drivers/spi/Kconfig | 6 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-renesas-rpc.c | 805 ++
3 files changed,
Hi Mark,
v7 patch is according to Geert and Sergei's comments:
1) Add all R-Car Gen3 model in dts.
2) patch rpc-if child node search.
3) minror coding style.
v6 patch is accroding to Geert, Marek and Sergei's comments:
1) spi_controller for new code.
2) "renesas,rcar-gen3-rpc" instead of
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
Add the wrapper to support for interconnect path voting
from GENI QUP. This wrapper provides the functionalities
to individual Serial Engine device to get the interconnect
path and to vote for bandwidth based on their need.
This wrapper
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
Add documentation for the interconnect and interconnect-names bindings
for the GENI QUP as detailed by bindings/interconnect/interconnect.txt.
Signed-off-by: Alok Chauhan
---
Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.txt | 10
On Tue, Jan 22, 2019 at 05:25:03PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 22, 2019 at 05:07:59PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2019-01-22 16:21:07 [+0100], Greg Kroah-Hartman wrote:
> > > diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> > > index
+Mark Brown
On 2019-01-22 12:03, Alok Chauhan wrote:
This patch series contains following:
* Add wrapper framework to support interconnect path from GENI QUPs.
This wrapper enabled and help individual SEs to put their BW request.
Adding this wrapper make sense because we don't want
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
drivers/block/drbd/drbd_int.h:1774:6: warning: this statement may fall through
[-Wimplicit-fallthrough=]
drivers/block/drbd/drbd_int.h:1774:6:
On Tue, Jan 22, 2019 at 11:24:25AM -0800, Guenter Roeck wrote:
> On Mon, Jan 21, 2019 at 02:41:54PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.4 release.
> > There are 111 patches in this series, all will be posted as a response
> > to this one.
On Tue, Jan 22, 2019 at 03:25:58PM -0700, shuah wrote:
> On 1/21/19 6:41 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.4 release.
> > There are 111 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Tue, Jan 22, 2019 at 03:29:33PM -0800, Omar Sandoval wrote:
> On Tue, Jan 22, 2019 at 04:21:04PM +0100, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do
On Wed, Jan 23, 2019 at 07:37:52PM +0800, Peng Hao wrote:
> Preparing for pvpanic driver framework. Create a pvpanic driver
> directory and move current driver file to new directory.
>
> Signed-off-by: Peng Hao
> ---
> drivers/misc/Kconfig | 9 +
> drivers/misc/Makefile
On Tue, Jan 22, 2019 at 02:42:26PM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 22, 2019 at 2:29 PM Rajat Jain wrote:
> >
> > Hi Marcel,
> >
> > On Sat, Jan 19, 2019 at 11:51 AM Marcel Holtmann
> > wrote:
> > >
> > > Hi Rajat,
> > >
> > > > In preparation for handling embedded USB devices let's
On Wed, Jan 23, 2019 at 07:33:05AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 23, 2019 at 09:11:41AM +0900, Masami Hiramatsu wrote:
> > On Tue, 22 Jan 2019 16:21:44 +0100
> > Greg Kroah-Hartman wrote:
> >
> > > When calling debugfs functions, there is no need to ever check the
> > > return
On Wed, Jan 23, 2019 at 09:11:41AM +0900, Masami Hiramatsu wrote:
> On Tue, 22 Jan 2019 16:21:44 +0100
> Greg Kroah-Hartman wrote:
>
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do
This controller appeared on Loongson-1 family MCUs
including Loongson-1B and Loongson-1C.
Signed-off-by: Jiaxun Yang
---
drivers/irqchip/Kconfig| 9 ++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-ls1x.c | 194 +
3 files changed, 204
Dt-bindings doc about Loongson-1 interrupt controller
Signed-off-by: Jiaxun Yang
---
.../loongson,ls1x-intc.txt| 28 +++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/loongson,ls1x-intc.txt
diff
v1->v2: Fix SPDX-License-Identifier
Sorry for the delayed review! >_<
On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
wrote:
>
> By historical reasons we defined firmware memory size to be 6MB even
> that the firmware size for all supported Venus versions is 5MBs. Correct
> that by compare the required firmware size returned from
On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
wrote:
>
> This corects maximum hardware load constant in per SoC resources
s/corect/correct. Same typo is present in patch title.
> for sdm845 aka Venus v4.
>
> Signed-off-by: Stanimir Varbanov
> ---
> drivers/media/platform/qcom/venus/core.c
On Wed, Jan 9, 2019 at 5:46 PM Stanimir Varbanov
wrote:
>
> The zero timestap is really a valid so not sure why I discarded it. Fix
s/timestap/timestamp, also in patch title.
> that mistake by drop the code which checks for zero timestamp.
s/drop/dropping
>
> Signed-off-by: Stanimir Varbanov
On 三, 2019-01-23 at 11:44 +1100, Joel Stanley wrote:
> Hello Rui,
>
> On Tue, 4 Dec 2018 at 02:12, Zhang Rui wrote:
> >
> > On 三, 2018-10-10 at 01:30 -0700, Matthew Garrett wrote:
> > >
> > > Platforms support more DPTF policies than the driver currently
> > > exposes.
> > > Add them. This
On Tue, Jan 22, 2019 at 03:12:54PM +0100, Marc Gonzalez wrote:
> On 22/01/2019 15:02, Marc Gonzalez wrote:
>
> > On 21/01/2019 18:42, Mike Rapoport wrote:
> >
> >> If I understood correctly, the trouble comes from no-map range allocated
> >> in
> >> early_init_dt_alloc_reserved_memory_arch().
> -Original Message-
> From: Greg Kroah-Hartman
> Sent: Tuesday, January 22, 2019 8:39 PM
> To: James Bottomley ; Martin Petersen
>
> Cc: linux-kernel@vger.kernel.org; linux-s...@vger.kernel.org; Greg Kroah-
> Hartman ; QLogic-Storage-
> upstr...@cavium.com
> Subject: [PATCH 6/7] scsi:
Hi Martin,
In commit
a8cf59a6692c ("scsi: communicate max segment size to the DMA mapping code")
Fixes tag
Fixes: 50c2e9107f ("scsi: introduce a max_segment_size host_template
parameters")
has these problem(s):
- SHA1 should be at least 12 digits long
--
Cheers,
Stephen Rothwell
Hi Tony,
In commit
5a1826e1b175 ("ARM: dts: am335x-shc.dts: fix wrong cd pin level")
Fixes tag
Fixes: e63201f19438 ("mmc: omap_hsmmc: Delete platform data
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
In commit
On Tue, Jan 22, 2019 at 11:47 PM Hans Verkuil wrote:
>
> On 01/22/19 11:02, Tomasz Figa wrote:
> > On Mon, Nov 12, 2018 at 8:37 PM Hans Verkuil wrote:
> >>
> >> Hi Tomasz,
> >>
> >> A general note for the stateful and stateless patches: they describe
> >> specific
> >> use-cases of the more
This patch adds Audio DT nodes for LS1028ARDB and LS1028AQDS boards.
Signed-off-by: Alison Wang
---
arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 62
arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts | 63 +
Hi all,
Changes since 20190122:
The vfs tree still had its build failure for which I applied a patch.
The netfilter-next tree lost its build failures.
The slave-dma tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 3027
3265 files changed, 99661
Hi Daniel,
On Fri, 21 Dec 2018 11:27:32 +0100
Daniel Bristot de Oliveira wrote:
> Currently, the patch of an address is done in three steps:
>
> -- Pseudo-code #1 - Current implementation ---
> 1) add an int3 trap to the address that will be patched
> sync cores (send IPI
Arend Van Spriel writes:
> The prefix should be 'brcmsmac'.
I can fix that during commit.
--
Kalle Valo
From: Nathan Chancellor
Date: Mon, 21 Jan 2019 21:23:01 -0700
> When building this code on a 32-bit platform such as ARM, there is a
> link time error (lld error shown, happpens with ld.bfd too):
>
> ld.lld: error: undefined symbol: __aeabi_uldivmod
referenced by devlink.c
From: Stefan Agner
Date: Mon, 21 Jan 2019 15:58:47 +0100
> According to the device tree binding the phy-supply property is
> optional. Use the regulator_get_optional API accordingly. The
> code already handles NULL just fine.
>
> This gets rid of the following warning:
> fec 2188000.ethernet:
Thanks Sudeep for reviewing. Please see my comment inline below.
On Mon, Jan 21, 2019 at 4:52 PM Sudeep Holla wrote:
>
> On Mon, Jan 21, 2019 at 11:28:27AM +0530, Pramod Kumar wrote:
> > On Fri, Jan 18, 2019 at 5:02 PM Sudeep Holla wrote:
> > > On Fri, Jan 18, 2019 at 11:16:20AM +0530, Pramod
From: Lubomir Rintel
Date: Mon, 21 Jan 2019 14:54:20 +0100
> This message gets logged far too often for how interesting is it.
>
> Most distributions nowadays configure NetworkManager to use randomly
> generated MAC addresses for Wi-Fi network scans. The interfaces end up
> being periodically
On Mon, Jan 21, 2019 at 10:50:32AM -0800, Shakeel Butt wrote:
> From the start of the git history of Linux, the kernel after selecting
> the worst process to be oom-killed, prefer to kill its child (if the
> child does not share mm with the parent). Later it was changed to prefer
> to kill a child
On Mon, 14 Jan 2019, Mathieu Malaterre wrote:
> There is a plan to build the kernel with -Wimplicit-fallthrough and
> this place in the code produced a warning (W=1).
>
> This commit remove the following warning:
>
> security/keys/keyring.c:248:10: warning: this statement may fall through
>
1 - 100 of 1233 matches
Mail list logo
