We want to merge the L2/L2CODE/L2DATA resources to be a single resource,
but we still need to be able to apply separate CODE and DATA schema to
the domain.
Move the new_ctrl bitmap value and flag into a struct, and create an
array of them. Today there is only one element in the array, but
eventual
Now that the cdp_enable() and cdp_disable() calls are basically the same,
merge them into cdp_set_enabled(true/false).
All these functions are behind resctrl_arch_set_cdp_enabled(),
so the can take the rdt_hw_resource directly.
Signed-off-by: James Morse
---
arch/x86/kernel/cpu/intel_rdt_rdtgro
Now that the L2/L2CODE/L2DATA resources are merged together, alloc_enabled
doesn't mean anything, its the same as alloc_capable which indicates
CAT is supported by this cache.
Take the opportunity to kill of alloc_enabled and its helpers.
Signed-off-by: James Morse
---
arch/x86/kernel/cpu/intel
.
Patch was compile tested with: u300_defconfig (implies MACH_U300_SPIDUMMY=y)
Patch is against 4.18 (localversion-next is next-20180824)
arch/arm/mach-u300/dummyspichip.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-u300/dummyspichip.c
b/arch/arm/mach-u300/dummyspi
On 2018-08-17 20:29, Mark Brown wrote:
On Fri, Aug 17, 2018 at 04:06:06PM +0530, dk...@codeaurora.org wrote:
Could you please clarify on below query.
I'm not seeing any further questions in your e-mail?
My bad; i mean, you to comment on below explanation on using
cur_speed_hz instead of clk_
On 08/03/2018 09:08 PM, Andy Shevchenko wrote:
Hi Andy,
(...)
>> +#define APU_FCH_ACPI_MMIO_BASE 0xFED8
>> +#define APU_FCH_GPIO_BASE (APU_FCH_ACPI_MMIO_BASE + 0x1500)
>
> Wow! Can we see ACPI tables for these boards? Care to share (via some
> file share service) output of `acpidump -o
Set it once is enough.
Also move n_voltages close to volt_table for better readability.
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regul
From: Colin Ian King
Trivial fix to spelling mistake in pr_err error message
Signed-off-by: Colin Ian King
---
kernel/locking/test-ww_mutex.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/test-ww_mutex.c b/kernel/locking/test-ww_mutex.c
index 5b915b370d5a..
On Fri, Aug 24, 2018 at 10:47:17AM +0200, Peter Zijlstra wrote:
> On Thu, Aug 23, 2018 at 02:39:59PM +0100, Will Deacon wrote:
> > The only problem with this approach is that we've lost track of the granule
> > size by the point we get to the tlb_flush(), so we can't adjust the stride
> > of
> > t
On Thu, Aug 23, 2018 at 08:59:15PM +, Mike Kravetz wrote:
> Correct a data corruption issue caused by improper handling of shared
> huge PMDs during page migration. This issue was observed in a customer
> environment and can be recreated fairly easily with a test program.
> Patch 0001 addresse
On Fri, 24 Aug 2018 17:20:53 +0900
Masami Hiramatsu wrote:
> On Fri, 24 Aug 2018 13:32:06 +1000
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the origin tree, today's linux-next build (powerpc
> > allyesconfig) produced these warnings:
> >
> > ld: warning: orphan section `.dat
Hello arm-soc maintainers,
Please pull these tee driver enhancements. There's one small fix for the
OP-TEE driver to take DT status into account. There's also a patch
providing a kernel only tee client interface that can be used by other
drivers etc. Currently there's no users of this interface in
Jacek
On 08/24/2018 05:05 AM, Pavel Machek wrote:
> Hi!
>
>> +/**
>> + * struct lm3697 -
>> + * @enable_gpio - Hardware enable gpio
>> + * @regulator - LED supply regulator pointer
>> + * @client - Pointer to the I2C client
>> + * @regmap - Devices register map
>> + * @dev - Pointer to the device
On Fri, Aug 24, 2018 at 10:48:24AM +0100, James Morse wrote:
> Why get avoid the layer stuff? Isn't counting DIMM/memory-devices what
> EDAC_MC_LAYER_SLOT is for?
Yap.
> so edac_raw_mc_handle_error() has no clue where the error happened. (I haven't
> read what it does with this information yet).
I'm announcing the release of the 4.18.5 kernel.
All users of the 4.18 kernel series must upgrade.
The updated 4.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.18.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index ef0dd566c104..a41692c5827a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 18
-SUBLEVEL = 4
+SUBLEVEL = 5
EXTRAVERSION =
NAME = Merciless Moray
diff --git a/arch/parisc/include/asm/spinloc
I'm announcing the release of the 4.17.19 kernel.
Note, this is the LAST 4.17.y kernel to be released, it is now
end-of-life. Pleas move to 4.18.y at this time.
All users of the 4.17 kernel series must upgrade.
The updated 4.17.y git tree can be found at:
git://git.kernel.org/pub/scm/li
I'm announcing the release of the 4.14.67 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
On 08/24/2018 12:36 PM, Vlastimil Babka wrote:
> On 08/24/2018 09:32 AM, Vlastimil Babka wrote:
>> On 08/23/2018 09:27 PM, Michal Hocko wrote:
>>> On Thu 23-08-18 16:28:12, Vlastimil Babka wrote:
Two users have reported [1] that they have an "extremely unlikely" system
with more than MAX_
diff --git a/Makefile b/Makefile
index b11e375bb18e..53d57acfc17e 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 123
+SUBLEVEL = 124
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/arc/Makefile b/arch/arc/Makefile
index 19cce226d1a8..8447eed
I'm announcing the release of the 4.4.152 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.9.124 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 04199cf99dd5..523b0d4354fb 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 151
+SUBLEVEL = 152
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/arc/Makefile b/arch/arc/Makefile
index c05ea2b54276..b9f73
> Subject: Re: [PATCH v2] PCI/AER: Enable SERR# forwarding in non ACPI flow
>
> On 2018-08-09 20:27, Bharat Kumar Gogada wrote:
> > As per Figure 6-3 in PCIe r4.0, sec 6.2.6, ERR_ messages will be
> > forwarded from the secondary interface to the primary interface, if
> > the SERR# Enable bit in t
On Fri, Aug 24, 2018 at 01:32:14PM +0200, Peter Zijlstra wrote:
> On Fri, Aug 24, 2018 at 10:47:17AM +0200, Peter Zijlstra wrote:
> > On Thu, Aug 23, 2018 at 02:39:59PM +0100, Will Deacon wrote:
> > > The only problem with this approach is that we've lost track of the
> > > granule
> > > size by t
> Subject: [PATCH 0/4] Add support to register platform service IRQ
>
> Some platforms have dedicated IRQ lines for PCIe services like AER/PME etc.
> The root complex on these platform will use these seperate IRQ lines to
> report AER/PME etc., interrupts and will not generate MSI/MSI-X/INTx
> int
On Fri 24-08-18 14:10:54, Vlastimil Babka wrote:
> On 08/24/2018 12:36 PM, Vlastimil Babka wrote:
> > On 08/24/2018 09:32 AM, Vlastimil Babka wrote:
> >> On 08/23/2018 09:27 PM, Michal Hocko wrote:
> >>> On Thu 23-08-18 16:28:12, Vlastimil Babka wrote:
> Two users have reported [1] that they h
Hi Tony,
I have a few points regarding the various Rockchip PMIC variants and
it's handling in this driver.
Am 24.08.18 um 05:30 schrieb Tony Xie:
> Add support for the rk809 and rk817 regulator driver.
> Their specifications are as follows：
> 1、The RK809 and RK809 consist of 5 DCDCs,
Lorenzo, Sudeep, Mark
On 15 August 2018 at 12:44, Lorenzo Pieralisi wrote:
> On Fri, Aug 10, 2018 at 02:18:15PM -0600, Lina Iyer wrote:
>
> [...]
>
>> >>But, the OSI feature is critical for QCOM mobile platforms. The
>> >>last man activities during cpuidle save quite a lot of power.
>> >
>> >What
Hallo,
4.4.147 is the last kernel of the 4.4.x series that boots for me. All
subsequent versions panic on boot. How do I report this bug?
If I'm supposed to use https://bugzilla.kernel.org/ I don't know what
to fill into the fields. I don't even know if the longterm kernel falls
under "Mainline"
When notifier converted to state-machine in hotplug, we missed to
remove header file from some of the files.
So, Remove it with this.
Signed-off-by: Mukesh Ojha
---
fs/buffer.c| 1 -
kernel/printk/printk.c | 1 -
lib/percpu_counter.c | 1 -
mm/page-writeback.c| 1 -
mm/page_all
On Fri 24-08-18 14:18:44, Christian König wrote:
> Am 24.08.2018 um 14:03 schrieb Michal Hocko:
> > On Fri 24-08-18 13:57:52, Christian König wrote:
> > > Am 24.08.2018 um 13:52 schrieb Michal Hocko:
> > > > On Fri 24-08-18 13:43:16, Christian König wrote:
> > [...]
> > > > > That won't work like t
Currently, kmemleak only prints the number of suspected leaks to dmesg
but requires the user to read a debugfs file to get the actual stack
traces of the objects' allocation points. Add an option to print the
stack trace information (except the hex dumps) to dmesg too. This
allows easier integrat
Hi Masami,
On Fri, 24 Aug 2018 20:47:56 +0900 Masami Hiramatsu wrote:
>
> gcc-7.3.0 cross build ld shows below warnings.
>
> MODPOST vmlinux.o
> /opt/gcc-7.3.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld: warning: orphan
> section `.gnu.hash' from `linker stubs' being placed in section `.gn
On Fri, Aug 24, 2018 at 10:23 AM Masami Hiramatsu wrote:
>
> On Fri, 24 Aug 2018 13:32:06 +1000
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After merging the origin tree, today's linux-next build (powerpc
> > allyesconfig) produced these warnings:
> >
> > Maybe introduced by commit
> >
> >
On Wed, 22 Aug 2018 22:08:42 +0800
Liang Yang wrote:
> > You have to wait tWB, that's for sure.
> >
> we have a maximum 32 commands fifo. when command is written into
> NFC_REG_CMD, it doesn't mean that command is executing right now, maybe
> it is buffering on the queue.Assume one ERASE ope
Removed a space between function name and open parant.
Signed-off-by: Mehdi Bounya
---
drivers/video/vgastate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/vgastate.c b/drivers/video/vgastate.c
index 548c751..122fb3c 100644
--- a/drivers/video/vgastate.c
+++
'make kselftest-merge' assumes that the config files for the tests are
located under the 'main' test dir, like tools/testing/selftests/android/
and not in a subdir to android.
Signed-off-by: Anders Roxell
---
tools/testing/selftests/android/{ion => }/config | 0
1 file changed, 0 insertions(+),
On Thu, Aug 23, 2018 at 09:23:50AM -0700, Roman Gushchin wrote:
> On Wed, Aug 22, 2018 at 04:12:13PM +0200, Michal Hocko wrote:
> > On Tue 21-08-18 14:35:57, Roman Gushchin wrote:
> > > @@ -248,9 +253,20 @@ static unsigned long *alloc_thread_stack_node(struct
> > > task_struct *tsk, int node)
> >
Hi Masahiro,
On Tue, 21 Aug 2018 17:23:19 +0900
Masahiro Yamada wrote:
> Commit 49aa76b16676 ("mtd: rawnand: do not execute nand_scan_ident()
> if maxchips is zero") gave a new meaning for calling nand_scan_ident()
> with maxchips=0.
>
> It is a special usage for some drivers such as docg4, but
On Mon, 20 Aug 2018 23:39:04 +0200
Janusz Krzysztofik wrote:
> In its current shape, the driver sets data port direction before each
> byte read/write operation, even during multi-byte transfers. Improve
> performance of the driver by setting the port direction only when
> needed.
>
> This opti
On Fri, Aug 24, 2018 at 02:40:11PM +0200, Vincent Whitchurch wrote:
> diff --git a/mm/kmemleak.c b/mm/kmemleak.c
> index 9a085d525bbc..61ba47a357fc 100644
> --- a/mm/kmemleak.c
> +++ b/mm/kmemleak.c
> @@ -311,6 +311,9 @@ static void hex_dump_object(struct seq_file *seq,
> const u8 *ptr = (con
On Fri, Aug 24, 2018 at 02:24:08PM +0200, Matthias B. wrote:
> Hallo,
>
> 4.4.147 is the last kernel of the 4.4.x series that boots for me. All
> subsequent versions panic on boot. How do I report this bug?
> If I'm supposed to use https://bugzilla.kernel.org/ I don't know what
> to fill into the
Sedat,
> This can be dropped with commit 771c035372a036f83353eef46dbb829780330234
> ("deprecate the '__deprecated' attribute warnings entirely and for good")
> now in upstream.
The pull request removing attach_adapter() is on the way now. Thanks for
triggering all this!
Happy hacking,
Wolfra
On Thu, Aug 23, 2018 at 06:47:09PM +1000, Nicholas Piggin wrote:
> The generic tlb_end_vma does not call invalidate_range mmu notifier,
> and it resets resets the mmu_gather range, which means the notifier
> won't be called on part of the range in case of an unmap that spans
> multiple vmas.
>
> A
On Fri, Aug 24, 2018 at 06:07:22AM -0700, Guenter Roeck wrote:
> On Thu, Aug 23, 2018 at 06:47:09PM +1000, Nicholas Piggin wrote:
> > The generic tlb_end_vma does not call invalidate_range mmu notifier,
> > and it resets resets the mmu_gather range, which means the notifier
> > won't be called on p
If kmemleak built in to the kernel, but is disabled by default, the
debugfs file is never registered. Because of this, it is not possible
to find out if the kernel is built with kmemleak support by checking for
the presence of this file. To allow this, always register the file.
After this patch,
On Fri, Aug 24, 2018 at 10:35:56AM +0200, Peter Zijlstra wrote:
> Anyway, its sorted now; although I'd like to write me a fairly big
> comment in asm-generic/tlb.h about things, before I forget again.
How's something like so? There's a little page_size thingy in this;
mostly because I couldn't be
Add PDC Global(Power Domain Controller) binding for SDM845 SoCs.
Signed-off-by: Sibi Sankar
---
.../bindings/reset/qcom,pdc-global.txt| 52 +++
include/dt-bindings/reset/qcom,sdm845-pdc.h | 20 +++
2 files changed, 72 insertions(+)
create mode 100644 Documentation/
This patch series add support for PDC Global (Power Domain Controller)
on SDM845 SoCs and adds pdc reset lines assert/deassert to remoteproc
Q6v5 modem-pil. The first two patches adds PDC Global reset driver to
control reset signals of Modem, Compute, Display, GPU, Debug, AOP,
Sensors, Audio, SP an
Add reset controller for SDM845 SoCs to control reset signals provided
by PDC Global for Modem, Compute, Display, GPU, Debug, AOP, Sensors,
Audio, SP and APPS
Signed-off-by: Sibi Sankar
---
drivers/reset/Kconfig | 9 +++
drivers/reset/Makefile | 1 +
drivers/reset/reset-qcom
Remove the additional definition tag declared for WCSS sub-system
under reset-names.
Signed-off-by: Sibi Sankar
---
Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,q6v
Add additional pdc_reset binding required for Q6V5 Modem PIL on
SDM845 SoCs.
Signed-off-by: Sibi Sankar
---
Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt
b/Documentati
Explicitly get mss_restart to facilitate adding PDC reset line
for modem on SDM845 SoCs
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_q6v5_pil.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/qcom_q6v5_pil.c
b/drivers/remoteproc/qcom_q6v5_pil.c
i
In the presence of a PDC block working with subsystem RSC, assert/deassert
PDC reset in modem start/stop path.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_q6v5_pil.c | 29 -
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/drivers/remoteproc/q
On 08/22/2018 07:40 PM, Christopher Lameter wrote:
> On Mon, 13 Aug 2018, Matthew Wilcox wrote:
>
>> Please consider pulling the XArray patch set. The XArray provides an
>> improved interface to the radix tree data structure, providing locking
>> as part of the API, specifying GFP flags at alloca
On Fri, Aug 24, 2018 at 02:10:27PM +0100, Will Deacon wrote:
> On Fri, Aug 24, 2018 at 06:07:22AM -0700, Guenter Roeck wrote:
> > On Thu, Aug 23, 2018 at 06:47:09PM +1000, Nicholas Piggin wrote:
> > > The generic tlb_end_vma does not call invalidate_range mmu notifier,
> > > and it resets resets th
Adding the label cpu0 allows the adjustment of cpu-parameters
by reference in overlaying dtsi files in the same way as it
is possible for imx6q devices.
Signed-off-by: Jan Tuerk
---
arch/arm/boot/dts/imx6dl.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dt
This patch adds support for the emtrion GmbH emCON-MX6 modules.
They are available with imx.6 Solo, Dual-Lite, Dual and Quad
equipped with Memory from 512MB to 2GB (configured by U-Boot).
Our default developer-Kit ships with the Avari baseboard and the
EDT ETM0700G0BDH6 Display (imx6[q|dl]-emcon-a
All recent emtrion modules based on i.mx6 make use of the DA9063.
Therefore enable it with the following defaults:
- CONFIG_MFD_DA9063=y
- CONFIG_REGULATOR_DA9063=y
- CONFIG_DA9063_WATCHDOG=m
MFD and REGULATOR are built-in to have it at Kernel boot-time.
The WATCHDOG is opti
Document the compatible strings for emtrion emCON-MX6 SoM's.
Signed-off-by: Jan Tuerk
---
Documentation/devicetree/bindings/arm/emtrion.txt | 12
1 file changed, 12 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/emtrion.txt
diff --git a/Documentation/device
Hi: Jerome
Please see my commits.
On 2018/8/14 20:40, Jerome Brunet wrote:
On Fri, 2018-08-10 at 17:54 +0800, Jian Hu wrote:
Add a Clock driver for the ALways-On part
of the Amlogic Meson-G12A SoC.
Signed-off-by: Jian Hu
---
drivers/clk/meson/Makefile | 2 +-
drivers/clk/meson/g12a-
On Fri, Aug 24, 2018 at 06:24:19AM -0700, Guenter Roeck wrote:
> On Fri, Aug 24, 2018 at 02:10:27PM +0100, Will Deacon wrote:
> > On Fri, Aug 24, 2018 at 06:07:22AM -0700, Guenter Roeck wrote:
> > > On Thu, Aug 23, 2018 at 06:47:09PM +1000, Nicholas Piggin wrote:
> > > > The generic tlb_end_vma doe
On Mon, 20 Aug 2018 10:39:43 -0300
Arnaldo Carvalho de Melo wrote:
> Hi guys,
>
> I noticed this while working on a new perf build container for the Clear
> Linux distro, can you take a look at it so that we get the build clean on
> Clear?
These all look like the compiler is being stupid. Do y
Hi Wolfram,
will my patch go to [1]?
Thank you, too.
Regards,
- Sedat -
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/log/?h=i2c/for-next
> Wolfram Sang hat am 24. August 2018 um 15:01 geschrieben:
>
>
> Sedat,
>
> > This can be dropped with commit 771c035372a036f83353
On Fri, Aug 24, 2018 at 02:34:27PM +0100, Will Deacon wrote:
> On Fri, Aug 24, 2018 at 06:24:19AM -0700, Guenter Roeck wrote:
> > On Fri, Aug 24, 2018 at 02:10:27PM +0100, Will Deacon wrote:
> > > On Fri, Aug 24, 2018 at 06:07:22AM -0700, Guenter Roeck wrote:
> > > > On Thu, Aug 23, 2018 at 06:47:0
On Fri, Aug 24, 2018 at 02:50:48PM +0100, Will Deacon wrote:
> >
> > Sorry, I was a bit quick of the mark there. You'll need a forward
> > declaration for the paramater type. Here it is with a commit message,
> > although still untested because I haven't got round to setting up a riscv
> > toolcha
Commit-ID: 6a012288d6906fee1dbc244050ade1dafe4a9c8d
Gitweb: https://git.kernel.org/tip/6a012288d6906fee1dbc244050ade1dafe4a9c8d
Author: Vlastimil Babka
AuthorDate: Thu, 23 Aug 2018 16:21:29 +0200
Committer: Thomas Gleixner
CommitDate: Fri, 24 Aug 2018 15:55:17 +0200
x86/speculation/l1t
Hi Thomas,
This is the last few irqchip updates for this merge window before I
disappear for a couple of weeks without much access to email. Nothing
major this time around, just a few random odd fixes.
Please pull,
M.
The following changes since commit a8db74564b0c634667e1722264bde303d2
On 08/24/2018 06:50 AM, Will Deacon wrote:
-#include
+struct mmu_gather;
static inline void tlb_flush(struct mmu_gather *tlb)
{
flush_tlb_mm(tlb->mm);
Bah, didn't spot the dereference so this won't work either. You basically
just need to copy what I did for arm64 in d475fac957
> will my patch go to [1]?
It won't be needed anymore, the __deprecated function will go away until
next week.
signature.asc
Description: PGP signature
The following is the dmesg output from my working 4.4.147 around the
time when the newer kernel panics.
0.425380] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[0.425932] Bluetooth: HIDP socket layer initialized
[0.426617] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x19
[
On Fri, Aug 24, 2018 at 04:09:47PM +0200, Matthias B. wrote:
> The following is the dmesg output from my working 4.4.147 around the
> time when the newer kernel panics.
>
>
> 0.425380] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
> [0.425932] Bluetooth: HIDP socket layer initialize
On Fri, 24 Aug 2018, Vlastimil Babka wrote:
>
> I think you can just post those for review and say that they apply on
> top of xarray git? Maybe also with your own git URL with those applied
> for easier access? I'm curious but also sceptical that something so
> major would get picked up to mmotm
On Fri, Aug 24, 2018 at 03:43:44PM +0200, Matthias B. wrote:
>
> On Fri, 24 Aug 2018 14:59:50 +0200
> Greg KH wrote:
>
> > It depends on what the panic looks like :)
> >
> > Any hints? You can post it here if you want.
>
> The attached image is everything I see on screen. Scrolling up does no
On Mon, Aug 13, 2018 at 09:37:38AM +0200, Juergen Gross wrote:
> struct pv_mmu_ops {
> + /* TLB operations */
> + void (*flush_tlb_user)(void);
> + void (*flush_tlb_kernel)(void);
> + void (*flush_tlb_one_user)(unsigned long addr);
> + void (*flush_tlb_others)(const struct cpum
On Fri, Aug 24, 2018 at 03:13:32PM +0200, Peter Zijlstra wrote:
> + * HAVE_RCU_TABLE_FREE
> + *
> + * This provides tlb_remove_table(), to be used instead of tlb_remove_page()
> + * for page directores (__p*_free_tlb()). This provides separate freeing of
> + * the page-table pages themselves in
> Wolfram Sang hat am 24. August 2018 um 16:07 geschrieben:
>
>
>
> > will my patch go to [1]?
>
> It won't be needed anymore, the __deprecated function will go away until
> next week.
>
The relict in drivers/i2/Makefile should go away, too.
- sed@ -
[1]
https://git.kernel.org/pub/scm/linu
Hi Ding,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bluetooth/master]
[also build test WARNING on v4.18 next-20180824]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hi Ding,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bluetooth/master]
[also build test ERROR on v4.18 next-20180824]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Fri, 24 Aug 2018 16:11:20 +0200
Greg KH wrote:
> > [0.595677] snd_hda_intel :01:00.1: Too many HDMI devices
> > [0.596251] snd_hda_intel :01:00.1: Consider building the
> > kernel with CONFIG_SND_DYNAMIC_MINORS=y [0.596839] snd_hda_intel
> > :01:00.1: Too many HDMI
On Fri, Aug 24, 2018 at 07:06:51AM -0700, Guenter Roeck wrote:
> On 08/24/2018 06:50 AM, Will Deacon wrote:
>
> >>-#include
> >>+struct mmu_gather;
> >> static inline void tlb_flush(struct mmu_gather *tlb)
> >> {
> >>flush_tlb_mm(tlb->mm);
> >
> >Bah, didn't spot the dereference so this won
On Fri, Aug 24, 2018 at 09:01:02AM +0200, Thomas Gleixner wrote:
> On Fri, 24 Aug 2018, Greg KH wrote:
> > On Thu, Aug 23, 2018 at 05:57:06PM -0500, Grygorii Strashko wrote:
> > > This patch was back ported to the Stable linux-4.14.y and It causes
> > > regression -
> > > flood of "NOHZ: local_so
Hi James,
> Why get avoid the layer stuff? Isn't counting DIMM/memory-devices what
> EDAC_MC_LAYER_SLOT is for?
Borislav has explained it in his response. Here let me elaborate a little more.
To use the layer information you need an accurate way to pinpoint each
component in the layer and the
On Fri, Aug 24, 2018 at 10:01:35AM +0200, Thomas Gleixner wrote:
> On Fri, 24 Aug 2018, Heiner Kallweit wrote:
> > On 24.08.2018 06:12, Frederic Weisbecker wrote:
> > > On Thu, Aug 16, 2018 at 08:13:03AM +0200, Heiner Kallweit wrote:
> > >> Recently I started to get warning "NOHZ: local_softirq_pen
On Fri, 24 Aug 2018 16:12:54 +0200
Greg KH wrote:
>
> All of the stable trees are here:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
> you want the linux-4.4.y branch to work off of.
>
> All of the kernels releases are tagged, so you can start with v4.4.147
> as the
Add RTB trace support to write data to a small uncached buffer.
When a system reset occurs, valuable data may still be remaining
in the cache (e.g. last printks) and this data will probably
be lost, giving an incomplete picture of what the system was last
doing. By logging useful information to thi
Hi,
This patch series adds a new tracing facility for register reads and writes
called
Register Trace Buffer(RTB).
We also add pstore support through which we can save all register read/write
logs into a
persistent ram buffer that can be dumped after reboot.
It can be used to determine from wh
read/write{b,w,l,q} are typically used for reading from memory
mapped registers, which can cause hangs if accessed
unclocked. Tracing these events can help in debugging
various issues faced during initial development.
We log this trace information in persistent ram buffer which
can be viewed after
Introduce dynamic debug filtering mechanism to register
tracing as dynamic_rtb() which will reduce a lot of
overhead otherwise of tracing all the register reads/writes
in all files.
Now we can just specify the file name or any wildcard pattern
as any other dynamic debug facility in bootargs and dy
On Wed, Aug 1, 2018 at 5:29 PM David Howells wrote:
> --- a/include/uapi/linux/fs.h
> +++ b/include/uapi/linux/fs.h
> @@ -351,6 +351,11 @@ typedef int __bitwise __kernel_rwf_t;
>
> #define FSMOUNT_CLOEXEC0x0001
>
> +#define FSPICK_CLOEXEC 0x0001
> +#define FSPICK_
Hi Maxime,
On 08/20/2018 06:32 PM, Maxime Ripard wrote:
> Hi Georgi,
>
> On Tue, Aug 07, 2018 at 05:54:38PM +0300, Georgi Djakov wrote:
>>> There is also a patch series from Maxime Ripard that's addressing the
>>> same general area. See "dt-bindings: Add a dma-parent property". We
>>> don't need
> On Aug 24, 2018, at 7:51 AM, Miklos Szeredi wrote:
>
>> On Wed, Aug 1, 2018 at 5:29 PM David Howells wrote:
>>
>> --- a/include/uapi/linux/fs.h
>> +++ b/include/uapi/linux/fs.h
>> @@ -351,6 +351,11 @@ typedef int __bitwise __kernel_rwf_t;
>>
>> #define FSMOUNT_CLOEXEC0x000
On Thu, Aug 23 2018 at 19:57 -0600, David Dai wrote:
Add RSC(Resource State Coordinator) provider
dictating network-on-chip interconnect bus performance
found on SDM845-based platforms.
Change-Id: I58f0bfc3ed484d7b45064dceb94dcfda507e9333
Remove this pls.
-- Lina
Signed-off-by: David Dai
--
Hi,
On Mon, Aug 20, 2018 at 04:27:15PM +0200, Emmanuel Vadot wrote:
> On Mon, 20 Aug 2018 16:07:37 +0200
> Maxime Ripard wrote:
>
> > On Mon, Aug 20, 2018 at 07:41:22AM -0600, Rob Herring wrote:
> > > On Mon, Aug 20, 2018 at 5:17 AM Maxime Ripard
> > > wrote:
> > > >
> > > > On Sat, Aug 04, 20
On Fri, Aug 24, 2018 at 04:19:53PM +0200, Sedat Dilek wrote:
> > Wolfram Sang hat am 24. August 2018 um 16:07
> > geschrieben:
> >
> >
> >
> > > will my patch go to [1]?
> >
> > It won't be needed anymore, the __deprecated function will go away until
> > next week.
> >
>
> The relict in driv
> Wolfram Sang hat am 24. August 2018 um 17:01 geschrieben:
>
>
> On Fri, Aug 24, 2018 at 04:19:53PM +0200, Sedat Dilek wrote:
> > > Wolfram Sang hat am 24. August 2018 um 16:07
> > > geschrieben:
> > >
> > >
> > >
> > > > will my patch go to [1]?
> > >
> > > It won't be needed anymore, th
Hi Boris,
2018-08-24 21:55 GMT+09:00 Boris Brezillon :
> Hi Masahiro,
>
> On Tue, 21 Aug 2018 17:23:19 +0900
> Masahiro Yamada wrote:
>
>> Commit 49aa76b16676 ("mtd: rawnand: do not execute nand_scan_ident()
>> if maxchips is zero") gave a new meaning for calling nand_scan_ident()
>> with maxchip
The is25lp256 supports 4-byte opcodes and quad output.
In is25lp256, the DWORD1 of JEDEC Basic Flash Parameter Header
is 0xfff920e5. So the DWORD1[18:17] Address Bytes bits are 0b00,
means that 3-Byte only addressing. Now this limits nor->addr_width
to 3 and makes it inpossible to access the addres
On Fri, Aug 24, 2018 at 5:48 AM, James Morse wrote:
> On 23/08/18 16:46, Tyler Baicar wrote:
>> On Thu, Aug 23, 2018 at 5:29 AM James Morse wrote:
>>> On 19/07/18 19:36, Tyler Baicar wrote:
This seems pretty hacky to me, so if anyone has other suggestions please
share
them.
>>>
>>
101 - 200 of 395 matches
Mail list logo
