On Thu, Aug 02, 2018 at 01:06:19PM -0700, Dave Hansen wrote:
> On 08/02/2018 12:54 PM, Peter Zijlstra wrote:
> >> I totally understand not wanting to fill the tree with code hijacking
> >> the raw PMU. Is your reaction to this really around not wanting to
> >> start down the slippery slope that
On Wed, Aug 1, 2018 at 5:49 PM John David Anglin wrote:
>
> On 2018-08-01 6:18 PM, Nick Desaulniers wrote:
> >> What about the uses in the fs support, etc?
> > Sorry, I don't see it?
> I mean _THIS_IP_.
I don't understand, I'm referring to current_text_addr(). Maybe this
explains more what I'm
On Thu, Aug 2, 2018 at 1:21 PM Jerome Brunet wrote:
>
> On Thu, 2018-08-02 at 09:52 +0200, Neil Armstrong wrote:
> > On 01/08/2018 22:23, Martin Blumenstingl wrote:
> > > Hi Neil,
> > >
> > > On Wed, Aug 1, 2018 at 12:05 PM Neil Armstrong
> > > wrote:
> > > >
> > > > The Amlogic Meson GX and
Hi Peter,
On 8/2/2018 1:13 PM, Peter Zijlstra wrote:
> On Thu, Aug 02, 2018 at 01:06:19PM -0700, Dave Hansen wrote:
>> On 08/02/2018 12:54 PM, Peter Zijlstra wrote:
I totally understand not wanting to fill the tree with code hijacking
the raw PMU. Is your reaction to this really around
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 402016 ("Missing break in switch")
Addresses-Coverity-ID: 1056542 ("Missing break in switch")
Addresses-Coverity-ID: 1339579 ("Missing break in switch")
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 115075 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
sound/isa/es18xx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/isa/es18xx.c
Quoting Dmitry Osipenko (2018-07-24 09:42:19)
> Kernel should never gate the EMC clock as it causes immediate lockup, so
> removing clk-gate functionality doesn't affect anything. Turning EMC clk
> gate into divider allows to implement glitch-less EMC scaling, avoiding
> reparenting to a backup
Quoting Dmitry Osipenko (2018-07-24 09:42:20)
> Ensure that direct PLLM sourcing is turned off for EMC as we don't support
> that configuration in the clk driver.
>
> Signed-off-by: Dmitry Osipenko
> Acked-by: Peter De Schrijver
> ---
Acked-by: Stephen Boyd
On Wed, Aug 1, 2018 at 1:12 PM Florian Eckert wrote:
> Add a new device driver "gpio-apu" which will now handle the GPIOs on
> APU2 and APU3 devices from PC Engines.
>
> - APU2/APU3 -> front button reset support
> - APU3 -> SIM switch support
>
> Signed-off-by: Florian Eckert
Hi Florian,
Allocate a temporary cgroup storage to use for bpf program test runs.
Because the test program is not actually attached to a cgroup,
the storage is allocated manually just for the execution
of the bpf program.
If the program is executed multiple times, the storage is not zeroed
on each run,
On Thu, Aug 02, 2018 at 06:31:06PM +0100, Alan Jenkins wrote:
> Hi
>
> I found this interesting, though I don't entirely follow the kernel
> mount/unmount code. I had one puzzle about the code, and two questions
> which I was largely able to answer.
>
> On 01/08/18 16:24, David Howells wrote:
>
On Thu, Aug 02, 2018 at 06:16:48PM +0200, Christoph Hellwig wrote:
> On Thu, Aug 02, 2018 at 05:08:38PM +0100, Al Viro wrote:
> > On Thu, Aug 02, 2018 at 06:08:16PM +0200, Christoph Hellwig wrote:
> > > On Thu, Aug 02, 2018 at 05:00:32PM +0100, Al Viro wrote:
> > > > BTW, what happens if we insert
On Wed, Aug 1, 2018, 4:26 PM Rishabh Bhatnagar
wrote:
> When calling request_firmware_into_buf() with the FW_OPT_NOCACHE flag
> it is expected that firmware is loaded into buffer from memory.
> But inside alloc_lookup_fw_priv every new firmware that is loaded is
> added to the firmware cache
On 08/02/2018 03:19 AM, Alexey Brodkin wrote:
> Otherwise kernel uses random MAC which is not very conveniet.
Curious what exactly is the issue - why does the user care what MAC is assigned
?
> With that change in place use might set desired MAC in U-Boot
> with "setenv ethaddr
Hello RT Folks!
This is the RT stable review cycle of patch 3.18.117-rt105-rc1.
In addition to the applicable stable-rt patches not yet in the 3.18-rt
kernel, this set includes some patches needed to fix cross-compilation
build failures.
Please scream at me if I messed something up. Please test
On 8/2/18 4:51 AM, Christoph Hellwig wrote:
From: Palmer Dabbelt
The RISC-V ISA defines a per-hart real-time clock and timer, which is
present on all systems. The clock is accessed via the 'rdtime'
pseudo-instruction (which reads a CSR), and the timer is set via an SBI
call.
Contains various
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/Kconfig
between commit:
1572497cb0e6 ("kconfig: include common Kconfig files from top-level Kconfig")
from the kbuild tree and commit:
6c359eb1dcdb ("MIPS: Allow auto-dection of ARCH_PFN_OFFSET &
On 2018-08-01 07:04, Rob Herring wrote:
On Tue, Jul 31, 2018 at 12:22 PM Prakruthi Deepak Heragu
wrote:
Documentation for Embedded USB Debugger (EUD) device tree bindings.
If you want bindings reviewed, send them to the correct list and
people (hint: run get_maintainers.pl).
New bindings
On Wed, Aug 1, 2018 at 2:55 PM, Hugh Dickins wrote:
> On Wed, 1 Aug 2018, Kirill A. Shutemov wrote:
>> On Wed, Aug 01, 2018 at 11:31:52AM -0700, Hugh Dickins wrote:
>> > On Wed, 1 Aug 2018, Linus Torvalds wrote:
>> > >
>> > > Anyway, the upshot of all this is that I think I know what the ia64
>>
On Thu, Aug 02, 2018 at 09:10:11PM +0200, Máté Eckl wrote:
> On Thu, Aug 02, 2018 at 09:05:57PM +0200, Máté Eckl wrote:
> > Hi Randy,
> >
> > Thanks for reporting!
> >
> > Please find the patch attached.
>
> Sorry I made an error in the commit message... See the fix below.
Please, resubmit
On 2018-08-02 05:07, Georgi Djakov wrote:
Hi Saravana,
On 08/02/2018 01:57 AM, skan...@codeaurora.org wrote:
On 2018-07-31 09:13, Georgi Djakov wrote:
Currently we support only platform data for specifying the
interconnect
endpoints. As now the endpoints are hard-coded into the consumer
2018-08-02 20:53 GMT+01:00 Dmitry Safonov <0x7f454...@gmail.com>:
> Hi Ivan,
>
> 2018-07-31 1:56 GMT+01:00 Ivan Delalande :
>> We were seeing unexplained segfaults in coreutils processes and other
>> basic utilities that we tracked down to binfmt_elf failing to load
>> segments for ld.so. Digging
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1165394 ("Missing break in switch")
Addresses-Coverity-ID: 1167851 ("Missing break in switch")
Addresses-Coverity-ID: 402015 ("Missing break in switch")
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1468367 ("Missing break in switch")
Addresses-Coverity-ID: 115037 ("Missing break in switch")
Addresses-Coverity-ID: 115038 ("Missing break in switch")
On Thu, 02 Aug 2018 14:00:52 +0300 Kirill Tkhai wrote:
> In case of shrink_slab_memcg() we do not zero nid, when shrinker
> is not numa-aware. This is not a real problem, since currently
> all memcg-aware shrinkers are numa-aware too (we have two:
> super_block shrinker and workingset shrinker),
On Thu, 2 Aug 2018 14:11:12 +0900 Minchan Kim wrote:
> If zram supports writeback feature, it's no more syncrhonous
> device beause zram does synchronous IO opeation for
> incompressible page.
>
> Do not pretend to be syncrhonous IO device. It makes system
> very sluggish as waiting IO
On 02/08/18 23:05, Will Deacon wrote:
> On Thu, Aug 02, 2018 at 09:45:26AM +1200, Chris Packham wrote:
>> GCC warns
>>
>>arm_pmu_platform.c:234:5: error: 'err' may be used uninitialized in this
>> function [-Werror=maybe-uninitialized]
>>
>> This is because we rely on the for_each_cpu loop in
Hi Baolin,
Thank you for addressing review remarks.
I've played a bit with the interface and I have one conclusion
regarding pattern parsing, please refer below.
Also one tiny optimization request in pattern_trig_activate().
On 08/01/2018 11:01 AM, Baolin Wang wrote:
> Some LED controllers
On Thu, Aug 2, 2018 at 12:44 PM wrote:
>
> On 2018-08-01 07:04, Rob Herring wrote:
> > On Tue, Jul 31, 2018 at 12:22 PM Prakruthi Deepak Heragu
> > wrote:
> >>
> >> Documentation for Embedded USB Debugger (EUD) device tree bindings.
> >
> > If you want bindings reviewed, send them to the correct
Current checkpatch implementation permits notation like:
} else{
in kernel code.
It looks like oversight and inconsistency in checkpatch rules (e.g.
instruction like 'do' is tested).
Add regex for checking space after 'else' keyword and trigger error if
space is not present.
Signed-off-by:
This reverts commit 3b5cf23e6b87a938522eb074baeb034e66dc9cb3.
Similar to commit d5bc2c7b2cc0 Revert "fs: jbd2: pull your plug when
waiting for space", according to Sebastian Siewior: this "is the same
thing but for ext3/jbd. The code was removed at some point so I did
not revert in my tree."
From: Julia Cartwright
Currently, the squashfs multi_cpu decompressor makes use of
get_cpu_ptr()/put_cpu_ptr(), which unconditionally disable preemption
during decompression.
Because the workload is distributed across CPUs, all CPUs can observe a
very high wakeup latency, which has been seen to
From: Sebastian Andrzej Siewior
In commit ("net: move xmit_recursion to per-task variable on -RT") the
recursion level was changed to be per-task since we can get preempted in
BH on -RT. The lock owner should consequently be recorded as the task
that holds the lock and not the CPU. Otherwise we
From: Peter Zijlstra
It's unused:
$ git grep "\" | wc -l
1
And dangerous, kill the bugger.
Cc: stable...@vger.kernel.org
Acked-by: Thomas Gleixner
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Sebastian Andrzej Siewior
(cherry picked from commit
From: Sebastian Andrzej Siewior
NEON in kernel mode is used by the crypto algorithms and raid6 code.
While the raid6 code looks okay, the crypto algorithms do not: NEON
is enabled on first invocation and may allocate/free/map memory before
the NEON mode is disabled again.
This needs to be
From: Sebastian Andrzej Siewior
On RT the timer can be preempted while running and therefore we wait
with timer_wait_for_callback() for the timer to complete (instead of
busy looping). The RCU-readlock is held to ensure that this posix timer
is not removed while we wait on it.
If the timer is
From: Sebastian Andrzej Siewior
If alarm_try_to_cancel() requires a retry, then depending on the
priority setting the retry loop might prevent timer callback completion
on RT. Prevent that by waiting for completion on RT, no change for a
non RT kernel.
Cc: stable...@vger.kernel.org
From: Sebastian Andrzej Siewior
During the stable update the arm architecture did not compile anymore
due to missing definition of u16/32.
Cc: stable...@vger.kernel.org
Signed-off-by: Sebastian Andrzej Siewior
(cherry picked from commit 1289b06974d64f244a26455fab699c6a1332f4bc)
Signed-off-by:
From: Julia Cartwright
The mainline implementation of read_seqbegin() orders prior loads w.r.t.
the read-side critical section. Fixup the RT writer-boosting
implementation to provide the same guarantee.
Also, while we're here, update the usage of ACCESS_ONCE() to use
READ_ONCE().
Fixes:
From: Philipp Schrader
With PREEMPT_RT and most of the lockdep-related options enabled I
encountered this splat when booting our DRA7 evaluation module:
[0.055073]
[0.055076] ===
[0.055079] [ INFO: suspicious RCU usage. ]
[0.055084] 4.1.6+ #2 Not
Quoting Steve Longerbeam (2018-07-18 10:56:51)
>
>
> On 07/06/2018 11:23 AM, Stephen Boyd wrote:
> > Quoting Steve Longerbeam (2018-05-31 18:59:17)
> >> Add checks in the .round_rate and .set_rate ops for zero requested
> >> rate or zero parent rate. If either are zero in .round_rate, just
> >>
On Tue, Jul 31, 2018 at 10:13 AM Georgi Djakov wrote:
>
> This binding is intended to represent the interconnect hardware present
> in some of the modern SoCs. Currently it consists only of a binding for
> the interconnect hardware devices (provider).
If you want the bindings reviewed, then you
Alan Jenkins wrote:
> Another closely-related limitation of `mount`, is that it can't atomically set
> the propagation type at mount time.
I want to add a mount_setattr() too at some point:
fd = open_tree(..., OPEN_TREE_CLONE);
mount_setattr(fd, ...);
move_mount(fd,
This implements the worst-case compression size querying interface for
lz4hc, based on the logic originally used by pstore.
Signed-off-by: Kees Cook
---
crypto/lz4hc.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/crypto/lz4hc.c b/crypto/lz4hc.c
Now that the crypto compression API has a zbufsize interface, use that
instead, so pstore doesn't need to keep getting updated for each new
compression algo that gets added to the kernel. This reorganizes the
code slightly at initialization time (since we must allocate the algo
first now), but
This implements the worst-case compression size querying interface for
zstd, based on the logic originally used by pstore.
Signed-off-by: Kees Cook
---
crypto/zstd.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/crypto/zstd.c b/crypto/zstd.c
index
On 2018/07/31 14:09, Michal Hocko wrote:
> On Tue 31-07-18 06:01:48, Tetsuo Handa wrote:
>> On 2018/07/31 4:10, Michal Hocko wrote:
>>> Since should_reclaim_retry() should be a natural reschedule point,
>>> let's do the short sleep for PF_WQ_WORKER threads unconditionally in
>>> order to guarantee
Redefinition of qca_uart_setup will help future Qualcomm Bluetooth
SoC, to use the same function instead of duplicating the function.
Added new arguments soc_type and soc_ver to the functions.
These arguments will help to decide type of firmware files
to be loaded into Bluetooth chip.
soc_type
On 2018-08-02 03:13, MyungJoo Ham wrote:
This driver registers itself as a devfreq device that allows devfreq
governors to make bandwidth votes for an interconnect path. This
allows
applying various policies for different interconnect paths using
devfreq
governors.
First of all, the name,
In function qca_setup, we set initial and operating speeds for Qualcomm
Bluetooth SoC's. This block of code is common across different
Qualcomm Bluetooth SoC's. Instead of duplicating the code, created
a wrapper function to set the speeds. So that future coming SoC's
can use these wrapper
This patch enables the RAM and NV patch download for wcn3990.
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Matthias Kaehlcke
---
drivers/bluetooth/btqca.c | 25 +
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a/drivers/bluetooth/btqca.c
Enable Qualcomm chips to operate at 3.2Mbps.
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Matthias Kaehlcke
---
drivers/bluetooth/hci_qca.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
index
Some of the QCA BTSoC ROME functions, are used for different versions
or different make of BTSoC's. Instead of duplicating the same functions
for new chip, update names of the functions that are used for both
chips to keep this generic and would help in future when we would have
new BT SoC. To
These patches enables Bluetooth functinalties for new Qualcomm
Bluetooth chip wnc3990. As this is latest chip with new features,
along with some common features to old chip "qcom,qca6174-bt".
we have updated names of functions that are used for both the chips
to keep this generic and would help
This patch enables regulators for the Qualcomm Bluetooth wcn3990
controller.
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Rob Herring
Reviewed-by: Stephen Boyd
---
Changes in v13:
* Segregated optional and required properties for wcn3990.
---
.../bindings/net/qualcomm-bluetooth.txt
On Thu, 2 Aug 2018, Parthiban Nallathambi wrote:
> Add support for VCNL4035, which is capable of Ambient light
> sensing (ALS) and proximity function. This patch adds support
> only for ALS function
comment below
> Signed-off-by: Parthiban Nallathambi
>
> Changelog since v1:
>
> 1. Fixed
Hi
I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a
strange problem.
When I use the links browser in graphics mode on the framebuffer, I get
occasional pixel corruption. Links does memcpy, memset and 4-byte writes
on the framebuffer - nothing else.
I found out that
Hello,
it is not clear to me why 'white' is needed;
isn't that the default, i.e. unfiltered light?
thanks, regards, p.
> Signed-off-by: Parthiban Nallathambi
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 7 +++
> drivers/iio/industrialio-core.c | 1 +
>
On Thu, Aug 02, 2018 at 09:41:35PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 02, 2018 at 12:09:46PM -0700, Guenter Roeck wrote:
> > On Thu, Aug 02, 2018 at 11:25:17AM -0700, Guenter Roeck wrote:
> > > On Thu, Aug 02, 2018 at 08:43:25AM -0700, Guenter Roeck wrote:
> > > > On Wed, Aug 01, 2018
The parallel data bus is a simple parallel bus
that may be used to drive displays.
It is mostly used in simple embedded systems
but is also used in some desings utilising Linux.
Signed-off-by: Sam Ravnborg
---
.../bindings/pardata/parallel-data-bus.txt | 60 ++
1
From: Sean Wang
This adds a driver based on serdev driver for the MediaTek serial protocol
based on running H:4, which can enable the built-in Bluetooth device inside
MT7622 SoC.
Signed-off-by: Sean Wang
---
drivers/bluetooth/Kconfig | 11 +
drivers/bluetooth/Makefile| 2 +
On Thu, Aug 02, 2018 at 09:41:35PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 02, 2018 at 12:09:46PM -0700, Guenter Roeck wrote:
> > On Thu, Aug 02, 2018 at 11:25:17AM -0700, Guenter Roeck wrote:
> > > On Thu, Aug 02, 2018 at 08:43:25AM -0700, Guenter Roeck wrote:
> > > > On Wed, Aug 01, 2018
The easiest explanation for this would be that the memory isn’t mapped
correctly. You can’t use PCIe memory spaces with anything other than
Device-nGnRE or stricter mappings. That’s just differences between the AMBA
and PCIe (posted/unposted) memory models.
Normal memory (cacheable or
Quoting Amit Daniel Kachhap (2018-07-30 22:55:55)
> This fix rounds the clock rate properly by using quotient and not
> remainder in the calculation. This issue was found while testing HDMI
> in the Juno platform.
>
> Fixes: 6d6a1d82eaef7 ("clk: add support for clocks provided by SCMI")
>
On Fri, Aug 03, 2018 at 01:40:43AM +0530, Balakrishna Godavarthi wrote:
> On 2018-08-03 01:27, Matthias Kaehlcke wrote:
> > On Fri, Aug 03, 2018 at 12:37:32AM +0530, Balakrishna Godavarthi wrote:
> > > Add support to set voltage/current of various regulators
> > > to power up/down Bluetooth chip
On 2018-08-02 02:56, MyungJoo Ham wrote:
Many CPU architectures have caches that can scale independent of the
CPUs.
Frequency scaling of the caches is necessary to make sure the cache is
not
a performance bottleneck that leads to poor performance and power. The
same
idea applies for RAM/DDR.
Quoting Michal Simek (2018-07-30 05:50:42)
> On 26.7.2018 18:36, Stephen Boyd wrote:
> > Quoting Michal Simek (2018-07-25 02:51:14)
> >> On 24.7.2018 20:14, Jolly Shah wrote:
> > create mode 100644 drivers/firmware/xilinx/zynqmp-debug.h
> > create mode 100644
On 8/2/18 4:50 AM, Christoph Hellwig wrote:
From: Palmer Dabbelt
This patch adds documentation for the platform-level interrupt
controller (PLIC) found in all RISC-V systems. This interrupt
controller routes interrupts from all the devices in the system to each
hart-local interrupt
Hi all,
Today's linux-next merge of the dma-mapping tree got a conflict in:
arch/nios2/Kconfig
between commit:
17c46a6aff5c ("kconfig: remove duplicate SWAP symbol defintions")
from the kbuild tree and commit:
25622e045a6a ("nios2: use generic dma_noncoherent_ops")
from the
The mm-of-the-moment snapshot 2018-08-02-15-29 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Chanwoo,
On Thu, Aug 02, 2018 at 10:58:59AM +0900, Chanwoo Choi wrote:
> Hi Matthias,
>
> On 2018년 08월 02일 02:08, Matthias Kaehlcke wrote:
> > Hi Chanwoo,
> >
> > On Wed, Aug 01, 2018 at 10:22:16AM +0900, Chanwoo Choi wrote:
> >> On 2018년 08월 01일 04:39, Matthias Kaehlcke wrote:
> >>> On Mon,
Hi Jonathan,
Sorry for the delay, I've been away from keyboard for a few days.
On Sun, Jul 29, 2018 at 12:44:22PM +0100, Jonathan Cameron wrote:
> On Tue, 24 Jul 2018 20:30:02 +0200
> Marcus Folkesson wrote:
>
> > MCP3911 is a dual channel Analog Front End (AFE) containing two
> > synchronous
On Thu, Aug 02, 2018 at 12:09:46PM -0700, Guenter Roeck wrote:
> On Thu, Aug 02, 2018 at 11:25:17AM -0700, Guenter Roeck wrote:
> > On Thu, Aug 02, 2018 at 08:43:25AM -0700, Guenter Roeck wrote:
> > > On Wed, Aug 01, 2018 at 06:48:30PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of
On 2018-08-03 01:27, Matthias Kaehlcke wrote:
On Fri, Aug 03, 2018 at 12:37:32AM +0530, Balakrishna Godavarthi wrote:
Add support to set voltage/current of various regulators
to power up/down Bluetooth chip wcn3990.
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Matthias Kaehlcke
---
Two defect fixes and one enhancement.
0001: Initialize pretimeout from module parameter.
Bug Fix.
Pretimeout was getting programmed correctly in the hardware,
but this issue caused it to not be displayed correctly
in sysfs.
0002: Claim NMI from iLO
Bug Fix.
Default configuration worked,
When the pretimeout is specified as a module parameter, the
value should be reflected in hpwdt_dev.pretimeout. The default
(on) case is correct. But, when disabling pretimeout, the value
should be set to zero in hpwdt_dev.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 5 +
1
Bump version number to reflect recent bug fixes.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index f098371..27091f3 100644
--- a/drivers/watchdog/hpwdt.c
+++
Print module parameters when the driver is loaded.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index 8a85ddd..f098371 100644
--- a/drivers/watchdog/hpwdt.c
The hwpdt driver is overloaded for handling both the iLO
watchdog and the explicit "Generate NMI to System" virutal
button.
Claim the iLO NMI virtual button even if we are not claiming
the iLO watchdog pretimeout.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 2 +-
1 file
Greg Kurz wrote on Thu, Aug 02, 2018:
> > @@ -443,9 +444,9 @@ static int rdma_request(struct p9_client *client,
> > struct p9_req_t *req)
> > **/
> > if (unlikely(atomic_read(>excess_rc) > 0)) {
> > if ((atomic_sub_return(1, >excess_rc) >= 0)) {
> > - /* Got
Quoting Amit Nischal (2018-07-30 04:28:56)
> On 2018-07-25 12:28, Stephen Boyd wrote:
> >
> > Ok. Sounds good! Is the rate range call really needed? It can't be
> > determined in the PLL code with some table or avoided by making sure
> > GPU
> > uses OPP table with only approved frequencies?
> >
On Wed, Aug 01, 2018 at 05:32:01PM -0700, Roman Gushchin wrote:
> For some workloads an intervention from the OOM killer
> can be painful. Killing a random task can bring
> the workload into an inconsistent state.
For patches 1-3,
Acked-by: Tejun Heo
Thanks.
--
tejun
On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote:
> Udit Agarwal wrote:
>
> > +==
> > +Secure Key
> > +==
> > +
> > +Secure key is the new type added to kernel key ring service.
> > +Secure key is a symmetric type key of minimum length 32 bytes
> > +and with maximum
Add support to set voltage/current of various regulators
to power up/down Bluetooth chip wcn3990.
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Matthias Kaehlcke
---
Changes in v13:
* updated review comments.
Changes in v12:
* removed retrying iteration loop in qca_wcn3990_init.
On Fri, Aug 03, 2018 at 12:37:32AM +0530, Balakrishna Godavarthi wrote:
> Add support to set voltage/current of various regulators
> to power up/down Bluetooth chip wcn3990.
>
> Signed-off-by: Balakrishna Godavarthi
> Reviewed-by: Matthias Kaehlcke
> ---
> Changes in v13:
>* updated review
On Mon, 25 Jun 2018 13:04:48 PDT (-0700), christ...@boehmwalder.at wrote:
On Fri, Jun 22, 2018 at 04:20:05PM -0700, Palmer Dabbelt wrote:
From: Palmer Dabbelt
This patch adds documentation on the RISC-V local interrupt controller,
which is a per-hart interrupt controller that manages all
Hi all,
In preparation to enabling -Wimplicit-fallthrough, this patchset aims
to add some annotations in order to mark switch cases where we are
expecting to fall through.
Thanks
Gustavo A. R. Silva (4):
ALSA: galaxy: Mark expected switch fall-through
ALSA: opti92x: mark expected switch
On Thu 02 Aug 14:21 PDT 2018, Jacek Anaszewski wrote:
> On 08/01/2018 11:01 AM, Baolin Wang wrote:
[..]
> > diff --git a/drivers/leds/trigger/ledtrig-pattern.c
> > b/drivers/leds/trigger/ledtrig-pattern.c
[..]
> > +static ssize_t pattern_trig_store_pattern(struct device *dev,
> > +
Dmitry Vyukov via V9fs-developer wrote on Wed, Jul 18, 2018:
> >> Btw, I see that p9_client_rpc uses wait_event_killable, why wasn't it
> >> killed along with the whole process?
> >>
> >
> > wait_event_killable() would return -ERESTARTSYS if got SIGKILL.
> > But if (c->status == Connected) &&
From: Dave Hansen
The kernel image starts out with the Global bit set across the entire
kernel image. The bit is cleared with set_memory_nonglobal() in the
configurations with PCIDs where we do not need the performance
benefits of the Global bit.
However, this is fragile. It means that we
Em Tue, 24 Jul 2018 11:35:59 +0200
Arnd Bergmann escreveu:
> Without the MFD driver, we run into a link error:
Weird... I'm not seeing this driver at the media tree... was it merged via
some other tree?
>
> drivers/media/platform/cros-ec-cec/cros-ec-cec.o: In function
>
From: Dave Hansen
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2. __init code
3. The hole between text and rodata
4. The hole between rodata and data
We call free_init_pages() to do this. Strangely, we convert the
symbol addresses to
From: Dave Hansen
The kernel image is mapped into two places in the virtual address
space (addresses without KASLR, of course):
1. The kernel direct map (0x8800)
2. The "high kernel map" (0x8100)
We actually execute out of #2. If we get the address of
From: Dave Hansen
When chunks of the kernel image are freed, free_init_pages()
is used directly. Consolidate the three sites that do this.
Also update the string to give an incrementally better
description of that memory versus what was there before.
Signed-off-by: Dave Hansen
Cc: Kees Cook
The fixes for the problem Hugh reported took a bit more surgery
than I would have liked, but they do appear to work. Note that
the last two patches are unnecessary cleanups that could be removed
from backports.
Changes from v1:
* Modify set_memory_np() to avoid messing with the direct map
From: Dave Hansen
This is a cleanup. There should be functional changes in this patch.
The pageattr code has the ability to find and change aliases
mappings. It does this for requests by default unless the
page protections being modified contain only the NX bit.
But, this behavior is
On 8/2/18 4:51 AM, Christoph Hellwig wrote:
Adds a driver for the SiFive implementation of the RISC-V Platform Level
Interrupt Controller (PLIC). The PLIC connects global interrupt sources
to the local interrupt controller on each hart.
This driver is based on the driver in the RISC-V tree
MCP3911 is a dual channel Analog Front End (AFE) containing two
synchronous sampling delta-sigma Analog-to-Digital Converters (ADC).
Signed-off-by: Marcus Folkesson
Signed-off-by: Kent Gustavsson
---
Notes:
v3:
- rename adc_clk to clki
- add error handling/cleanup for clock
On Fri, Aug 03, 2018 at 12:37:26AM +0530, Balakrishna Godavarthi wrote:
> This patch enables regulators for the Qualcomm Bluetooth wcn3990
> controller.
>
> Signed-off-by: Balakrishna Godavarthi
> Reviewed-by: Rob Herring
> Reviewed-by: Stephen Boyd
> ---
> Changes in v13:
> * Segregated
Add an entry for mcp3911 ADC driver and add myself and
Kent Gustavsson as maintainers of this driver.
Signed-off-by: Marcus Folkesson
Signed-off-by: Kent Gustavsson
---
Notes:
v3:
- no changes
v2:
- no changes
MAINTAINERS | 8
1 file changed, 8 insertions(+)
101 - 200 of 1362 matches
Mail list logo
