On Sun, Apr 22, 2018 at 8:19 PM, Paul E. McKenney
wrote:
> On Sun, Apr 22, 2018 at 06:14:18PM -0700, Joel Fernandes wrote:
[...]
>> I narrowed the performance hit down to the call to
>> rcu_irq_enter_irqson() and rcu_irq_exit_irqson() in __DO_TRACE.
>> Commenting these
On Wed, Apr 25, 2018 at 07:49:12PM +0300, Andy Shevchenko wrote:
> > For reference, here's the relevant ASL from the UP2 platform
> > controller.
>
> It should be in Documentation file or in commit message.
Perfect, I just wasn't sure whether dumping ASL this way would be
acceptable in commit
The SC27xx RTC can support dates from 1970-01-01 00:00:00 to 2149-06-06
23:59:59.
Signed-off-by: Baolin Wang
---
drivers/rtc/rtc-sc27xx.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/rtc/rtc-sc27xx.c b/drivers/rtc/rtc-sc27xx.c
index ac86322..6a3876e
This is a preparation patch, changing to use devm_rtc_allocate_device()
that can allow driver to set 'range_max' and 'range_min' for the RTC
device.
Signed-off-by: Baolin Wang
---
drivers/rtc/rtc-sc27xx.c | 14 ++
1 file changed, 10 insertions(+), 4
On Wed, Apr 25, 2018 at 10:30:29PM +0200, David Sterba wrote:
> I had similar toughts some time ago while browsing the fs/ directory.
> Access to the filesystem images can be reimplemented in FUSE, but other
> than that, I don't think the in-kernel code would be missed.
>
> It's hard to know how
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Thursday, April 26, 2018 5:46 AM
> To: Anson Huang
> Cc: Shawn Guo ; Sascha Hauer
> ; Fabio Estevam
On 04/25/2018 01:02 PM, Mikulas Patocka wrote:
> This patch reorders Kconfig entries, so that menuconfig displays proper
> indentation.
>
> Signed-off-by: Mikulas Patocka
Acked-by: Randy Dunlap
Tested-by: Randy Dunlap
w/o RXE_START_MASK, the last_psn of IB_OPCODE_RC_SEND_ONLY_INV
will not be updated in update_wqe_psn, and the corresponding
wqe will not be acked in rxe_completer due to its last_psn is
zero. Finally, the other wqe will also not be able to be acked,
because the wqe of IB_OPCODE_RC_SEND_ONLY_INV
We can use for_each_set_bit() to simplify code slightly in the
ARM io-pgtable self tests while unmapping.
Signed-off-by: YueHaibing
---
drivers/iommu/io-pgtable-arm-v7s.c | 5 +
drivers/iommu/io-pgtable-arm.c | 5 +
2 files changed, 2 insertions(+), 8
Hi Krzysztof,
On 25.04.2018 05:32, Krzysztof Kozlowski wrote:
The Exynos5440 (quad-core A15 with GMAC, PCIe, SATA) was targeting
server platforms but it did not make it to the market really. There
are
no development boards with it and probably there are no real products
neither. The
lspci -vv loaded in bugzilla.
I referred to a pci port nr as the nr in an expansion slot
On 25-04-18 19:05, Bjorn Helgaas wrote:
[Please retain the mailing list cc when replying]
On Wed, Apr 25, 2018 at 3:28 AM Janpieter Sollie
wrote:
Hi Bjorn,
I'm at work now,
On 25.04.2018 23:30, David Sterba wrote:
> On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote:
>> Recently ncpfs got moved to staging. Also recently, we had some fuzzer
>> developers report bugs in hfs, which they deem a security hole because
>> Ubuntu attempts to automount an
> Thanks for the report!
>
> I assume since you're upgrading your own kernel, you must not be
> running Chrome OS on your Acer CB3-431 Chromebook (Edgar). Are you
> running Chromium --- or some Linux distribution on it?
>
> Thanks,
>
> - Ted
Correct, I'm
On Tue, 2018-04-03 at 12:29 +0200, Marcel Holtmann wrote:
> Hi Sean,
>
> > In order to open up the required power gate before any operation can be
> > effectively performed over the serial bus between CPU and serdev, it's
> > clearly essential to add common attach functions for PM domains to
Commit-ID: 9124130573950dcfc06b6a59306edfda2fc33ec7
Gitweb: https://git.kernel.org/tip/9124130573950dcfc06b6a59306edfda2fc33ec7
Author: Fenghua Yu
AuthorDate: Mon, 23 Apr 2018 11:29:22 -0700
Committer: Ingo Molnar
CommitDate: Thu, 26 Apr 2018
Hi Dennis,
On Wed, 2018-04-25 at 22:06 -0500, Dennis Gilmore wrote:
> Hi Srinivas,
>
> Yes I have latest bios, I have version 1.3.1 that was released on
> 18th
> of Feb.
Can you try these commands and repeat the test?
# cd /sys/kernel/debug/pmc_core/
# for i in {0..32}; do echo $i >
Commit-ID: e3072805c61167b85a30ceeef606620704db31f7
Gitweb: https://git.kernel.org/tip/e3072805c61167b85a30ceeef606620704db31f7
Author: Dou Liyang
AuthorDate: Wed, 25 Apr 2018 10:05:53 +0800
Committer: Ingo Molnar
CommitDate: Thu, 26 Apr
Commit-ID: ee05d21791db6db954bbb7b79bb18d88b5f6b7ff
Gitweb: https://git.kernel.org/tip/ee05d21791db6db954bbb7b79bb18d88b5f6b7ff
Author: Namhyung Kim
AuthorDate: Mon, 19 Feb 2018 19:05:45 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 23
Hi!
> Since Linux 4.17-rcX, Linux spams a lot of `random: get_random_u32 called
> from` messages. I believe, this setting should be reverted by default as
> otherwise a lot of other messages are not seen.
>
> Please find my configuration attached.
Same here, thinkpad X60:
[3.163839]
Commit-ID: b31a8cc1a53dda3a33b6c9c62779869d4d5fc142
Gitweb: https://git.kernel.org/tip/b31a8cc1a53dda3a33b6c9c62779869d4d5fc142
Author: Thomas Richter
AuthorDate: Mon, 23 Apr 2018 10:24:28 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb
Gitweb: https://git.kernel.org/tip/ce04abfbd3ea545a8eb38a8b6a48fb6e7d139dcb
Author: Thomas Richter
AuthorDate: Mon, 23 Apr 2018 10:17:45 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate:
Hi Ludovic,
Am 25.04.2018 um 17:08 schrieb Ludovic Desroches:
Hi David,
On Wed, Apr 18, 2018 at 02:40:55PM +0200, David Engraf wrote:
With FIFO enabled it is possible to read multiple bytes
at once in the interrupt handler as long as RXRDY is
set. This may also reduce the number of
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: c690eddc2f3b44b24520f4a77cc3a4c9bde7d571 CRIS: Drop support for the
CRIS port
date: 6 weeks ago
config: cris-allmodconfig
compiler: cris-linux-gcc (GCC)
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc2 next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Wed, Apr 25, 2018 at 3:42 PM Stephen Rothwell
wrote:
> Hi Andy,
> After merging the qcom tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> ERROR: "geni_se_select_mode" [drivers/tty/serial/qcom_geni_serial.ko]
undefined!
> ERROR: "geni_se_init"
On 25/04/18 04:23, valmiki wrote:
Hi all,
When an IRQ line is set affinity using irq_set_affinity, which calls
irq_do_set_affinity, this API copies affinity mask to affinity variable
in irq_common_data of this irq descriptor.
It does a wee bit more. Crucially, it contains the line:
On 4/26/2018 1:39 AM, Peter Zijlstra wrote:
On Wed, Apr 25, 2018 at 02:03:19PM +0530, Gaurav Kohli wrote:
diff --git a/kernel/smpboot.c b/kernel/smpboot.c
index 5043e74..c5c5184 100644
--- a/kernel/smpboot.c
+++ b/kernel/smpboot.c
@@ -122,7 +122,45 @@ static int smpboot_thread_fn(void *data)
On 2018/4/26 11:52, Jianchao Wang wrote:
w/o RXE_START_MASK, the last_psn of IB_OPCODE_RC_SEND_ONLY_INV
will not be updated in update_wqe_psn, and the corresponding
wqe will not be acked in rxe_completer due to its last_psn is
zero. Finally, the other wqe will also not be able to be acked,
Hi Bartosz,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.17-rc2]
[cannot apply to next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Wednesday 25 April 2018 11:10 PM, Santosh Shilimkar wrote:
> On 4/25/2018 6:27 AM, Kishon Vijay Abraham I wrote:
>> Update mmc dt node to use sdhci-omap binding instead of omap_hsmmc
>> binding.
>>
>> I've also updated keystone_defconfig to enable CONFIG_MMC_SDHCI_OMAP.
>> Everyone who use a
We should take "gsm_mux_lock" when we access gsm_mux[].
Reported-by: Sun Peng
Signed-off-by: Dan Carpenter
diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
index 3b3e1f6632d7..cc7f68814200 100644
--- a/drivers/tty/n_gsm.c
+++
On 2018-04-25 18:29, Miquel Raynal wrote:
Hi Abhishek,
On Wed, 25 Apr 2018 12:02:29 +0530, Abhishek Sahu
wrote:
On 2018-04-23 12:28, Miquel Raynal wrote:
> Hi Abhishek,
> > On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu
> wrote:
> >> On
Logically, if gsm->dlci[0] is NULL then it's not open. Also if it's
NULL then we would Oops when we do dlci_get(gsm->dlci[0]); at the end
of the function.
Reported-by: Sun Peng
Signed-off-by: Dan Carpenter
diff --git a/drivers/tty/n_gsm.c
Commit-ID: 129193bb0c43d42f1c397c175346e3e0dba5a578
Gitweb: https://git.kernel.org/tip/129193bb0c43d42f1c397c175346e3e0dba5a578
Author: Jiri Olsa
AuthorDate: Mon, 23 Apr 2018 11:08:17 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 23 Apr
We're freeing the gsm->dlci[] array elements but leaving the freed
pointers hanging around.
My concern here is if we use the ioctl to change the config, it triggers
a restart in gsmld_config(). In that case, we would only reset the
first ->dlci[0] element and not the others so it does look to me
We don't use this spin_lock so we can remove the dead code.
Signed-off-by: Dan Carpenter
diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
index 1f2fd9e76fe0..44e9c5e3dbc1 100644
--- a/drivers/tty/n_gsm.c
+++ b/drivers/tty/n_gsm.c
@@ -177,7 +177,6 @@ struct
Hi, Satendra:
I've applied this patch to my branch mediatek-drm-next-4.18,
and I've added below modification in this patch to prevent build error,
diff --git a/drivers/gpu/drm/mediatek/Kconfig
b/drivers/gpu/drm/mediatek/Kconfig
index 294de45..119ec0a 100644
--- a/drivers/gpu/drm/mediatek/Kconfig
Commit-ID: 121f325f34caf9a7654ec8a50e20942ed9d6dafc
Gitweb: https://git.kernel.org/tip/121f325f34caf9a7654ec8a50e20942ed9d6dafc
Author: Kan Liang
AuthorDate: Tue, 24 Apr 2018 11:20:12 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue,
On Wed, 2018-04-25 at 15:34 -0700, Greg Thelen wrote:
> Allow INFINIBAND without INFINIBAND_ADDR_TRANS because fuzzing has been
> finding fair number of CM bugs. So provide option to disable it.
>
> Signed-off-by: Greg Thelen
> Cc: Tarick Bedeir
> ---
>
When CONFIG_BPF_JIT_ALWAYS_ON is enabled, kernel has limitation for
bpf_jit_enable, so it has fixed value 1 and we cannot set it to 2
for JIT opcode dumping; this patch is to update the doc for it.
Signed-off-by: Leo Yan
---
Documentation/networking/filter.txt | 6 ++
1
On Wed, Apr 25, 2018 at 05:37:39PM +0200, Daniel Borkmann wrote:
> On 04/25/2018 04:14 PM, Alexei Starovoitov wrote:
> > On Wed, Apr 25, 2018 at 05:25:47PM +0800, Leo Yan wrote:
> >>
> >> If we have concern for security issue, should we remove support for
> >> 'bpf_jit_enable = 2' and modify the
Hi Andy,
First off, many thanks for your thorough review! Replies inline.
On Wed, Apr 25, 2018 at 06:57:30PM +0300, Andy Shevchenko wrote:
> > +config MFD_UPBOARD
> > + tristate "UP Squared"
> > + depends on ACPI
> > + depends on GPIOLIB
> > + select MFD_CORE
> > + select REGMAP
> > +
On Wed, Apr 25, 2018 at 05:17:49PM +0800, Yangbo Lu wrote:
> +/* PTP nominal frequency 1GHz */
> +#define DPAA2_PTP_NOMINAL_FREQ_PERIOD_NS 1
Nit: Frequency is the inverse of the period. It can be one or the
other, not both.
Why not call it simply DPAA2_PTP_CLK_PERIOD_NS?
You haven't
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: bb9d812643d8a121df7d614a2b9c60193a92deb0 arch: remove tile port
date: 6 weeks ago
config: tile-tilegx_defconfig
compiler: tilegx-linux-gcc (GCC) 7.2.0
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: c690eddc2f3b44b24520f4a77cc3a4c9bde7d571 CRIS: Drop support for the
CRIS port
date: 6 weeks ago
config: cris-etrax-100lx_v2_defconfig
compiler:
2018-04-26 0:13 GMT+08:00 Eric W. Biederman :
>
> While reviewing f6ed1ecad56f ("signal/nds32: Use force_sig(SIGILL) in
> do_revisn")
> Vincent Chen asked if it was possible to provide more information in
> do_revinsn
> with force_sig_fault.
>
> That seems reasonable and
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc2 next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
I noticed "systems without sufficient boot randomness" and would like to add to
this.
With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec
Chromebook does not reach
the login screen upon boot (it stays stuck on a black screen) until I provide a
source of entropy to
the
Hi Krzysztof,
On 25.04.2018 05:32, Krzysztof Kozlowski wrote:
The Exynos5440 is not actively developed, there are no development
boards available and probably there are no real products with it.
Remove wide-tree support for Exynos5440.
Signed-off-by: Krzysztof Kozlowski
If "re-add" is written to the "state" file for a device
which is faulty, this has an effect similar to removing
and re-adding the device. It should take up the
same slot in the array that it previously had, and
an accelerated (e.g. bitmap-based) rebuild should happen.
The slot that "it
We report the crash:
unable to handle kernel paging request in snd_seq_oss_readq_puts
This crash has been found in v4.16 using RaceFuzzer (a modified
version of Syzkaller), which we describe more at the end of this
report. Our analysis shows that the race occurs when invoking two
syscalls
On Wed, Apr 25, 2018 at 09:11:08PM -0700, Sultan Alsawaf wrote:
> I noticed "systems without sufficient boot randomness" and would like to add
> to this.
>
> With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec
> Chromebook does not reach
> the login screen upon boot (it
Hi Krzysztof,
On 25.04.2018 05:32, Krzysztof Kozlowski wrote:
The Exynos5440 is not actively developed, there are no development
boards available and probably there are no real products with it.
Remove wide-tree support for Exynos5440.
Signed-off-by: Krzysztof Kozlowski
* Shilpa Bhat [2018-04-25 16:29:31]:
> gpstate_timer_handler() uses synchronous smp_call to set the pstate
> on the requested core. This causes the below hard lockup:
>
> [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180
> (unreliable)
>
@Thomas: Do you guys use this ?
On 25-04-18, 20:57, Rob Herring wrote:
> Remove LPC32xx and SPEAr ADC bindings in staging. They have not been
> touched since 2012.
>
> Cc: Roland Stigge
> Cc: Stefan Roese
> Cc: Jonathan Cameron
> Cc: Viresh
Merge tag 'perf-urgent-for-mingo-4.17-20180420' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
> (2018-04-21 09:38:33 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> ta
Greg deleted your patch already...
regards,
dan carpenter
Commit-ID: 5d9946c3e5e38e07ab7019db9413a96807a325f2
Gitweb: https://git.kernel.org/tip/5d9946c3e5e38e07ab7019db9413a96807a325f2
Author: Thomas Richter
AuthorDate: Mon, 23 Apr 2018 16:29:40 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 30060eaed769039c6e523b9d159f2b2858fa8907
Gitweb: https://git.kernel.org/tip/30060eaed769039c6e523b9d159f2b2858fa8907
Author: Kan Liang
AuthorDate: Tue, 24 Apr 2018 11:20:11 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue,
Commit-ID: 292c34c10249c64a70def442f0d977bf9d466ed7
Gitweb: https://git.kernel.org/tip/292c34c10249c64a70def442f0d977bf9d466ed7
Author: Kan Liang
AuthorDate: Tue, 24 Apr 2018 11:20:10 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue,
There are GLINK clients who open the same channel on multiple GLINK
links. These clients need a way to distinguish which remoteproc they
are communicating to. Add a label property to identify the edge this
node represents.
Signed-off-by: Chris Lew
---
Changes since v1:
-
Channels may need to identify the edge their channel was probed for.
Store the edge name by reading the label property from device tree or
default to the node name.
Signed-off-by: Chris Lew
---
Changes since v1:
- None
drivers/rpmsg/qcom_glink_native.c | 6 ++
1 file
Add support for the GLINK rpmsg transport to register a rpmsg chrdev.
This will create the rpmsg_ctrl nodes for userspace clients to open
rpmsg epts. Create a label property that will help userspace clients
distinguish between the different GLINK links. The rpmsg chrdev
allocation is done by
RPMSG provides a char device interface to userspace. Probe the rpmsg
chrdev channel to enable the rpmsg_ctrl device creation on glink
transports.
Signed-off-by: Chris Lew
---
Changes since v1:
- Use qcom_glink_alloc_channel to create the chrdev rpmsg device
In RPMSG GLINK the chrdev device will allocate an ept as part of the
rpdev creation. This device will not register endpoint ops even though
it has an allocated ept. Protect against the case where the device is
being destroyed.
Signed-off-by: Chris Lew
---
Changes since v1:
Expose the name field as an attr so clients listening to uevents for
rpmsg can identify the edge the events correspond to.
Signed-off-by: Chris Lew
---
Changes since v1:
- Add const to attribute struct
- Get name from glink channel
drivers/rpmsg/qcom_glink_native.c | 18
The open_req and open_ack completion variables are the state variables
to represet a remote channel as open. Use complete_all so there are no
races with waiters and using completion_done.
Signed-off-by: Chris Lew
---
Changes since v1:
- New change
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: 553b085c2075f6a4a2591108554f830fa61e881f arch: remove m32r port
date: 7 weeks ago
config:
On Wed, Apr 25, 2018 at 7:13 PM Bart Van Assche
wrote:
> On Wed, 2018-04-25 at 15:34 -0700, Greg Thelen wrote:
> > Allow INFINIBAND without INFINIBAND_ADDR_TRANS because fuzzing has been
> > finding fair number of CM bugs. So provide option to disable it.
> >
> >
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: b8c9c8f0190f4004d3d4364edb2dea5978dfc824 arch: remove score port
date: 7 weeks ago
config:
Hi Srinivas,
Yes I have latest bios, I have version 1.3.1 that was released on 18th
of Feb.
Dennis
El jue, 26-04-2018 a las 02:13 +, Pandruvada, Srinivas escribió:
>
> I see around 43% PC10 residency with power drop of 0.7W.
> Do you have the latest BIOS of Dell 9365?
>
>
> Thanks,
>
Hi Bjorn,
After merging the rpmsg tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem':
drivers/remoteproc/remoteproc_core.c:557:8: error: implicit declaration of
function 'iommu_map_sync'; did you mean
Dear Theodore,
Am 25.04.2018 um 09:41 schrieb Theodore Y. Ts'o:
Does this help on your system?
Thank you, after figuring out how to apply the paste, yes it helped on
my Lenovo X60.
commit 4e00b339e264802851aff8e73cde7d24b57b18ce
Author: Theodore Ts'o
Date: Wed Apr 25
On 25-04-18, 16:29, Shilpasri G Bhat wrote:
> gpstate_timer_handler() uses synchronous smp_call to set the pstate
> on the requested core. This causes the below hard lockup:
>
> [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180
> (unreliable)
> [c03fe566b390]
Hi all,
News: There will be no linux-next release tomorrow.
Changes since 20180424:
The qcom tree gained a build failure so I used the version from
next-20180424.
The clk-samsung tree gained a build failure so I used the version from
next-20180424.
The bpf-next tree gained conflicts against
Hello,
On 26/04/2018 00:57:34 CEST, Dmitry Torokhov wrote:
> On Wed, Apr 25, 2018 at 03:26:50PM -0700, Dmitry Torokhov wrote:
>> On Wed, Apr 25, 2018 at 02:32:58PM +0200, Vittorio Gambaletta (VittGam)
>> wrote:
>> > This patch adds the correct platform data information for the Caroline
>> >
The vectors between FIRST_SYSTEM_VECTOR and NR_VECTORS are special IRQ
vectors used by the SMP architecture. But, if X86_LOCAL_APIC=n, it will
not be used, and the FIRST_SYSTEM_VECTOR is equal to NR_VECTORS.
idt_setup_apic_and_irq_gates() didn't notice that, which make the code
a little complex.
Remove LPC32xx and SPEAr ADC bindings in staging. They have not been
touched since 2012.
Cc: Roland Stigge
Cc: Stefan Roese
Cc: Jonathan Cameron
Cc: Viresh Kumar
Signed-off-by: Rob Herring
---
Move
On Wed, Apr 25, 2018 at 12:33:40PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.37 release.
> There are 183 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Wed, Apr 25, 2018 at 07:15:45PM +0300, Andy Shevchenko wrote:
> On Sat, 2018-04-21 at 09:50 +0100, Javier Arteaga wrote:
> > Allow userspace to use the on-board LEDs as "upboard::".
>
> > + struct upboard_led *led = container_of(cdev, struct
> > upboard_led, cdev);
>
> #define
Hi David,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 26ed24e429d89e045e5eb2d2b75215244347b7f2
commit: 739d875dd6982618020d30f58f8acf10f6076e6d mn10300: Remove the
architecture
date: 7 weeks ago
config:
Hi Arnd,
I love your patch! Yet something to improve:
[auto build test ERROR on v4.17-rc2]
[cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Wed 25 Apr 20:33 PDT 2018, Stephen Rothwell wrote:
> Hi Bjorn,
>
> After merging the rpmsg tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/remoteproc/remoteproc_core.c: In function 'rproc_handle_devmem':
> drivers/remoteproc/remoteproc_core.c:557:8:
Hi Bartosz,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc2]
[cannot apply to next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Evan,
On Thu, 26 Apr 2018 03:39:25 + Evan Green wrote:
>
> Guenter and I had a fix for compile test here, which had failures that
> looked similar:
>
> https://lkml.org/lkml/2018/4/18/752
That looks like it could very well be the problem/solution.
> I was hoping
On 2018-04-23 20:53, Oza Pawandeep wrote:
This patch set brings in error handling support for DPC
The current implementation of AER and error message broadcasting to the
EP driver is tightly coupled and limited to AER service driver.
It is important to factor out broadcasting and other link
On Thu, Apr 26, 2018 at 07:58:52AM +0300, Nikolay Borisov wrote:
>
>
> On 25.04.2018 23:30, David Sterba wrote:
> > On Wed, Apr 25, 2018 at 08:46:02AM -0700, Matthew Wilcox wrote:
> >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer
> >> developers report bugs in hfs,
Hi,
On 4/19/2018 5:48 PM, Andrew Lunn wrote:
On Thu, Apr 19, 2018 at 04:02:32PM +0800, Jisheng Zhang wrote:
From: Jingju Hou
If WOL event happened once, the LED[2] interrupt pin will not be
cleared unless reading the CSISR register. So clear the WOL event
before
pm_runtime handles sdio power on and power off transitions.
An old workaround for trying to control the power explicitly from the
driver was in fact causing failures on suspend/resume as the mmc layer
already power the module on resume.
In case of resume pm_runtime_get sync returns a positive
Commit-ID: 3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165
Gitweb: https://git.kernel.org/tip/3138a2ef62667b6ac8eb5fb33a9e0b84ec3ab165
Author: Sangwon Hong
AuthorDate: Sun, 22 Apr 2018 16:29:06 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 23
Commit-ID: 9a4a931ce847f4aaa12edf11b2e050e18bf45910
Gitweb: https://git.kernel.org/tip/9a4a931ce847f4aaa12edf11b2e050e18bf45910
Author: Jiri Olsa
AuthorDate: Mon, 23 Apr 2018 11:08:18 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 23 Apr
Commit-ID: e9add8bac6c69edb4bf391e537faa659b2ed70d2
Gitweb: https://git.kernel.org/tip/e9add8bac6c69edb4bf391e537faa659b2ed70d2
Author: Jiri Olsa
AuthorDate: Mon, 23 Apr 2018 11:08:19 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 23 Apr
On Wed, Apr 25, 2018 at 09:46:42AM +0900, Tetsuo Handa wrote:
> Theodore Ts\'o wrote:
> > We can do a sleeping allocation from an irq context when CONFIG_NUMA
> > is enabled. Fix this by initializing the NUMA crng instances in a
> > workqueue.
>
> Offloading to workqueue context itself would be
On Tue, Apr 24, 2018 at 07:02:34PM +, Wei Wang wrote:
> We have seen many cases vendor have shipped kernel/drivers with it, and
> have to clean up that every year. This was brought up in an internal
> discussion and Greg suggested have some feedback from upstream about what
> should be taken
On Wed, Apr 25, 2018 at 7:48 AM, Christoph Hellwig wrote:
> On Tue, Apr 24, 2018 at 09:32:20PM +0200, Daniel Vetter wrote:
>> Out of curiosity, how much virtual flushing stuff is there still out
>> there? At least in drm we've pretty much ignore this, and seem to be
>> getting
On 2018-04-23 12:28, Miquel Raynal wrote:
Hi Abhishek,
On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu
wrote:
On 2018-04-22 21:49, Miquel Raynal wrote:
> Hi Abhishek,
> > On Thu, 12 Apr 2018 12:36:42 +0530, Abhishek Sahu
> wrote:
> >> On
On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
> For more fun:
>
> https://www.spinics.net/lists/dri-devel/msg173630.html
>
> Yeah, sometimes we want to disable the iommu because the on-gpu
> pagetables are faster ...
I am not on this list, but remote NAK from here. This needs
Hi Pavel,
On Wed, Apr 25, 2018 at 08:41:33AM +0200, Pavel Machek wrote:
> On Sat 2018-04-21 09:50:08, Javier Arteaga wrote:
> > Allow userspace to use the on-board LEDs as "upboard::".
> >
> > Signed-off-by: Javier Arteaga
>
> > +static enum led_brightness
On Wed, 25 Apr 2018, Dou Liyang wrote:
> Now, Linux uses matrix allocator for vector assignment, the original
> assignment code which used VECTOR_OFFSET_START has been removed.
>
> So remove the stale macro as well
>
> Signed-off-by: Dou Liyang
This was removed in
On Wed, Apr 25, 2018 at 8:43 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 08:23:15AM +0200, Daniel Vetter wrote:
>> For more fun:
>>
>> https://www.spinics.net/lists/dri-devel/msg173630.html
>>
>> Yeah, sometimes we want to disable the iommu because the on-gpu
>>
1 - 100 of 2720 matches
Mail list logo