On Fri, May 10, 2019 at 04:59:38PM +0530, Amit Kucheria wrote:
> Fix up a few entry-method="psci" issues and then add cpuidle low power
> states for msm8996, msm8998, qcs404, sdm845. All these have been tested
> to only make sure that the C-states are entered from Linux point-of-view.
>
> We will c
On Fri, May 10, 2019 at 04:59:42PM +0530, Amit Kucheria wrote:
> Instead of using Qualcomm-specific terminology, use generic node names
> for the idle states that are easier to understand. Move the description
> into the "idle-state-name" property.
>
> Signed-off-by: Amit Kucheria
> ---
> arch/a
On Fri, May 10, 2019 at 04:59:43PM +0530, Amit Kucheria wrote:
> From: Niklas Cassel
>
> Add device bindings for cpuidle states for cpu devices.
>
> [amit: rename the idle-states to more generic names and fixups]
>
> Signed-off-by: Niklas Cassel
> Reviewed-by: Vinod Koul
> Signed-off-by: Amit
On Fri, May 10, 2019 at 04:59:45PM +0530, Amit Kucheria wrote:
> Add device bindings for cpuidle states for cpu devices.
>
> Cc: Marc Gonzalez
> Signed-off-by: Amit Kucheria
> ---
> arch/arm64/boot/dts/qcom/msm8998.dtsi | 32 +++
> 1 file changed, 32 insertions(+)
>
> d
On Fri, May 10, 2019 at 04:59:46PM +0530, Amit Kucheria wrote:
> From: "Raju P.L.S.S.S.N"
>
> Add device bindings for cpuidle states for cpu devices.
>
> [amit: rename the idle-states to more generic names and fixups]
>
> Cc:
> Cc:
> Signed-off-by: Raju P.L.S.S.S.N
> Reviewed-by: Evan Green
On Fri, May 10, 2019 at 04:59:44PM +0530, Amit Kucheria wrote:
> Add device bindings for cpuidle states for cpu devices.
>
> Signed-off-by: Amit Kucheria
> ---
> arch/arm64/boot/dts/qcom/msm8996.dtsi | 28 +++
> 1 file changed, 28 insertions(+)
>
> diff --git a/arch/arm64/
Hi,
On 14/05/2019 17:06, Oleksandr Tyshchenko wrote:
diff --git a/arch/arm/mach-shmobile/setup-rcar-gen2.c
b/arch/arm/mach-shmobile/setup-rcar-gen2.c
index eea60b2..64e3abd 100644
--- a/arch/arm/mach-shmobile/setup-rcar-gen2.c
+++ b/arch/arm/mach-shmobile/setup-rcar-gen2.c
@@ -17,6 +17,7 @@
#
The following changes since commit dc4060a5dc2557e6b5aa813bf5b73677299d62d2:
Linux 5.1-rc5 (2019-04-14 15:17:41 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/
tags/kgdb-5.2-rc1
for you to fetch changes up to ca976bfb3154c7bc6
Hello Wolfram,
On Tue, May 14, 2019 at 05:54:51PM +0200, Wolfram Sang wrote:
>
> > > > Fixes: https://patchwork.kernel.org/patch/10929511/
> > >
> > > I don't think this is an appropriate reference, as it points to a patch
> > > that
> > > was never applied.
> >
> > I included it as a link to
On Tue, May 14, 2019 at 8:58 AM Peter Zijlstra wrote:
>
> So if two variables share a line, and one is local while the other is
> shared atomic, can contention on the line, but not the variable, cause
> issues for the local variable?
>
> If not; why not? Because so far the issue is line granular d
On 5/14/19 5:23 PM, Andy Lutomirski wrote:
On Tue, May 14, 2019 at 2:42 AM Alexandre Chartre
wrote:
On 5/14/19 10:34 AM, Andy Lutomirski wrote:
On May 14, 2019, at 1:25 AM, Alexandre Chartre
wrote:
On 5/14/19 9:09 AM, Peter Zijlstra wrote:
On Mon, May 13, 2019 at 11:18:41AM -0700,
On Mon, May 13, 2019 at 01:12:35PM -0700, Dmitry Torokhov wrote:
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
>
> to receive updates for the input subsystem. You will get a few new
> drivers:
>
> - driver for Azoteq IQS550/572/525 touch con
On 14.05.19 18:09, Sironi, Filippo wrote:
>> Isnt kvm_para_available a function that is defined in the context of the HOST
>> and not of the guest?
>
> No, kvm_para_available is defined in the guest context.
> On x86, it checks for the presence of the KVM CPUID leafs.
>
Right you are, I mixe
Hi,
Q: is there a way to query the crypto layer whether a given algorithm
(digest, crypto) is accelerated by the driver?
This information can be used to decide if eg. a checksum should can be
calculated right away or offloaded to a thread. This is done in btrfs,
(fs/btrfs/disk-io.c:check_async_wr
On 5/14/2019 5:19 PM, Andy Lutomirski wrote:
On Mon, May 13, 2019 at 5:47 AM Roberto Sassu wrote:
On 5/13/2019 11:07 AM, Rob Landley wrote:
On 5/13/19 2:49 AM, Roberto Sassu wrote:
On 5/12/2019 9:43 PM, Arvind Sankar wrote:
On Sun, May 12, 2019 at 05:05:48PM +, Rob Landley wrote:
On
> -Original Message-
> From: linux-hyperv-ow...@vger.kernel.org
> On Behalf Of David Miller
> Sent: Thursday, May 9, 2019 1:58 PM
> To: Sunil Muthuswamy
> Cc: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger
> ; sas...@kernel.org; Dexuan Cui
> ; Michael Kelley ;
> net...@vger.ker
On Mon, 13 May 2019 09:45:55 -0700
Sultan Alsawaf wrote:
> On Fri, May 10, 2019 at 05:10:25PM +0200, Oleg Nesterov wrote:
> > I am starting to think I am ;)
> >
> > If you have task1 != task2 this code
> >
> > task_lock(task1);
> > task_lock(task2);
> >
> > should trigger print_deadloc
On Tue, May 14, 2019 at 06:56:04PM +0800, Wanpeng Li wrote:
> On Tue, 14 May 2019 at 09:45, Wanpeng Li wrote:
> >
> > On Tue, 14 May 2019 at 03:54, Sean Christopherson
> > wrote:
> > > Rather than reinvent the wheel, can we simply move the call to
> > > wait_lapic_expire() into vmx.c and svm.c?
The problem is with the input data size sent to CAAM for encrypt/decrypt.
Pkcs1pad is failing due to pkcs1 padding done in SW starting with0x01
instead of 0x00 0x01.
CAAM expects an input of modulus size. For this we strip the leading
zeros in case the size is more than modulus or pad the input wit
--
Hello
my name is Joan the manager of ssoe marketing and
importing department company. please
provide me the detail of your company website and
also your company product details for us to present to our customer
which we want to have new importing deal to carry out here in united
state.
On Mon, 13 May 2019 23:50:04 +0200
Viktor Rosendahl wrote:
> Hello all,
Hi Viktor,
Note, as the merge window is open and I'm also currently at a
conference, it may be a while before I can take a look at this. If you
don't hear something from me in 10 days, feel free to send me a ping.
-- Steve
On 14.05.19 19:13, Julien Grall wrote:
Hi,
Hi Julien
On 14/05/2019 17:06, Oleksandr Tyshchenko wrote:
diff --git a/arch/arm/mach-shmobile/setup-rcar-gen2.c
b/arch/arm/mach-shmobile/setup-rcar-gen2.c
index eea60b2..64e3abd 100644
--- a/arch/arm/mach-shmobile/setup-rcar-gen2.c
+++ b/arch/
On Tue, May 14, 2019 at 11:00:27PM +0800, Muchun Song wrote:
> There is a race condition between removing glue directory and adding a new
> device under the glue directory. It can be reproduced in following test:
>
> path 1: Add the child device under glue dir
> device_add()
> get_device_paren
On Tue, May 14, 2019 at 09:10:34AM -0700, Linus Torvalds wrote:
> On Tue, May 14, 2019 at 8:58 AM Peter Zijlstra wrote:
> >
> > So if two variables share a line, and one is local while the other is
> > shared atomic, can contention on the line, but not the variable, cause
> > issues for the local
On Tue, May 14, 2019 at 06:33:29PM +0200, Roberto Sassu wrote:
> On 5/14/2019 5:19 PM, Andy Lutomirski wrote:
> > On Mon, May 13, 2019 at 5:47 AM Roberto Sassu
> > wrote:
> > >
> > > On 5/13/2019 11:07 AM, Rob Landley wrote:
> > > >
> > > >
> > > > On 5/13/19 2:49 AM, Roberto Sassu wrote:
> >
> On May 14, 2019, at 1:00 AM, Paul Turner wrote:
>
> From: Nadav Amit
> Date: Fri, May 10, 2019 at 7:45 PM
> To:
> Cc: Borislav Petkov, , Nadav Amit, Andy
> Lutomirsky, Ingo Molnar, Peter Zijlstra, Thomas Gleixner, Jann Horn
>
>> It may be useful to check in runtime whether certain assertions
The pull request you sent on Tue, 14 May 2019 09:51:36 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
> tags/fuse-update-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4856118f4953627e9a087253766b9e7361f5f4a0
Thank you!
--
Deet-doot-do
The pull request you sent on Tue, 14 May 2019 09:55:55 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
> tags/ovl-update-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7e9890a3500d95c01511a4c45b7e7192dfa47ae2
Thank you!
--
Deet-doot-dot,
On Tue, May 14, 2019 at 06:24:48PM +0200, Alexandre Chartre wrote:
> On 5/14/19 5:23 PM, Andy Lutomirski wrote:
> > How important is the ability to enable IRQs while running with the KVM
> > page tables?
> >
>
> I can't say, I would need to check but we probably need IRQs at least for
> some tim
On Thu, May 9, 2019 at 4:55 PM Stephen Boyd wrote:
>
> Some functions in here are never called, and others are only called
> during __init. Remove the dead code and some dead exports for functions
> that don't exist (I'm looking at you of_fdt_get_string!). Mark some
> functions with __init so we c
On Tue, May 14, 2019 at 9:56 AM Peter Zijlstra wrote:
>
> Understood; the problem is that "*p++" is not good enough for local_t
> either (on load-store architectures), since it needs to be "atomic" wrt
> all other instructions on that CPU, most notably exceptions.
Right. But I don't think that's
Now that we've gotten rid of clk_readl() we can remove io.h from the
clk-provider header and push out the io.h include to any code that isn't
already including the io.h header but using things like readl/writel,
etc.
Found with this grep:
git grep -l clk-provider.h | grep '.c$' | xargs git grep
On Tue, May 14, 2019 at 10:09:31AM -0700, Stephen Boyd wrote:
> Now that we've gotten rid of clk_readl() we can remove io.h from the
> clk-provider header and push out the io.h include to any code that isn't
> already including the io.h header but using things like readl/writel,
> etc.
Acked-by: M
Colin,
> Currently an int is being shifted and the result is being cast to a
> u64 which leads to undefined behaviour if the shift is more than 31
> bits. Fix this by casting the integer value 1 to u64 before the shift
> operation.
Applied to 5.2/scsi-fixes, thanks!
--
Martin K. Petersen
IMA signer log (created using ima-sig template) contains
the IMA signature of the file. The IMA signature includes
the key identifier of the key that was used to generate
the IMA signature.
Outside the client machine this key id is not sufficient to
uniquely determine which key the IMA signature
The motive behind this patch series is to measure the public key
of the IMA signature signer in the IMA log.
The IMA signature of the file, logged using ima-sig template, contains
the key identifier of the key that was used to generate the signature.
But outside the client machine this key id is
Added a new interface method namely query_public_key
to asymmetric_key_subtype interface.
Defined public_key_query_public_key method that returns the public key
of the given key. This method is called when the query_public_key
interface method in asymmetric_key_subtype interface is invoked.
This
On May 14, 2019, at 10:00 AM, Nadav Amit wrote:
>> On May 14, 2019, at 1:00 AM, Paul Turner wrote:
>>
>> From: Nadav Amit
>> Date: Fri, May 10, 2019 at 7:45 PM
>> To:
>> Cc: Borislav Petkov, , Nadav Amit, Andy
>> Lutomirsky, Ingo Molnar, Peter Zijlstra, Thomas Gleixner, Jann Horn
>>
>>> I
Fenghua/Andre,
On 5/10/19 2:29 PM, Yu, Fenghua wrote:
> [CAUTION: External Email]
>
>> On Friday, May 10, 2019 10:40 AM
>> Andre Przywara [mailto:andre.przyw...@arm.com] wrote:
>> To: Yu, Fenghua
>> Cc: Thomas Gleixner ; Ingo Molnar
>> ; Borislav Petkov ; H Peter Anvin
>> ; Luck, Tony ; Chatre,
> Subject: Re: [PATCH V5 1/4] spi: tegra114: add support for gpio based CS
> On 14/05/2019 06:03, Sowjanya Komatineni wrote:
> > This patch adds support for GPIO based CS control through SPI core
> > function spi_set_cs.
> >
> > Signed-off-by: Sowjanya Komatineni
> Can you elaborate on the use-
Hi Andre,
(thanks for digging into this!)
On 10/05/2019 18:39, Andre Przywara wrote:
> On Sat, 9 Feb 2019 18:50:39 -0800
> Fenghua Yu wrote:
>> From: Babu Moger
>>
>> RESCTRL feature is supported both on Intel and AMD now. Some features
>> are implemented differently. Add vendor detection mech
Hi Fenghua,
On 10/05/2019 20:20, Yu, Fenghua wrote:
>> On Friday, May 10, 2019 10:36 AM
>> Andre Przywara [mailto:andre.przyw...@arm.com] wrote:
>> On Sat, 9 Feb 2019 18:50:29 -0800
>> Fenghua Yu wrote:
>>> With more and more resctrl features are being added by Intel, AMD and
>>> ARM, a test to
On 5/14/2019 6:58 PM, Greg KH wrote:
On Tue, May 14, 2019 at 06:33:29PM +0200, Roberto Sassu wrote:
On 5/14/2019 5:19 PM, Andy Lutomirski wrote:
On Mon, May 13, 2019 at 5:47 AM Roberto Sassu wrote:
On 5/13/2019 11:07 AM, Rob Landley wrote:
On 5/13/19 2:49 AM, Roberto Sassu wrote:
On 5/12
Future Domain 16xx ISA SCSI support card support.
Tested on IBM 92F0330 card (18C50 chip) with v1.00 BIOS.
Signed-off-by: Ondrej Zary
Reviewed-by: Christoph Hellwig
---
drivers/scsi/Kconfig | 14 +++
drivers/scsi/Makefile | 1 +
drivers/scsi/fdomain_isa.c | 222 ++
Resurrect previously removed fdomain driver, in modern style.
Initialization is rewritten completely, with support for multiple cards,
no more global state variables.
Most of the code from interrupt handler is moved to a workqueue.
This is a modularized version with core separated from bus-specifi
Future Domain TMC-3260/AHA-2920A PCI card support.
Tested on Adaptec AHA-2920A PCI card.
Signed-off-by: Ondrej Zary
Reviewed-by: Christoph Hellwig
---
drivers/scsi/Kconfig | 17
drivers/scsi/Makefile | 1 +
drivers/scsi/fdomain_pci.c | 68 ++
Future Domain TMC-16xx/TMC-3260 SCSI driver.
This is the core driver, common for PCI, ISA and PCMCIA cards.
Signed-off-by: Ondrej Zary
Reviewed-by: Christoph Hellwig
---
drivers/scsi/Kconfig | 4 +
drivers/scsi/Makefile | 1 +
drivers/scsi/fdomain.c | 586 +++
On 5/14/19 7:54 AM, Will Deacon wrote:
On Mon, May 13, 2019 at 04:01:09PM -0700, Yang Shi wrote:
On 5/13/19 9:38 AM, Will Deacon wrote:
On Fri, May 10, 2019 at 07:26:54AM +0800, Yang Shi wrote:
diff --git a/mm/mmu_gather.c b/mm/mmu_gather.c
index 99740e1..469492d 100644
--- a/mm/mmu_gather
On Tue, 2019-05-14 at 10:14 -0700, Lakshmi wrote:
> The motive behind this patch series is to measure the public key
> of the IMA signature signer in the IMA log.
>
> The IMA signature of the file, logged using ima-sig template, contains
> the key identifier of the key that was used to generate th
On 14/05/2019 18:18, Sowjanya Komatineni wrote:
>> Subject: Re: [PATCH V5 1/4] spi: tegra114: add support for gpio based CS
>
>> On 14/05/2019 06:03, Sowjanya Komatineni wrote:
>>> This patch adds support for GPIO based CS control through SPI core
>>> function spi_set_cs.
>>>
>>> Signed-off-by:
On Tue, May 14, 2019 at 12:44:53PM -0400, Steven Rostedt wrote:
> OK, this has gotten my attention.
>
> This thread is quite long, do you have a git repo I can look at, and
> also where is the first task_lock() taken before the
> find_lock_task_mm()?
>
> -- Steve
Hi Steve,
This is the git repo
On 5/14/19 9:03 AM, Steven Sistare wrote:
On 5/13/2019 7:35 AM, Peter Zijlstra wrote:
On Mon, May 13, 2019 at 03:04:18PM +0530, Viresh Kumar wrote:
On 10-05-19, 09:21, Peter Zijlstra wrote:
I don't hate his per se; but the whole select_idle_sibling() thing is
something that needs looking at.
Ondrej,
> Resurrect previously removed fdomain driver, in modern style.
> Initialization is rewritten completely, with support for multiple
> cards, no more global state variables. Most of the code from
> interrupt handler is moved to a workqueue.
>
> This is a modularized version with core sep
When building on a 64-bit host, we will get warnings like those:
drivers/firmware/broadcom/bcm47xx_nvram.c:103:3: note: in expansion of macro
'pr_err'
pr_err("nvram on flash (%i bytes) is bigger than the reserved space in
memory, will just copy the first %i bytes\n",
^~
drivers/firmwar
Allow building building the BCM47xx NVRAM and SPROM drivers using
COMPILE_TEST.
Signed-off-by: Florian Fainelli
---
drivers/firmware/broadcom/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/broadcom/Kconfig
b/drivers/firmware/broadcom/Kconfig
index f
On 5/14/19 10:27 AM, Subhra Mazumdar wrote:
On 5/14/19 9:03 AM, Steven Sistare wrote:
On 5/13/2019 7:35 AM, Peter Zijlstra wrote:
On Mon, May 13, 2019 at 03:04:18PM +0530, Viresh Kumar wrote:
On 10-05-19, 09:21, Peter Zijlstra wrote:
I don't hate his per se; but the whole select_idle_sibli
Hi Thank you both for the explanation.
On Tue, 14 May 2019 11:41:24 +0100
Jean-Philippe Brucker wrote:
> On 14/05/2019 08:36, Auger Eric wrote:
> > Hi Jacob,
> >
> > On 5/14/19 12:16 AM, Jacob Pan wrote:
> >> On Mon, 13 May 2019 18:09:48 +0100
> >> Jean-Philippe Brucker wrote:
> >>
> >>> O
On 5/14/2019 5:57 PM, Arvind Sankar wrote:
On Tue, May 14, 2019 at 11:27:04AM -0400, Arvind Sankar wrote:
It's also much easier to change/customize it for the end
system's requirements rather than setting the process in stone by
putting it inside the kernel.
As an example, if you allow unverif
If fgets fails due to any other error besides end-of-file, the version char
array may not even be null-terminated.
Signed-off-by: Donald Yandt
Fixes: a1645ce12adb ("perf: 'perf kvm' tool for monitoring guest performance
from host")
---
tools/perf/util/machine.c | 3 ++-
1 file changed, 2 inser
On Tue, May 14, 2019 at 06:01:59PM +0200, Oleg Nesterov wrote:
> Roman,
>
> Sorry, I can't agree with this patch. And even the changelog doesn't
> look right.
>
> On 05/13, Roman Gushchin wrote:
> >
> > The ptrace_stop() function contains the cgroup_enter_frozen() call,
> > but no cgroup_leave_fr
But this link is mentioned in dmesg of 5.1.2
--
Toralf
PGP C4EACDDE 0076E94E
The pull request you sent on Tue, 14 May 2019 11:41:33 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> tags/backlight-next-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e0654264c4806dc436b291294a0fbf9be7571ab6
Thank you!
--
Deet-doot
The pull request you sent on Tue, 14 May 2019 11:38:36 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-next-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ebcf5bb28241fe3ddc9e786e3816848a10f688b8
Thank you!
--
Deet-doot-dot, I am a bo
The pull request you sent on Mon, 13 May 2019 18:57:21 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
> tags/pci-v5.2-changes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/414147d99b928c574ed76e9374a5d2cb77866a29
Thank you!
--
Deet-doot-dot
Hi Neil,
On Mon, May 13, 2019 at 11:16 AM Neil Armstrong wrote:
>
> On the Amlogic G12A SoC family, (only) the SDIO controller has a bug which
> makes any DDR access from the MMC controller fail.
>
> Add the amlogic,ddr-access-quirk property so signal this particular
> controller has this bug and
On Mon, May 13, 2019 at 11:17 AM Neil Armstrong wrote:
>
> The Amlogic G12A SDIO Controller has a bug preventing direct DDR access,
> mark this specific controller with the amlogic,ddr-access-quirk property.
>
> Signed-off-by: Neil Armstrong
Acked-by: Martin Blumenstingl
Hi Neil,
On Mon, May 13, 2019 at 11:16 AM Neil Armstrong wrote:
[...]
> @@ -1158,15 +1183,27 @@ static int meson_mmc_probe(struct platform_device
> *pdev)
> */
> mmc->caps2 &= ~MMC_CAP2_HS400;
>
> - /* data bounce buffer */
> - host->bounce_buf_size = mmc->max_req_si
On Sun, May 12, 2019 at 10:57 PM Jerome Brunet wrote:
>
> MPLL_5OM (the capital letter o) should indeed be MPLL_50M (the number)
> Fix this before it gets used.
>
> Reported-by: Martin Blumenstingl
> Fixes: 25db146aa726 ("dt-bindings: clk: meson: add g12a periph clock
> controller bindings")
> S
I'm announcing the release of the 5.1.2 kernel.
All users of the 5.1 kernel series must upgrade. Well, kind of, let me
rephrase that...
All users of Intel processors made since 2011 must upgrade.
Note, this release, and the other stable releases that are all being
released right now at the sam
I'm announcing the release of the 5.0.16 kernel.
All users of the 5.0 kernel series must upgrade.
The updated 5.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.0.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 9605dbd4b5b5..141a7bb58b80 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -484,6 +484,7 @@ What:
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 9605dbd4b5b5..141a7bb58b80 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -484,6 +484,7 @@ What:
I'm announcing the release of the 4.19.43 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 73318225a368..8718d4ad227b 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -477,6 +477,7 @@ What:
On 13.05.2019 22:43, Arnaldo Carvalho de Melo wrote:
> Em Mon, Apr 22, 2019 at 05:37:52PM +0300, Alexey Budankov escreveu:
>>
>> When dwarf stacks are collected jointly with user specified register
>> set using --user-regs option like below the full register context is
>> still captured on a sample
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu
b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 6cae60929cb6..645687b1870d 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -380,6 +380,7 @@ What:
I'm announcing the release of the 4.9.176 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:
On Mon, May 13, 2019 at 3:05 PM Jerome Brunet wrote:
>
> Add UHS ddr50 mode to the nanopi k2
>
> Signed-off-by: Jerome Brunet
Acked-by: Martin Blumenstingl
since I'm curious: is this due to your recent meson-gx-mmc patches?
this is the first board where we enable the UHS DDR50 mode
Martin
I'm announcing the release of the 4.14.119 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 Tue, May 14, 2019 at 5:32 AM Peter Zijlstra wrote:
>
> On Mon, May 13, 2019 at 05:27:47PM -0700, Cong Wang wrote:
> > We have been consistently triggering the warning
> > WARN_ON_ONCE(cpuctx->cgrp) in perf_cgroup_switch() for a rather
> > long time, although we still have no clue on how to repr
On Tue, May 14, 2019 at 08:04:24PM +0200, Greg KH wrote:
> I'm announcing the release of the 5.1.2 kernel.
>
> All users of the 5.1 kernel series must upgrade. Well, kind of, let me
> rephrase that...
>
> All users of Intel processors made since 2011 must upgrade.
>
> Note, this release, and t
On Tue, May 14, 2019 at 07:05:22PM +0200, Peter Zijlstra wrote:
> On Tue, May 14, 2019 at 06:24:48PM +0200, Alexandre Chartre wrote:
> > On 5/14/19 5:23 PM, Andy Lutomirski wrote:
>
> > > How important is the ability to enable IRQs while running with the KVM
> > > page tables?
> > >
> >
> > I ca
On Mon, May 13, 2019 at 04:50:05PM -0700, Nick Desaulniers wrote:
> On Mon, May 13, 2019 at 4:29 PM Nathan Chancellor
> wrote:
> >
> > On Mon, May 13, 2019 at 03:21:09PM -0700, 'Nick Desaulniers' via Clang
> > Built Linux wrote:
> > > With CONFIG_LKDTM=y and make OBJCOPY=llvm-objcopy, llvm-objcop
On Mon, May 13, 2019 at 2:45 PM Jerome Brunet wrote:
>
> While some SoC samples are able to lock with a PLL factor of 55, others
> samples can't. ATM, a minimum of 60 appears to work on all the samples
> I have tried.
>
> Even with 60, it sometimes takes a long time for the PLL to eventually
> loc
On Tue, 14 May 2019 19:48:12 +0200
Toralf Förster wrote:
> But this link is mentioned in dmesg of 5.1.2
It works for me. I think you just needed to wait for the relevant commit
to make it upstream and the docs to be regenerated.
Thanks,
jon
On Mon, May 13, 2019 at 2:31 PM Jerome Brunet wrote:
>
> The bit 'SSEN' available on some MPLL DSS outputs is not related to the
> fractional part of the divider but to the function called
> 'Spread Spectrum'.
>
> This function might be used to solve EM issues by adding a jitter on
> clock signal.
Em Tue, May 14, 2019 at 07:39:12AM -0700, kan.li...@linux.intel.com escreveu:
> From: Kan Liang
>
> Some non general purpose registers, e.g. XMM, can be collected on some
> platforms, e.g. X86 Icelake.
>
> Add a weak function has_non_gprs_support() to check if the
> kernel/hardware support non-g
On Tue, 14 May 2019 10:26:57 +0200, Fabien Dessenne wrote:
> Add the device tree bindings document for the stm32 remoteproc devices.
>
> Signed-off-by: Fabien Dessenne
> ---
> .../devicetree/bindings/remoteproc/stm32-rproc.txt | 63
> ++
> 1 file changed, 63 insertions(+)
>
On Tue, May 14, 2019 at 11:20:15AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, May 14, 2019 at 10:50:23AM -0300, Marcelo Tosatti wrote:
> > On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
> > > On Wed, 8 May 2019 at 02:57, Marcelo Tosatti wrote:
> > > >
> > > >
> > > > Certain worklo
On Tue, 14 May 2019 10:26:56 +0200, Fabien Dessenne wrote:
> Document the ML-AHB interconnect for stm32 SoCs.
>
> Signed-off-by: Fabien Dessenne
> ---
> .../devicetree/bindings/arm/stm32/mlahb.txt| 37
> ++
> 1 file changed, 37 insertions(+)
> create mode 100644 Doc
On Tue, May 14, 2019 at 11:16 AM Jerome Brunet wrote:
>
> Enable eMMC and SDCard on the g12a sei510 board
>
> Signed-off-by: Jerome Brunet
I compared the GPIOs with the Odroid-N2 schematics because I'm
assuming that they will be the same on all G12A/G12B boards:
Reviewed-by: Martin Blumenstingl
On Tue, May 14, 2019 at 11:16 AM Jerome Brunet wrote:
>
> Enable eMMC and SDCard on the g12a u200 board
>
> Signed-off-by: Jerome Brunet
I compared the GPIOs with the Odroid-N2 schematics because I'm
assuming that they will be the same on all G12A/G12B boards:
Reviewed-by: Martin Blumenstingl
On Tue, May 14, 2019 at 11:16 AM Jerome Brunet wrote:
>
> Add port B (sdcard) and port C (eMMC) pinctrl and controllers nodes to
> the g12a DT.
I assume port A is missing due to the controller bug (missing DDR
access) for which Neil has sent a fix. this shouldn't stop us from
adding SD card and eM
On Tue, May 14, 2019 at 11:45 AM Jerome Brunet wrote:
>
> Now that the AO clock controller is available, make the uarts of the
> always-on domain claim the appropriate peripheral clock.
>
> Signed-off-by: Jerome Brunet
Reviewed-by: Martin Blumenstingl
13.05.2019 20:40, Mark Brown пишет:
> On Sun, May 12, 2019 at 09:29:54PM +0300, Dmitry Osipenko wrote:
>> 12.05.2019 12:04, Mark Brown пишет:
>>> On Wed, May 08, 2019 at 04:27:42PM +0300, Dmitry Osipenko wrote:
>
>>> Those seem like they should be doable in generic code, though the fact
>>> that t
On 14.05.19 20:14, Jonathan Corbet wrote:
> On Tue, 14 May 2019 19:48:12 +0200
> Toralf Förster wrote:
>
>> But this link is mentioned in dmesg of 5.1.2
>
> It works for me. I think you just needed to wait for the relevant commit
> to make it upstream and the docs to be regenerated.
>
> Thanks,
>
[ Purple is a nice shade on the bike shed. ;-) ]
On Tue, 14 May 2019 11:02:17 +0200
Geert Uytterhoeven wrote:
> On Tue, May 14, 2019 at 10:29 AM David Laight wrote:
> > > And I like Steven's "(fault)" idea.
> > > How about this:
> > >
> > > if ptr < PAGE_SIZE -> "(null)"
>
On Mon, May 13, 2019 at 08:30:59AM +0100, Lee Jones wrote:
> On Fri, 10 May 2019, Nathan Chancellor wrote:
>
> > Clang warns:
> >
> > In file included from drivers/mfd/stmfx.c:13:
> > include/linux/mfd/stmfx.h:7:9: warning: 'MFD_STMFX_H' is used as a
> > header guard here, followed by #define of
In commit 37a186225a0c ("platform/chrome: cros_ec_spi: Transfer
messages at high priority") we moved transfers to a high priority
workqueue. This helped make them much more reliable.
...but, we still saw failures.
We were actually finding ourselves competing for time with dm-crypt
which also sch
All currently known ECs in the wild are very sensitive to timing.
Specifically the ECs are known to drop a transfer if more than 8 ms
passes from the assertion of the chip select until the transfer
finishes.
Let's use the new feature introduced in the patch (spi: Allow SPI
devices to request the p
301 - 400 of 661 matches
Mail list logo
