Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=168ec15660
kernel config: https://syzkaller.appspot.com/x/.
Add the clock tree definition for the new RK3308 SoC.
Signed-off-by: Finley Xiao
---
drivers/clk/rockchip/Makefile | 1 +
drivers/clk/rockchip/clk-rk3308.c | 955 ++
drivers/clk/rockchip/clk.h| 13 +
3 files changed, 969 insertions(+)
create mo
Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=174761b660
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=165e551e60
kernel config: https://syzkaller.appspot.com/x/.
Add devicetree bindings for Rockchip cru which found on
Rockchip SoCs.
Signed-off-by: Finley Xiao
---
.../devicetree/bindings/clock/rockchip,rk3308.txt | 58 ++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3308.txt
Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=173983ac60
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=14c3589e60
kernel config: https://syzkaller.appspot.com/x/.
Hello,
syzbot found the following crash on:
HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=101b49ea60
kernel config: https://syzkaller.appspot.com/x/.
If CONFIG_REGMAP_I2C is not set, building fails:
drivers/media/i2c/max2175.o: In function `max2175_probe':
max2175.c:(.text+0x1404): undefined reference to `__devm_regmap_init_i2c'
Select REGMAP_I2C to fix this.
Reported-by: Hulk Robot
Fixes: b47b79d8a231 ("[media] media: i2c: max2175: Add MAX2
If CONFIG_REGMAP_I2C is not set, building fails:
drivers/usb/typec/tps6598x.o: In function `tps6598x_probe':
tps6598x.c:(.text+0x5f0): undefined reference to `__devm_regmap_init_i2c'
Select REGMAP_I2C to fix this.
Reported-by: Hulk Robot
Fixes: 0a4c005bd171 ("usb: typec: driver for TI TPS6598x
Hi Daniel,
On Mon, Sep 2, 2019 at 10:42 AM Daniel Lezcano
wrote:
> On 02/09/2019 10:39, Geert Uytterhoeven wrote:
> > On Mon, Sep 2, 2019 at 10:32 AM Simon Horman wrote:
> >> On Fri, Aug 30, 2019 at 10:37:54AM +, Fabrizio Castro wrote:
> >>> This patch has been reviewed by Geert, Simon, and
From: Markus Elfring
Date: Tue, 3 Sep 2019 14:04:05 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
fs/befs/btr
On Tue, Sep 03, 2019 at 01:57:48PM +0200, Michal Hocko wrote:
> On Mon 02-09-19 03:23:40, William Kucharski wrote:
> > Add an 'order' argument to __page_cache_alloc() and
> > do_read_cache_page(). Ensure the allocated pages are compound pages.
>
> Why do we need to touch all the existing callers a
On Tue, Sep 03, 2019 at 10:42:59AM +0100, Ben Whitten wrote:
> You mentioned that we likely have breakage elsewhere, I believe that
> regmap_noinc_write probably shouldn't ever have been calling
> _regmap_raw_write.
> Whilst regmap_noinc_read calls _regmap_raw_read, this function doesn't
> do any
On Tue, Sep 3, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=165e5
On Tue, Sep 3, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=140a7
On Tue, Sep 3, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=16ab9
On Tue, Sep 3, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=168ec
On Mon 02-09-19 03:23:41, William Kucharski wrote:
> Add filemap_huge_fault() to attempt to satisfy page
> faults on memory-mapped read-only text pages using THP when possible.
This deserves much more description of how the thing is implemented and
expected to work. For one thing it is not really
On Tue, Sep 3, 2019 at 2:08 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:eea39f24 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=17398
On Tue 03-09-19 05:11:55, Matthew Wilcox wrote:
> On Tue, Sep 03, 2019 at 01:57:48PM +0200, Michal Hocko wrote:
> > On Mon 02-09-19 03:23:40, William Kucharski wrote:
> > > Add an 'order' argument to __page_cache_alloc() and
> > > do_read_cache_page(). Ensure the allocated pages are compound pages.
On Tue, Sep 03, 2019 at 02:14:24PM +0200, Michal Hocko wrote:
> On Mon 02-09-19 03:23:41, William Kucharski wrote:
> > Add filemap_huge_fault() to attempt to satisfy page
> > faults on memory-mapped read-only text pages using THP when possible.
>
> This deserves much more description of how the th
On Tue, Sep 03, 2019 at 08:10:26PM +0800, YueHaibing wrote:
> If CONFIG_REGMAP_I2C is not set, building fails:
>
> drivers/usb/typec/tps6598x.o: In function `tps6598x_probe':
> tps6598x.c:(.text+0x5f0): undefined reference to `__devm_regmap_init_i2c'
>
> Select REGMAP_I2C to fix this.
>
> Report
> > > > First, you only force the remap if the overlap is with NVS, but I
> > > > have systems where the overlap is with other reserved regions. You
> > > > should force the remap regardless, but if it is NVS, grab the space back
> > > > from NVS.
> > >
> > > I didn't know about that. I just found
On Sun, Aug 25, 2019 at 10:32 PM Alexandre Belloni
wrote:
> AT91 SoC for 5.4
>
> - MAINTAINERS updates
> - a generated headers parallel build fix
>
>
> Masahiro Yamada (1):
> ARM: at91: move platform-specific asm-offset.h to
From: Colin Ian King
There is a spelling mistake in a dev_warning message. Fix it. Also
break line to clear up checkpatch warning.
Signed-off-by: Colin Ian King
---
drivers/spi/spi-npcm-fiu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/spi-npcm-fiu.c b/dri
From: Markus Elfring
Date: Tue, 3 Sep 2019 14:24:38 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the tests around the shown calls are not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
fs
From: Markus Elfring
Date: Tue, 3 Sep 2019 14:24:38 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the tests around the shown calls are not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
fs
On Mon, 2019-09-02 at 14:38 +0100, Rob Herring wrote:
Hi Rob,
> On Wed, Aug 28, 2019 at 08:28:46PM +0800, Henry Chen wrote:
> > Add interconnect provider dt-bindings for MT8183.
> >
> > Signed-off-by: Henry Chen
> > ---
> > .../devicetree/bindings/soc/mediatek/dvfsrc.txt| 9 +
>
Hello Arthur and Laís,
Thanks for your patch!
On 9/1/19 4:40 PM, Arthur Moraes do Lago wrote:
> Add mean window size parameter for debayer filter as a control in
> vimc-debayer.
>
> vimc-debayer was patched to allow changing mean windows parameter
> of the filter without needing to reload the dr
On Tue, Sep 03, 2019 at 12:21:36AM -0400, Qian Cai wrote:
> The linux-next commit "fs/namei.c: keep track of nd->root refcount status”
> [1] causes boot panic on all
> architectures here on today’s linux-next (0902). Reverted it will fix the
> issue.
OK, I see what's going on. Incremental to
Thanks for your urgent response. My name is Stella Adams, a personal
secretary to John Paul. My boss left an envelope which contain bank card
worth of $800,000.00. The bank card will be used at any ATM machine across
the globe. Courier delivery company will deliver the parcel to your
doorstep. All
On Wed, Aug 21, 2019 at 9:52 AM Krzysztof Kozlowski wrote:
> On Fri, 16 Aug 2019 at 18:30, Krzysztof Kozlowski wrote:
> >
> > Samsung DTS ARM changes for v5.4
> >
> > 1. Add AHCI to Exynos5250,
> > 2. Add camera and GPU power domain
+CC Greg as fix for a patch in my outstanding pull request.
On Tue, 3 Sep 2019 07:18:02 +0200
Martin Kepplinger wrote:
> With the underscore character in the lsm9ds1_imu device name, we get the
> following error below, so use a dash, just like the other device names do too.
>
> [3.961399] U
From: Markus Elfring
Date: Tue, 3 Sep 2019 14:40:18 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
fs/ext2/sup
On Tue, Sep 03, 2019 at 12:04:03PM +0200, Oliver Neukum wrote:
> Am Dienstag, den 03.09.2019, 11:19 +0200 schrieb Greg KH:
> > On Tue, Sep 03, 2019 at 10:46:14AM +0200, Oliver Neukum wrote:
> > > Am Montag, den 02.09.2019, 18:47 +0200 schrieb Greg KH:
> > > >
> > > > This should work just fine tod
Hi,
Thank you for working on the patchset.
Since there is only one module now, the section in the vimc Documentation
regarding module params should be changed:
In the file Documentation/media/v4l-drivers/vimc.rst
The following text should be removed:
```
You should pass
those arguments to each s
On Tue 03-09-19 05:22:08, Matthew Wilcox wrote:
> On Tue, Sep 03, 2019 at 02:14:24PM +0200, Michal Hocko wrote:
> > On Mon 02-09-19 03:23:41, William Kucharski wrote:
> > > Add filemap_huge_fault() to attempt to satisfy page
> > > faults on memory-mapped read-only text pages using THP when possible
On 03.09.19 14:43, Jonathan Cameron wrote:
> +CC Greg as fix for a patch in my outstanding pull request.
>
> On Tue, 3 Sep 2019 07:18:02 +0200
> Martin Kepplinger wrote:
>
>> With the underscore character in the lsm9ds1_imu device name, we get the
>> following error below, so use a dash, just li
On Tue, 2019-09-03 at 07:54 +, Jonas Karlman wrote:
[...]
> After a closer look both ffmpeg and rkmpp only apply zig-zag scan and not
> field scan,
> ffmpeg will memcpy the scaling_matrix4/8 as is for vaapi, vdpau and nvdec,
> for dxva2 there is a workaround flag that controls if zig-zag shoul
From: Andrei Leonchikov
Signed-off-by: Andrei Leonchikov
---
drivers/pci/pci.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 1b27b5af3..ed5f0888c 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -3149,9 +3149,12
On 9/3/19 6:50 AM, Dafna Hirschfeld wrote:
Hi,
Thank you for working on the patchset.
Since there is only one module now, the section in the vimc Documentation
regarding module params should be changed:
In the file Documentation/media/v4l-drivers/vimc.rst
The following text should be removed:
From: Markus Elfring
Date: Tue, 3 Sep 2019 14:56:16 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
fs/fat/dir.
On Mon, 2 Sep 2019, Joe Lawrence wrote:
> On 9/2/19 12:13 PM, Miroslav Benes wrote:
> >> I can easily foresee more problems like those in the future. Going
> >> forward we have to always keep track of which special sections are
> >> needed for which architectures. Those special sections can chan
Ingo or Peter, please take a look at this trivial patch. Still see the warning
in linux-next every day.
On Tue, 2019-08-20 at 14:40 -0400, Qian Cai wrote:
> The linux-next commit "sched/fair: Fix low cpu usage with high
> throttling by removing expiration of cpu-local slices" [1] introduced a
> fe
On Tue, Sep 03, 2019 at 01:37:19PM +0100, Al Viro wrote:
> On Tue, Sep 03, 2019 at 12:21:36AM -0400, Qian Cai wrote:
> > The linux-next commit "fs/namei.c: keep track of nd->root refcount status”
> > [1] causes boot panic on all
> > architectures here on today’s linux-next (0902). Reverted it will
Hi!
On Tue, Sep 03, 2019 at 03:23:57PM +1000, Alastair D'Silva wrote:
> diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
> +#if !defined(CONFIG_PPC_8xx) & !defined(CONFIG_PPC64)
Please write that as &&? That is more usual, and thus, easier to read.
> +static void flush_dcache_icache_
From: Richard Gong
This is the 5th submission of Intel Stratix10 remote system update (RSU)
driver.
Intel Stratix10 remote system update driver patches have been reviewed by
Alan Tull and other colleagues at Intel.
The Intel Stratix10 Remote System Update driver exposes interfaces
access throug
On Mon 2019-09-02 11:32:39, Sakari Ailus wrote:
> Add support for %pfw conversion specifier (with "f" and "P" modifiers) to
> support printing full path of the node, including its name ("f") and only
> the node's name ("P") in the printk family of functions. The two flags
> have equivalent function
From: Richard Gong
The Intel Remote System Update (RSU) driver exposes interfaces access
through the Intel Service Layer to user space via sysfs interface.
The RSU interfaces report and control some of the optional RSU features
on Intel Stratix 10 SoC.
The RSU feature provides a way for customer
On 09/02, Eric W. Biederman wrote:
>
> @@ -1644,7 +1644,7 @@ static void task_numa_compare(struct task_numa_env *env,
> return;
>
> rcu_read_lock();
> - cur = task_rcu_dereference(&dst_rq->curr);
> + cur = rcu_dereference(dst_rq->curr);
> if (cur && ((cur->flags
From: Richard Gong
Extend Intel Stratix10 service layer driver to support new RSU notify and
MAX_RETRY with watchdog event.
RSU is used to provide our customers with protection against loading bad
bitstream onto their devices when those devices are booting from flash
RSU notifies provides users
From: Richard Gong
Describe Intel Stratix10 Remote System Update (RSU) device attributes
Signed-off-by: Richard Gong
Reviewed-by: Alan Tull
---
v2: changed to use tab everywhere and wrap lines at 72 columns
s/soc:firmware:svc:rsu/stratix10-rsu.0
added for watchdog
v3: s/KernelVersion:5
"Valdis wrote:
> Fix spurious warning message when building with W=1:
>
> CC [M] drivers/net/wireless/realtek/rtlwifi/usb.o
> drivers/net/wireless/realtek/rtlwifi/usb.c:243: warning: Cannot understand *
> on line 243 - I thought it was a doc line
> drivers/net/wireless/realtek/rtlwifi/usb.c:
From: Richard Gong
Add myself as maintainer for the newly created Intel Stratix10
firmware drivers.
Signed-off-by: Richard Gong
Reviewed-by: Alan Tull
---
v2: removed RSU binding text file
v3: no change
v4: no change
v5: s/richard.g...@intel.com/richard.g...@linux.intel.com
---
MAINTAINERS |
The `phy_tunable_id` has been named `ETHTOOL_PHY_EDPD` since it looks like
this feature is common across other PHYs (like EEE), and defining
`ETHTOOL_PHY_ENERGY_DETECT_POWER_DOWN` seems too long.
The way EDPD works, is that the RX block is put to a lower power mode,
except for link-pulse detection
This driver becomes the first user of the kernel's `ETHTOOL_PHY_EDPD`
phy-tunable feature.
EDPD is also enabled by default on PHY config_init, but can be disabled via
the phy-tunable control.
When enabling EDPD, it's also a good idea (for the ADIN PHYs) to enable TX
periodic pulses, so that in cas
This change syncs the `ethtool-copy.h` file with Linux net-next to add
support for Energy Detect Powerdown control via phy tunable.
Some formatting also changes with this sync.
Signed-off-by: Alexandru Ardelean
---
ethtool-copy.h | 13 +
1 file changed, 9 insertions(+), 4 deletions(
This patch series is actually 2 series in 1.
First 2 patches implement the kernel support for controlling Energy Detect
Powerdown support via phy-tunable, and the next 2 patches implement the
ethtool user-space control.
Hopefully, this combination of 2 series is an acceptable approach; if not,
I a
This change adds control for enabling/disabling Energy Detect Power Down
mode, as well as configuring wake-up intervals for TX pulses, via the new
ETHTOOL_PHY_EDPD control added in PHY tunable, in the kernel.
Signed-off-by: Alexandru Ardelean
---
ethtool.8.in | 28 +
ethtool.c
Hello get back to me urgently
On 2019-09-03 10:03:35 [+0200], To Clark Williams wrote:
> anything in a brief test. What I saw however is that switching to
> fullscreen while playing a video gives me ~0.5 to ~2ms latency. This is
> has nothing to do with this change, I have to dig deeper… It might be
> one of the preempt_disable
On Tue, Sep 3, 2019 at 12:44 PM Krzysztof Kozlowski wrote:
>
> On Tue, 3 Sep 2019 at 11:00, Rob Herring wrote:
> >
> > On Tue, Sep 3, 2019 at 8:47 AM Krzysztof Kozlowski wrote:
> > >
> > > On Tue, 3 Sep 2019 at 09:14, Rob Herring wrote:
> > > >
> > > > On Mon, Sep 2, 2019 at 4:03 PM Krzysztof K
On Tue, Sep 03, 2019 at 12:53:15PM +, Andrei Leonvikov wrote:
> + if ((dev->driver != NULL) && (strncmp(dev->driver->name, "nvme", 4) ==
> 0)) {
> + // for NVME device this field always zero, but ARI can be
> enabled
> + pcie_capability_read_dword(bridge, PCI_EXP_D
On Tue, Sep 03, 2019 at 10:46:09AM +0200, Christoph Hellwig wrote:
> Hi all,
>
> the first patch fixes the ohci-sm501 regression that Guenther reported
> due to the platform device dma_mask changes. The second one ports that
> fix to another driver that works the same way. The rest cleans up
> v
On Tue 03-09-19 16:27:46, sunqiuyang wrote:
> From: Qiuyang Sun
>
> Currently, after a page is migrated, it
> 1) has its PG_isolated flag cleared in move_to_new_page(), and
> 2) is deleted from its LRU list (cc->migratepages) in unmap_and_move().
> However, between steps 1) and 2), the page could
On Tue, Sep 03, 2019 at 03:28:49PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 2 Sep 2019 14:26:40 + "Lendacky, Thomas"
> wrote:
> > Maybe we should make this mem_encrypt_active(), since this will probably
> > be needed if/when an IOMMU device is eventually added to a guest, and the
On Sun, 2019-09-01 at 12:45 +, Jonas Karlman wrote:
> This need code cleanup and formatting
>
> Signed-off-by: Jonas Karlman
The previous patches all work, but this patch breaks decoding of
progressive content for me (i.MX8MQ with FFmpeg based on Ezequiel's
branch).
regards
Philipp
> ---
>
On Fri 30-08-19 18:15:22, Eric Dumazet wrote:
> If there is a risk of flooding the syslog, we should fix this generically
> in mm layer, not adding hundred of __GFP_NOWARN all over the places.
We do already ratelimit in warn_alloc. If it isn't sufficient then we
can think of a different parameters
Hi Peter,
There is one question regarding following commit:
commit 69d927bba39517d0980462efc051875b7f4db185
Author: Peter Zijlstra
Date: Wed Apr 24 13:38:23 2019 +0200
x86/atomic: Fix smp_mb__{before,after}_atomic()
Recent probing at the Linux Kernel Memory Model uncovered a
'sur
On 9/3/19 12:39 PM, Joao Martins wrote:
> Hey,
>
> Presented herewith a series with aims to tie in together the haltpoll
> idle driver and governor, without sacrificing previous governor setups.
> In addition, there are a few fixes with respect to module loading for
> cpuidle-haltpoll.
>
> The s
The recently introduced haltpoll driver is largely only useful with
haltpoll governor. To allow drivers to associate with a particular idle
behaviour, add a @governor property to 'struct cpuidle_driver' and thus
allow a cpuidle driver to switch to a *preferred* governor on idle driver
registration.
When a user loads cpuidle-haltpoll on a non KVM guest the module will
successfully load, even though idle driver registration didn't take
place.
We should instead return -ENODEV signaling the user that the driver can't
be loaded, like other error paths in haltpoll_init(). An example of such
error
Hey,
Presented herewith a series with aims to tie in together the haltpoll
idle driver and governor, without sacrificing previous governor setups.
In addition, there are a few fixes with respect to module loading for
cpuidle-haltpoll.
The series is organized as follows:
Patch 1: Allows idle dr
On Tue, Sep 03, 2019 at 02:39:44PM +0800, zhong jiang wrote:
> kmemdup contains the kmalloc + memcpy. hence it is better to use kmemdup
> directly. Just replace it.
>
> Signed-off-by: zhong jiang
This same patch was already sent to me by someone else and I acked it:
https://lore.kernel.org/lkml
cpuidle-haltpoll can be built as a module to allow optional late load.
Given we are setting @owner to THIS_MODULE, cpuidle will attempt to grab a
module reference every time a cpuidle_device is registered -- so
essentially all online cpus get a reference.
This prevents for the module to be unloade
On Tue, Sep 03, 2019 at 04:06:33PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 3ae92b3782182d282a92573abe95c96d34ca6e73 ("btrfs: change the minimum
> global reserve size")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/li
Right now, guest current governors have the following ratings:
* ladder-> 10
* teo -> 19
* menu -> 20
* haltpoll -> 21
* ladder + nohz=off -> 25
haltpoll governor got introduced and it is now the default governor given
its highest rating -- wit
This new trace option "console-latency" will enable the latency
tracers to trace the console latencies. Previously this has always been
implicitely disabled. I guess this is because they are considered
to be well known and unavoidable.
However, for some organizations it may nevertheless be desirab
Hello all,
Changes in v5:
- [PATCH 1/4]:
* trace_disable_fsnotify() => latency_fsnotify_disable(), in order to avoid
naming conflicts with trace points.
* Using more appropriate operations for the percpu variables.
* Moved around the calls to latency_fsnotify_enable/disable() a bit.
This is a tool that is intended to work around the fact that the
preemptoff, irqsoff, and preemptirqsoff tracers only work in
overwrite mode. The idea is to act randomly in such a way that we
do not systematically lose any latencies, so that if enough testing
is done, all latencies will be captured
This patch implements the feature that the tracing_max_latency file,
e.g. /sys/kernel/debug/tracing/tracing_max_latency will receive
notifications through the fsnotify framework when a new latency is
available.
One particularly interesting use of this facility is when enabling
threshold tracing, t
This burst feature enables the user to generate a burst of
preempt/irqsoff latencies. This makes it possible to test whether we
are able to detect latencies that systematically occur very close to
each other.
The maximum burst size is 10. We also create 10 identical test
functions, so that we get
On Tue, Sep 03, 2019 at 10:46:10AM +0200, Christoph Hellwig wrote:
> This driver doesn't support normal DMA, only direct access to its
> local memory. Remove the HCD_DMA flag to properly express that fact.
>
> Fixes: 1e4946c4412e ("usb: add a HCD_DMA flag instead of guestimating DMA
> capabiliti
YueHaibing wrote:
> drivers/net/wireless/realtek/rtlwifi/efuse.c:16:31:
> warning: RTL8712_SDIO_EFUSE_TABLE defined but not used
> [-Wunused-const-variable=]
> drivers/net/wireless/realtek/rtlwifi/efuse.c:9:17:
> warning: MAX_PGPKT_SIZE defined but not used [-Wunused-const-variable=]
>
> They
I saw Christ start to remove npu-dma.c code [1]
[1] https://lore.kernel.org/linuxppc-dev/20190625145239.2759-4-...@lst.de/
Should pnv_npu_dma_set_32() be removed too?
It was only called by pnv_npu_try_dma_set_bypass() but the later is not used
anywhere in the kernel tree. If that is a case, I do
On Tue, 3 Sep 2019 at 15:12, Rob Herring wrote:
> > arch/arm/boot/dts/exynos3250-artik5-eval.dt.yaml: syscon-reboot:
> > {'regmap': [[9]], 'mask': [[1]], '$nodename': ['syscon-reboot'],
> > 'value': [[1]], 'offset': [[1024]], 'compatible': ['syscon-reboot']}
> > is valid under each of {'required':
On Tue, Sep 03, 2019 at 09:29:14AM -0400, Qian Cai wrote:
> I saw Christ start to remove npu-dma.c code [1]
>
> [1] https://lore.kernel.org/linuxppc-dev/20190625145239.2759-4-...@lst.de/
>
> Should pnv_npu_dma_set_32() be removed too?
>
> It was only called by pnv_npu_try_dma_set_bypass() but th
On Tue, Sep 03, 2019 at 01:37:19PM +0100, Al Viro wrote:
> On Tue, Sep 03, 2019 at 12:21:36AM -0400, Qian Cai wrote:
> > The linux-next commit "fs/namei.c: keep track of nd->root refcount status”
> > [1] causes boot panic on all
> > architectures here on today’s linux-next (0902). Reverted it will
On Tue, Sep 03, 2019 at 08:54:02PM +0800, Brad Campbell wrote:
> On 3/9/19 7:55 pm, Mika Westerberg wrote:
> > On Tue, Sep 03, 2019 at 07:11:32PM +0800, Brad Campbell wrote:
> >
> > I think the problem is that for some reason, probably because this is
> > first generation hardware with all the bug
Colin King wrote:
> From: Colin Ian King
>
> Pointer debugfs_topdir is initialized to a value that is never read
> and it is re-assigned later. The initialization is redundant and can
> be removed.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King
Patch applied to wire
Jia-Ju Bai wrote:
> In wlc_phy_radio_init_2056(), regs_SYN_2056_ptr, regs_TX_2056_ptr and
> regs_RX_2056_ptr may be not assigned, and thus they are still NULL.
> Then, they are used on lines 20042-20050:
> wlc_phy_init_radio_regs(pi, regs_SYN_2056_ptr, (u16) RADIO_2056_SYN);
> wlc_phy_i
The kernel has plenty of ternary operators to choose between constant
strings, such as condition ? "yes" : "no", as well as value == 1 ? "" :
"s":
$ git grep '? "yes" : "no"' | wc -l
258
$ git grep '? "on" : "off"' | wc -l
204
$ git grep '? "enabled" : "disabled"' | wc -l
196
$ git grep '? "" : "s
THIS IS NOT FOR MERGING; DEMO FOR PREVIOUS PATCH ONLY!
Further conversion should be done incrementally and by
driver/subsystem. This here is the result of running the following on
the below cocci patch:
$ spatch --sp-file yesno.cocci --in-place --dir drivers/gpu/drm
I wish I knew how to not dupl
The intention seems to be to warn once when we don't wait enough for the
reset to complete. Let's use the right retry counter to accomplish that
semantic.
Signed-off-by: Halil Pasic
---
drivers/s390/crypto/vfio_ap_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/
YueHaibing wrote:
> drivers/bcma/driver_mips.c:70:18: warning:
> ipsflag_irq_shift defined but not used [-Wunused-const-variable=]
> drivers/bcma/driver_mips.c:62:18: warning:
> ipsflag_irq_mask defined but not used [-Wunused-const-variable=]
>
> They are never used, so can be removed.
>
> Re
On Mon 2019-09-02 11:32:40, Sakari Ailus wrote:
> Add a test for the %pfw printk modifier using software nodes.
>
> Signed-off-by: Sakari Ailus
> Reviewed-by: Andy Shevchenko
> ---
> lib/test_printf.c | 37 +
> 1 file changed, 37 insertions(+)
>
> diff --git
Colin King wrote:
> From: Colin Ian King
>
> The pointer hash is being initialized with a value that is never read
> and is being re-assigned a little later on. The assignment is
> redundant and hence can be removed.
>
> Addresses-Coverity: ("Unused value")
> Signed-off-by: Colin Ian King
Pa
Wenwen Wang wrote:
> In proc_BSSList_open(), 'file->private_data' is allocated through kzalloc()
> and 'data->rbuffer' is allocated through kmalloc(). In the following
> execution, if an error occurs, they are not deallocated, leading to memory
> leaks. To fix this issue, free the allocated memor
* H. Nikolaus Schaller [190902 10:56]:
> Matching the ti-cpufreq driver needs to specify explicitly if
> a board uses an omap34xx or omap36xx chip.
>
> Signed-off-by: H. Nikolaus Schaller
> ---
> arch/arm/boot/dts/omap3-beagle.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> dif
301 - 400 of 1216 matches
Mail list logo
