Now that we have everything in place, we can get rid of the
memory_access abstraction layer.
Now, everything related to heterogeneous memory management
(hmm) is under hmm.c & related pools.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/Makefile| 1 -
.../stagin
From: Nathan Chancellor
Clang warns:
../drivers/staging/media/atomisp/pci/atomisp_v4l2.c:1097:3: warning:
variable 'count' is incremented both in the loop header and in the loop
body [-Wfor-loop-analysis]
count++;
^
This was probably unintentional, remove it.
Li
The hmm code is partially based on a fork from 3.10 code,
and has bugs.
Add debug there to help tracking what happens there.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/staging/media/atomisp/pci/hmm/hmm_bo.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/staging/media/ato
> Some processes dont't want to be killed early, but in "Action Required"
> case, those also may be killed by BUS_MCEERR_AO when sharing memory
> with other which is accessing the fail memory.
> And sending SIGBUS with BUS_MCEERR_AO for action required error is
> strange, so ignore the non-current
On Sat, May 30, 2020 at 08:33:50AM +0200, Heiner Kallweit wrote:
> It *was* default y. This changed with a914ff2d78ce ("PCI/ASPM: Don't
> select CONFIG_PCIEASPM by default") and that's what triggered the
> problem. If there's no easy solution, then maybe it's best to revert
> the change for now.
Hi there,
When I was trying to create dts for my platform that need PCI
DeviceTree sub node to express interrupt of children devices under the
bridge, like this:
pci@1a00 {
compatible = "loongson,ls7a-pci";
device_type = "pci";
#address-cells = <3>;
#size-cells = <2>;
#int
The dev_id used in 'request_irq()' and 'free_irq()' should match.
So use 'host' in both cases.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Christophe JAILLET
---
drivers/scsi/arm/powertec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/arm/powertec.
From: Liao Pingfang
The message should just be dropped as the call will print the failure
message anyway.
Signed-off-by: Liao Pingfang
---
changes in v2: remove the message instead of changing it.
drivers/misc/mic/host/mic_main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/misc
The dev_id used in 'request_irq()' and 'free_irq()' should match.
So use 'host' in both cases.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Christophe JAILLET
---
drivers/scsi/arm/eesox.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/arm/eesox.c b/dr
The dev_id used in 'request_irq()' and 'free_irq()' should match.
So use 'host' in both cases.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Christophe JAILLET
---
drivers/scsi/arm/cumana_2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/arm/cumana_2.
DW Watchdog IP core can be synthesised with asynchronous timer/APB
clocks support (WDT_ASYNC_CLK_MODE_ENABLE == 1). In this case
separate clock signals are supposed to be used to feed watchdog timer
and APB interface of the device. Currently the driver supports
the synchronous mode only. Since ther
DW Watchdog IP core can be synthesised with asynchronous timer/APB
clocks support (WDT_ASYNC_CLK_MODE_ENABLE == 1). In this case
separate clock signals are supposed to be used to feed watchdog timer
and APB interface of the device. Let's update the DW Watchdog DT node
schema so it would support the
In case if the DW Watchdog IP core is synthesised with
WDT_USE_FIX_TOP == false, the TOP interval indexes make the device
to load a custom periods to the counter. These periods are hardwired
at the IP synthesis stage and can be within [2^8, 2^(WDT_CNT_WIDTH - 1)].
Alas their values can't be detecte
DW Watchdog can rise an interrupt in case if IRQ request mode is enabled
and timer reaches the zero value. In this case the IRQ lane is left
pending until either the next watchdog kick event (watchdog restart) or
until the WDT_EOI register is read or the device/system reset. This
interface can be u
Modern device tree bindings are supposed to be created as YAML-files
in accordance with dt-schema. This commit replaces the DW Watchdog
legacy bare text bindings with YAML file. As before the binding states
that the corresponding dts node is supposed to have a registers
range, a watchdog timer refe
Merge window is upon us. Please review/merge in/whatever the rest of the
patches.
There were a few features enabled at the time of the Baikal-T1 SoC DW WDT
IP synthesis, which weren't taken into account in the DW WDT driver available
in the kernel. First of all the SoC engineers synthesized the wa
In case if DW Watchdog IP core is built with WDT_USE_FIX_TOP == false,
a custom timeout periods are used to preset the timer counter. In
this case that periods should be specified in a new "snps,watchdog-tops"
property of the DW watchdog dts node.
Signed-off-by: Serge Semin
Reviewed-by: Rob Herri
For the sake of the easier device-driver debug procedure, we added a
DebugFS file with the controller registers state. It's available only if
kernel is configured with DebugFS support.
Signed-off-by: Serge Semin
Reviewed-by: Guenter Roeck
Cc: Alexey Malahov
Cc: Thomas Bogendoerfer
Cc: Arnd Ber
Peter Zijlstra writes:
> On Fri, May 29, 2020 at 06:07:11PM +0200, Peter Zijlstra wrote:
>> Like with KCSAN, we should blanket kill KASAN/UBSAN and friends (at the
>> very least in arch/x86/) until they get that function attribute stuff
>> sorted.
>
> Something like so.
We have noinstr in kernel/
On 2020-05-22 20:59, John Hubbard wrote:
This code was using get_user_pages*(), in a "Case 1" scenario
(Direct IO), using the categorization from [1]. That means that it's
time to convert the get_user_pages*() + put_page() calls to
pin_user_pages*() + unpin_user_pages() calls.
There is some help
The value aiptek->data is stored in DMA memory, and it is assigned to
data. Thus in the code:
macro = get_unaligned_le16(data + 1);
The value of marco can be modified by malicious hardware.
In this case, buffer overflow may occur when the code
"macroKeyEvents[macro - 1]" and "macroKeyEvents[macro
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 2234ae846ccb9ebdf4c391824cb79e73674dceda
Gitweb:
https://git.kernel.org/tip/2234ae846ccb9ebdf4c391824cb79e73674dceda
Author:Anup Patel
AuthorDate:Mon, 18 May 2020 14:44:40 +05:30
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 0e375f51017bcc86c23979118b10445c424ef5ad
Gitweb:
https://git.kernel.org/tip/0e375f51017bcc86c23979118b10445c424ef5ad
Author:Anup Patel
AuthorDate:Mon, 18 May 2020 14:44:41 +05:30
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: c5d6082d35e0bcc20a26a067ffcfddcb5257e580
Gitweb:
https://git.kernel.org/tip/c5d6082d35e0bcc20a26a067ffcfddcb5257e580
Author:Marc Zyngier
AuthorDate:Fri, 15 May 2020 17:57:52 +01:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 5c8f77a278737a6af44a892f0700d9aadb2b0de0
Gitweb:
https://git.kernel.org/tip/5c8f77a278737a6af44a892f0700d9aadb2b0de0
Author:Bartosz Golaszewski
AuthorDate:Thu, 14 May 2020 10:39:00 +02:00
Comm
The following commit has been merged into the irq/core branch of tip:
Commit-ID: ae0bb9fda405c881848f7f6e94d912b35f6e31d2
Gitweb:
https://git.kernel.org/tip/ae0bb9fda405c881848f7f6e94d912b35f6e31d2
Author:Shaokun Zhang
AuthorDate:Mon, 18 May 2020 11:00:59 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 82f2202ddc97490994fad0dbfec04a014fa5163d
Gitweb:
https://git.kernel.org/tip/82f2202ddc97490994fad0dbfec04a014fa5163d
Author:Wesley W. Terpstra
AuthorDate:Tue, 12 May 2020 10:26:36 -07:00
Commi
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1
Gitweb:
https://git.kernel.org/tip/337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1
Author:Bartosz Golaszewski
AuthorDate:Thu, 14 May 2020 10:39:01 +02:00
Comm
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 87526603c89256e18ad2c23821fdaf376b072fc8
Gitweb:
https://git.kernel.org/tip/87526603c89256e18ad2c23821fdaf376b072fc8
Author:Andy Shevchenko
AuthorDate:Wed, 20 May 2020 19:49:26 +03:00
Committe
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 2f13ff1d1d5c0257c97ea76b86a2d9c99c44a4b9
Gitweb:
https://git.kernel.org/tip/2f13ff1d1d5c0257c97ea76b86a2d9c99c44a4b9
Author:Marc Zyngier
AuthorDate:Fri, 15 May 2020 17:57:51 +01:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 8a94c1ab34d53476617f83610521cfb6674db8d4
Gitweb:
https://git.kernel.org/tip/8a94c1ab34d53476617f83610521cfb6674db8d4
Author:Ingo Rohloff
AuthorDate:Wed, 22 Apr 2020 13:28:57 +02:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 9ed78b05f998050784ae863bd5ba4aea2e2141ed
Gitweb:
https://git.kernel.org/tip/9ed78b05f998050784ae863bd5ba4aea2e2141ed
Author:Andy Shevchenko
AuthorDate:Wed, 20 May 2020 19:49:27 +03:00
Committe
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 128516e49de67d10d52fba62ef8d482b220ac4b0
Gitweb:
https://git.kernel.org/tip/128516e49de67d10d52fba62ef8d482b220ac4b0
Author:Dan Carpenter
AuthorDate:Wed, 20 May 2020 15:03:06 +03:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 181e9d4efaf6aa8d1e7d510aeb7114c0f276fad7
Gitweb:
https://git.kernel.org/tip/181e9d4efaf6aa8d1e7d510aeb7114c0f276fad7
Author:Andy Shevchenko
AuthorDate:Wed, 20 May 2020 19:49:25 +03:00
Committe
The following commit has been merged into the irq/core branch of tip:
Commit-ID: cc86432aa8cc5a81f99d79eea2a29099da694df3
Gitweb:
https://git.kernel.org/tip/cc86432aa8cc5a81f99d79eea2a29099da694df3
Author:Valentin Schneider
AuthorDate:Thu, 21 May 2020 23:35:00 +01:00
Commi
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 818e915fbac518e8c78e1877a0048d92d4965e5a
Gitweb:
https://git.kernel.org/tip/818e915fbac518e8c78e1877a0048d92d4965e5a
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:49 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 2458ed31e9b9ab40d78a452ab2650a0857556e85
Gitweb:
https://git.kernel.org/tip/2458ed31e9b9ab40d78a452ab2650a0857556e85
Author:Anup Patel
AuthorDate:Mon, 18 May 2020 14:44:39 +05:30
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 6c2832c3c6edc38ab58bad29731b4951c0a90cf8
Gitweb:
https://git.kernel.org/tip/6c2832c3c6edc38ab58bad29731b4951c0a90cf8
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:50 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: b6e4bc125fc517969f97d901b1845ebf47bbea26
Gitweb:
https://git.kernel.org/tip/b6e4bc125fc517969f97d901b1845ebf47bbea26
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:52 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 632dcc2c75ef6de3272aa4ddd8f19da1f1ace323
Gitweb:
https://git.kernel.org/tip/632dcc2c75ef6de3272aa4ddd8f19da1f1ace323
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:53 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: ef8c01eb64ca6719da449dab0aa9424e13c58bd0
Gitweb:
https://git.kernel.org/tip/ef8c01eb64ca6719da449dab0aa9424e13c58bd0
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:51 +08:00
Committer:
The following commit has been merged into the irq/core branch of tip:
Commit-ID: da10a4b626657387845f32d37141fc7d48ebbdb3
Gitweb:
https://git.kernel.org/tip/da10a4b626657387845f32d37141fc7d48ebbdb3
Author:Jiaxun Yang
AuthorDate:Thu, 28 May 2020 23:27:54 +08:00
Committer:
Hi Florian,
Am 29.05.20 um 21:15 schrieb Florian Fainelli:
> Leverage the IRQCHIP_MASK_ON_SUSPEND flag in order to avoid having to
> specifically treat the GPIO interrupts during suspend and resume, and
> simply implement an irq_set_wake() callback that is responsible for
> enabling the parent wak
On Sat, May 30, 2020 at 03:34:01PM +0800, Yi Wang wrote:
> From: Liao Pingfang
>
> The message should just be dropped as the call will print the failure
> message anyway.
>
> Signed-off-by: Liao Pingfang
> ---
> changes in v2: remove the message instead of changing it.
>
> drivers/misc/mic/ho
On Sat, May 30, 2020 at 5:52 AM Nathan Chancellor
wrote:
> On Fri, May 29, 2020 at 10:15:51PM +0200, Arnd Bergmann wrote:
> > strcat(buf, "Threads\tTime(ns)\n");
> >
> > for (exp = 0; exp < nruns; exp++) {
> > + u64 avg;
> > + u32 rem;
> > +
> > if
On 5/29/20 7:53 PM, Rich Felker wrote:
> Frustratingly, I _still_ don't have an official tree on kernel.org for
> the purpose of being the canonical place for linux-next to pull from,
> due to policies around pgp keys and nobody following up on signing
> mine. This is all really silly since there a
MediaTek IOMMU block diagram always like below:
M4U
|
smi-common
|
-
| | ...
| |
larb1 larb2
| |
vdec venc
All the consumer connect with smi-larb, then connect with smi-common.
MediaTek IOMMU don't have its powe
From: Maoguang Meng
Update binding document since the avc and vp8 hardware encoder in
mt8173 are now separated. Separate "mediatek,mt8173-vcodec-enc" to
"mediatek,mt8173-vcodec-vp8-enc" and "mediatek,mt8173-vcodec-avc-enc".
This is a preparing patch for smi cleaning up "mediatek,larb".
Signed-o
The iommu consumer should use device_link to connect with the
smi-larb(supplier). then the smi-larb should run before the iommu
consumer. Here we delay the iommu driver until the smi driver is
ready, then all the iommu consumer always is after the smi driver.
When there is no this patch, if some c
MediaTek IOMMU don't have its power-domain. all the consumer connect
with smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-
| |...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should en
After adding device_link between the consumer with the smi-larbs,
if the consumer call its owner pm_runtime_get(_sync), the
pm_runtime_get(_sync) of smi-larb and smi-common will be called
automatically. Thus, the consumer don't need the property.
And IOMMU also know which larb this consumer connec
MediaTek IOMMU has already added device_link between the consumer
and smi-larb device. If the jpg device call the pm_runtime_get_sync,
the smi-larb's pm_runtime_get_sync also be called automatically.
CC: Rick Chang
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drivers/media/platform/mtk-j
Normally, If the smi-larb HW need work, we should enable the smi-common
HW power and clock firstly.
This patch adds device-link between the smi-larb dev and the smi-common
dev. then If pm_runtime_get_sync(smi-larb-dev), the pm_runtime_get_sync
(smi-common-dev) will be called automatically.
Also, A
From: Maoguang Meng
MTK H264 Encoder(VENC_SYS) and VP8 Encoder(VENC_LT_SYS) are two
independent hardware instance. They have their owner interrupt,
register mapping, and special clocks.
This patch seperates the two instance. This is a preparing patch for
adding device_link between the larbs and
From: Yongqiang Niu
Display use the dispsys device to call pm_rumtime_get_sync before.
This patch add pm_runtime_xx with ovl and rdma device whose nodes has
"iommus" property, then display could help pm_runtime_get for smi via
ovl or rdma device.
This is a preparing patch that smi cleaning up "m
MediaTek IOMMU has already added the device_link between the consumer
and smi-larb device. If the mdp device call the pm_runtime_get_sync,
the smi-larb's pm_runtime_get_sync also be called automatically.
CC: Minghsiu Tsai
CC: Houlong Wei
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
driv
MediaTek IOMMU has already added the device_link between the consumer
and smi-larb device. If the vcodec device call the pm_runtime_get_sync,
the smi-larb's pm_runtime_get_sync also be called automatically.
CC: Tiffany Lin
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
.../media/platform/m
After adding device_link between the iommu consumer and smi-larb,
the pm_runtime_get(_sync) of smi-larb and smi-common will be called
automatically. we can get rid of mtk_smi_larb_get/put.
CC: Matthias Brugger
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drivers/memory/mtk-smi.c | 14 -
From: Irui Wang
There are two separate hardware encoder blocks inside MT8173. Split
the current mtk-vcodec-enc node to match the hardware architecture.
Signed-off-by: Irui Wang
Signed-off-by: Hsin-Yi Wang
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 60 +---
1 fi
MediaTek IOMMU has already added the device_link between the consumer
and smi-larb device. If the drm device call the pm_runtime_get_sync,
the smi-larb's pm_runtime_get_sync also be called automatically.
CC: CK Hu
CC: Philipp Zabel
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
drivers/gp
After adding device_link between the IOMMU consumer and smi,
the mediatek,larb is unnecessary now.
CC: Matthias Brugger
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
arch/arm/boot/dts/mt2701.dtsi | 1 -
arch/arm/boot/dts/mt7623.dtsi | 1 -
2 files changed, 2 deletions(-)
diff --git a/arc
MediaTek IOMMU should wait for smi larb which need wait for the
power domain(mtk-scpsys.c) and the multimedia ccf, both are module
init. Thus, subsys_initcall for MediaTek IOMMU is not helpful.
Switch to module_platform_driver.
Correspondingly, add the module license information.
Signed-off-by: Y
smi-larb driver should run after smi-common, Use device_is_bound to confirm
whether smicommon driver is ready.
CC: Matthias Brugger
Signed-off-by: Yong Wu
---
drivers/memory/mtk-smi.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/mtk-smi.c b/drivers/m
After adding device_link between the IOMMU consumer and smi,
the mediatek,larb is unnecessary now.
CC: Matthias Brugger
Signed-off-by: Yong Wu
Reviewed-by: Evan Green
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 16
1 file changed, 16 deletions(-)
diff --git a/arch/arm64/bo
'ret' is known to be 0 at this point.
So, explicitly return -ENOMEM if one of the 'ecardm_iomap()' calls fail.
Fixes: e95a1b656a98 ("[ARM] rpc: acornscsi: update to new style ecard driver")
Signed-off-by: Christophe JAILLET
---
drivers/scsi/arm/acornscsi.c | 4 +++-
1 file changed, 3 insertions(
The tail call optimization can unexpectedly make the stack smaller and
cause the test to fail.
Signed-off-by: Ian Rogers
---
tools/perf/tests/dwarf-unwind.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tools/perf/tests/dwarf-unwind.c b/tools/perf/tests/dwarf-unw
Tail call optimizations can remove stack frames that are used in
unwinding tests. Add an attribute that can be used to disable the tail
call optimization. Tested on clang and GCC.
Signed-off-by: Ian Rogers
---
tools/include/linux/compiler-gcc.h | 8
tools/include/linux/compiler.h |
Avoid a false positive caused by assembly code in arch/x86.
In tests, zero the perf_event to avoid uninitialized memory uses.
Warnings were caught using clang with -fsanitize=memory.
Signed-off-by: Ian Rogers
---
tools/perf/arch/x86/tests/dwarf-unwind.c | 8
tools/perf/tests/dwarf-unwin
Fix stack frame count and memory sanitizer issues when running the
dwarf unwinding test with the elfutils/libdw unwinder (libunwind
disabled).
Ian Rogers (3):
tools compiler.h: Add attribute to disable tail calls
perf tests: Don't tail call optimize in unwind test
perf test: Initialize memor
s/locksapce/lockspace/
Signed-off-by: Christophe JAILLET
---
fs/dlm/lockspace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
index e93670ecfae5..f17e091daab3 100644
--- a/fs/dlm/lockspace.c
+++ b/fs/dlm/lockspace.c
@@ -859,7 +859,7 @
On Thu, May 28, 2020 at 09:01:55AM +0200, Ard Biesheuvel wrote:
> On Thu, 28 May 2020 at 01:23, Russell King - ARM Linux admin
> wrote:
> >
> > Ard,
> >
> > Please take a look. Obviously, whatever the resolution is going to be
> > needed when Linus opens the merge window.
> >
>
> Sorry for that.
Hi Jean-Baptiste,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on robh/for-next linus/master v5.7-rc7 next-20200529]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also s
On Sat, May 30, 2020 at 3:49 AM Andy Shevchenko
wrote:
>
> On Sat, May 30, 2020 at 1:11 AM Syed Nayyar Waris
> wrote:
> > On Sat, May 30, 2020 at 3:13 AM Andy Shevchenko
> > wrote:
> > > On Fri, May 29, 2020 at 11:07 PM Syed Nayyar Waris
> > > wrote:
> > > > On Sat, May 30, 2020 at 12:08 AM A
On Sat, May 30, 2020 at 10:08 AM John Paul Adrian Glaubitz
wrote:
> On 5/29/20 7:53 PM, Rich Felker wrote:
> > Frustratingly, I _still_ don't have an official tree on kernel.org for
> > the purpose of being the canonical place for linux-next to pull from,
> > due to policies around pgp keys and no
On Sat, 30 May 2020 at 10:41, Russell King - ARM Linux admin
wrote:
>
> On Thu, May 28, 2020 at 09:01:55AM +0200, Ard Biesheuvel wrote:
> > On Thu, 28 May 2020 at 01:23, Russell King - ARM Linux admin
> > wrote:
> > >
> > > Ard,
> > >
> > > Please take a look. Obviously, whatever the resolution
In 1394 OHCI specification, Isochronous Receive DMA context has several
modes. One of mode is 'BufferFill' and Linux FireWire stack uses it to
receive isochronous packets for multiple isochronous channel as
FW_ISO_CONTEXT_RECEIVE_MULTICHANNEL.
The mode is not used by in-kernel driver, while it's a
On Sat, May 30, 2020 at 10:51:32AM +0200, Ard Biesheuvel wrote:
> On Sat, 30 May 2020 at 10:41, Russell King - ARM Linux admin
> wrote:
> >
> > On Thu, May 28, 2020 at 09:01:55AM +0200, Ard Biesheuvel wrote:
> > > On Thu, 28 May 2020 at 01:23, Russell King - ARM Linux admin
> > > wrote:
> > > >
>
On Sat, May 30, 2020 at 11:45 AM Syed Nayyar Waris wrote:
> On Sat, May 30, 2020 at 3:49 AM Andy Shevchenko
> wrote:
...
> I am still investigating more on this. Let me know if you have any
> suggestions.
As far as I understand the start pointers are implementations of abs()
macro followed by
On 29-05-20, 22:17, Arnd Bergmann wrote:
> An uninitialized pointer is passed into another function but
> ignored there:
>
> drivers/opp/core.c:875:32: error: variable 'opp' is uninitialized when used
> here [-Werror,-Wuninitialized]
> ret = _set_opp_bw(opp_table, opp, dev, true);
Em Fri, 29 May 2020 22:31:44 +0200
Arnd Bergmann escreveu:
> On Fri, May 29, 2020 at 10:23 PM Arnd Bergmann wrote:
> >
> > On Fri, May 29, 2020 at 10:04 PM 'Nick Desaulniers' via Clang Built
> > Linux wrote:
> > >
> > > See also Nathan's 7 patch series.
> > > https://lore.kernel.org/lkml/2020
> To fix these possible bugs, index is checked before being used.
How do you think about a wording variant like the following?
Thus check the index before using it further.
Would you like to add the tag “Fixes” to the commit message?
Regards,
Markus
Hi!
> On Fri, May 29, 2020 at 06:02:04PM +0200, Pavel Machek wrote:
> > > ping?
> >
> > Well, I thought that we maybe do not need standard LEDs on medical hardware.
>
> The discussion died and the patch was not applied :) In general
> IDK how worthwhile it is to use standard LED names for them.
From: Huaisheng Ye
When wc_entry has been removed from wbl->list in writeback, it will
be not used again except waiting to be set free in writecache_free_entry.
That is a little of annoying, it has to reinitialize lru of wc_entry
in endio before calling writecache_free_entry.
Using list_del_ini
From: Yue Hu
There is no need to goto out to check ret if it's an invalid io request
since we know ret = -EINVAL. Let's return the error directly in that
case.
Signed-off-by: Yue Hu
---
drivers/block/zram/zram_drv.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drive
> + addr = reg & 0x3FFFU;
> + snprintf(unit_addr, sizeof(unit_addr), "%x", addr);
Hmm, this hardcoded value will not work if we ever need to add another
bit. I hope this will never happen, though.
> + if ((reg & (1U << 31)) && addr > 0x3ff)
Same here with bit 31. I haven
Hi Oscar,
On 2020-05-29 18:18, Oscar Carter wrote:
In an effort to enable -Wcast-function-type in the top-level Makefile
to
support Control Flow Integrity builds, there are the need to remove all
the function callback casts.
To do this, modify the IRQCHIP_ACPI_DECLARE macro to use the new
def
Just double checking:
> Signed-off-by: Serge Semin
> Reviewed-by: Rob Herring
Rob, what about this checkpatch warning?
WARNING: DT binding documents should be licensed (GPL-2.0-only OR BSD-2-Clause)
signature.asc
Description: PGP signature
Fixes: 4ffea5e083f8 ("regulator: max8998: Add charger regulator")
Signed-off-by: kbuild test robot
---
max8998.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/max8998.c b/drivers/regulator/max8998.c
index 668ced0064179..ab16790a02068 100644
--- a/drive
If the cdrom fails to be registered then the device minor should be
deallocated.
Signed-off-by: Simon Arlott
---
drivers/scsi/sr.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
index 8d062d4f3ce0..1e13c6a0f0ca 100644
--- a/drivers/
If the device minor cannot be allocated or the cdrom fails to be
registered then the mutex should be destroyed.
Signed-off-by: Simon Arlott
---
drivers/scsi/sr.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/sr.c b/drivers/scsi/sr.c
index d2fe3fa470f9..8d062d4f3ce0 100644
---
On Sat, May 30, 2020 at 09:35:55AM +0200, Christophe JAILLET wrote:
> The dev_id used in 'request_irq()' and 'free_irq()' should match.
> So use 'host' in both cases.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Christophe JAILLET
This is itself wrong. cumanascsi_2_intr() requi
Please avoid typos in the patch subject.
> To fix this possible bug, sfr->buf_size is assigned to a local variable,
> and then this variable is checked before being used.
How do you think about a wording variant like the following?
Thus assign the data structure member “buf_size” to a local v
Hi Russell,
On Sat, 30 May 2020 10:17:47 +0100 Russell King - ARM Linux admin
wrote:
>
> I don't know - I don't have a resolution for the first one, Stephen
> didn't provide a 3-way diff with his report, and I was expecting a
> 3-way diff from you for it rather than another pull request.
There
Having mixer control to switch between DMICs prevents user to
initiate capture simultaneously on both the DMIcs.
Earlier 2 separate devices, one for each DMIC, gave an option of
using them simultaneously, which is not supported.
Signed-off-by: Akshu Agrawal
---
v2: Modified "Front Mic" to "DMIC S
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 87aa9b64e0ccb779db3970e2e9af1cc5930c2c3d
Gitweb:
https://git.kernel.org/tip/87aa9b64e0ccb779db3970e2e9af1cc5930c2c3d
Author:Lai Jiangshan
AuthorDate:Fri, 29 May 2020 23:27:32 +02:00
Committer
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 9a06f99a03a0f961047bbae4ee80ce9265757bfe
Gitweb:
https://git.kernel.org/tip/9a06f99a03a0f961047bbae4ee80ce9265757bfe
Author:Lai Jiangshan
AuthorDate:Fri, 29 May 2020 23:27:31 +02:00
Committer
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 92a6521bf846dd08768bc4de447b79e8bd2cdb2f
Gitweb:
https://git.kernel.org/tip/92a6521bf846dd08768bc4de447b79e8bd2cdb2f
Author:Lai Jiangshan
AuthorDate:Fri, 29 May 2020 23:27:30 +02:00
Committer
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: f841aea13b3ba6d7ad19b1d0744593e2d2448d2f
Gitweb:
https://git.kernel.org/tip/f841aea13b3ba6d7ad19b1d0744593e2d2448d2f
Author:Thomas Gleixner
AuthorDate:Thu, 28 May 2020 16:53:16 +02:00
Committ
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 83f7a80367e99cca0023be95538635abacec07ae
Gitweb:
https://git.kernel.org/tip/83f7a80367e99cca0023be95538635abacec07ae
Author:Lai Jiangshan
AuthorDate:Fri, 29 May 2020 23:27:29 +02:00
Committer
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: ff98610a03285516b578821549973f969118d6a3
Gitweb:
https://git.kernel.org/tip/ff98610a03285516b578821549973f969118d6a3
Author:Peter Zijlstra
AuthorDate:Fri, 29 May 2020 23:27:35 +02:00
Committe
1 - 100 of 406 matches
Mail list logo