Commit-ID: 9749b90e566ca1a235fc8e2118f99c5690969342
Gitweb: https://git.kernel.org/tip/9749b90e566ca1a235fc8e2118f99c5690969342
Author: Jiri Olsa
AuthorDate: Sun, 21 Jul 2019 13:23:50 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
perf tools:
Commit-ID: f854839ba2a546a888159667c5ade96793e5cd10
Gitweb: https://git.kernel.org/tip/f854839ba2a546a888159667c5ade96793e5cd10
Author: Jiri Olsa
AuthorDate: Sun, 21 Jul 2019 13:23:49 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
perf cpu_map:
On Mon, Jul 29, 2019 at 11:41:11AM +, Reshetova, Elena wrote:
> I want to summarize here the data (including the performance numbers)
> and reasoning for the in-stack randomization feature. I have organized
> it in a simple set of Q below.
Thanks for these!
> The in-stack randomization is
Commit-ID: df1d6856eaa7ec9ad1e670685b370f3e66326079
Gitweb: https://git.kernel.org/tip/df1d6856eaa7ec9ad1e670685b370f3e66326079
Author: Jiri Olsa
AuthorDate: Sun, 21 Jul 2019 13:23:48 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
perf stat: Move
Commit-ID: e4b00e930bf71ef32189716e6cb6b0565592f078
Gitweb: https://git.kernel.org/tip/e4b00e930bf71ef32189716e6cb6b0565592f078
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 17 Jul 2019 20:32:13 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Commit-ID: ad4153f964ebb756617e1586ba372156db0efeed
Gitweb: https://git.kernel.org/tip/ad4153f964ebb756617e1586ba372156db0efeed
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 17 Jul 2019 18:27:33 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Commit-ID: 30a910d7d3e04dd920e4ca3e8dcabf10c67fb03e
Gitweb: https://git.kernel.org/tip/30a910d7d3e04dd920e4ca3e8dcabf10c67fb03e
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 18 Jul 2019 20:19:30 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
On Tue, Jul 30, 2019 at 03:03:46PM -0300, Jason Gunthorpe wrote:
> On Tue, Jul 30, 2019 at 08:52:03AM +0300, Christoph Hellwig wrote:
> > There isn't really any architecture specific code in this page table
> > walk implementation, so drop the dependencies.
> >
> > Signed-off-by: Christoph
On 30.07.19 19:11, Thomas Huth wrote:
> On 30/07/2019 16.57, Christian Borntraeger wrote:
>>
>>
>> On 30.07.19 12:01, Thomas Huth wrote:
>>> To run the dirty_log_test on s390x, we have to make sure that we
>>> access the dirty log bitmap with little endian byte ordering and
>>> we have to
Commit-ID: b8b1033fcaa091d82289698d7179e84e28cbd92a
Gitweb: https://git.kernel.org/tip/b8b1033fcaa091d82289698d7179e84e28cbd92a
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 17 Jul 2019 20:21:37 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Hi Tudor,
On 25-Jul-19 4:49 PM, tudor.amba...@microchip.com wrote:
> All,
>
> I want this in 5.4, please review/test the soonest.
>
> On 07/20/2019 11:00 AM, Vignesh Raghavendra wrote:
>
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
>> index
Commit-ID: 5d2bd88975117062766a48b5f36ce31d2c1a8269
Gitweb: https://git.kernel.org/tip/5d2bd88975117062766a48b5f36ce31d2c1a8269
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 17 Jul 2019 19:53:51 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Commit-ID: cfa9ac73d6f9790f569959a729cbc9d52bff4270
Gitweb: https://git.kernel.org/tip/cfa9ac73d6f9790f569959a729cbc9d52bff4270
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 17 Jul 2019 11:47:37 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Hi Zhou,
Le mar. 30 juil. 2019 à 10:55, Zhou Yanjie a
écrit :
1.fix bugs when detecting L2 cache sets value.
2.fix bugs when detecting L2 cache ways value.
3.fix bugs when calculate bogoMips and loops_per_jiffy.
Signed-off-by: Zhou Yanjie
---
arch/mips/kernel/cpu-probe.c | 7 ++-
On Tue, Jul 30, 2019 at 08:52:00AM +0300, Christoph Hellwig wrote:
> We only need the special pud_entry walker if PUD-sized hugepages and
> pte mappings are supported, else the common pagewalk code will take
> care of the iteration. Not implementing this callback reduced the
> amount of code
Commit-ID: 247dd65b909f1cd62a178febe3f6f8d5efdd7dd2
Gitweb: https://git.kernel.org/tip/247dd65b909f1cd62a178febe3f6f8d5efdd7dd2
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 17:38:26 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:42 -0300
Hi,
On Tue, Jul 30, 2019 at 10:34 AM Matthias Kaehlcke wrote:
>
> @@ -130,12 +138,13 @@
> regulator-max-microvolt = <180>;
> regulator-name = "vdd18_lcdt";
> regulator-state-mem {
> -
Commit-ID: 3c475bc021be1f5e0a00dc1a13dc85ce7924a7d6
Gitweb: https://git.kernel.org/tip/3c475bc021be1f5e0a00dc1a13dc85ce7924a7d6
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 17:33:39 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: ef969ca64d04161ccbde2aaf8b0767f91a6d32ff
Gitweb: https://git.kernel.org/tip/ef969ca64d04161ccbde2aaf8b0767f91a6d32ff
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 17:21:09 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 79d725cdf24dec7bfe7ad27b107f5cb06cd3785a
Gitweb: https://git.kernel.org/tip/79d725cdf24dec7bfe7ad27b107f5cb06cd3785a
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 16:56:49 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 1d86275225b4c9db3fb426e992886df5051f0047
Gitweb: https://git.kernel.org/tip/1d86275225b4c9db3fb426e992886df5051f0047
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 16:34:27 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
On Mon, Jul 29, 2019 at 02:01:08PM -0700, Nick Desaulniers wrote:
On Mon, Jul 29, 2019 at 1:57 PM Matthias Kaehlcke wrote:
On Mon, Jul 29, 2019 at 01:54:22PM -0700, Matthias Kaehlcke wrote:
> Hi Greg,
>
> Toralf just pointed out in another thread that the commit message and
> the content of
Commit-ID: 212b9ab6775b5f340de848b5b6eef6968ccf7f20
Gitweb: https://git.kernel.org/tip/212b9ab6775b5f340de848b5b6eef6968ccf7f20
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 16:28:14 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 6f563674935e6dc9e2190ce798c1917f51af6eed
Gitweb: https://git.kernel.org/tip/6f563674935e6dc9e2190ce798c1917f51af6eed
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 15:33:20 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Hi!
Dne torek, 04. junij 2019 ob 11:38:44 CEST je Code Kipper napisal(a):
> On Tue, 4 Jun 2019 at 11:02, Christopher Obbard wrote:
> > On Tue, 4 Jun 2019 at 09:43, Code Kipper wrote:
> > > On Tue, 4 Jun 2019 at 09:58, Maxime Ripard
wrote:
> > > > On Mon, Jun 03, 2019 at 07:47:32PM +0200,
Commit-ID: 8b8044e5c9527cdfff3b0937f2d17470cc4acf9e
Gitweb: https://git.kernel.org/tip/8b8044e5c9527cdfff3b0937f2d17470cc4acf9e
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 15:24:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 8d5da2649d8211e63c5f65ccf8945f2c46a9c0b8
Gitweb: https://git.kernel.org/tip/8d5da2649d8211e63c5f65ccf8945f2c46a9c0b8
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 14:55:57 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
The "free memory" comment is obsolete since 2013 and the other ones
explain the obvious. Just remove the comments.
Signed-off-by: Wolfram Sang
---
Change since v1:
* none
drivers/media/i2c/ir-kbd-i2c.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/media/i2c/ir-kbd-i2c.c
Convert this driver to use the new i2c_new_dummy_device() call and bail
out if the dummy device cannot be registered to make failure more
visible to the user.
Signed-off-by: Wolfram Sang
---
Change since v1:
* reworded commit message because there was no NULL ptr access
Commit-ID: bf134ca6c8eafd7ddc28840f767259b97e950bac
Gitweb: https://git.kernel.org/tip/bf134ca6c8eafd7ddc28840f767259b97e950bac
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 12:34:59 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 236dd5838871024d58d354ff8d0dab00ee59a867
Gitweb: https://git.kernel.org/tip/236dd5838871024d58d354ff8d0dab00ee59a867
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 12:31:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Currently, when checking to see if accessing n bytes starting at
address "ptr" will cause a wraparound in the memory addresses,
the check in check_bogus_address() adds an extra byte, which is
incorrect, as the range of addresses that will be accessed is
[ptr, ptr + (n - 1)].
This can lead to
Commit-ID: b119970aa541091e405373399690c24ead9d2920
Gitweb: https://git.kernel.org/tip/b119970aa541091e405373399690c24ead9d2920
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 16 Jul 2019 11:53:03 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Quoting Abel Vesa (2019-07-30 00:22:55)
> Initially, the TMU_ROOT clock was marked as critical, which automatically
> made the AHB clock to stay always on. Since the TMU_ROOT clock is not
> marked as critical anymore, following commit:
>
> 431bdd1df48e ("clk: imx8mq: Remove CLK_IS_CRITICAL flag
Commit-ID: 5834da7f10917245d191032f76f132e62e57197c
Gitweb: https://git.kernel.org/tip/5834da7f10917245d191032f76f132e62e57197c
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 17:51:43 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 83e69b92b10c2a8b75e1919b7074338f8bdbacaf
Gitweb: https://git.kernel.org/tip/83e69b92b10c2a8b75e1919b7074338f8bdbacaf
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 17:28:25 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 5ca0b7f5004a5f1a35c1cb47894790ad98e34ed1
Gitweb: https://git.kernel.org/tip/5ca0b7f5004a5f1a35c1cb47894790ad98e34ed1
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 17:03:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: c8c805707ed4c5d976210821da3242af8610a533
Gitweb: https://git.kernel.org/tip/c8c805707ed4c5d976210821da3242af8610a533
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 16:58:23 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: af4a0991f40a1e50e5caff0317f152df2c82bdeb
Gitweb: https://git.kernel.org/tip/af4a0991f40a1e50e5caff0317f152df2c82bdeb
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 16:22:57 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:41 -0300
Commit-ID: 2620b7e3696a9470c7cda0a08e55813fd5e57e5c
Gitweb: https://git.kernel.org/tip/2620b7e3696a9470c7cda0a08e55813fd5e57e5c
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 15:29:34 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:40 -0300
Commit-ID: 941a7658e065e339ebdaf27b9a7702f9935d1d4a
Gitweb: https://git.kernel.org/tip/941a7658e065e339ebdaf27b9a7702f9935d1d4a
Author: Arnaldo Carvalho de Melo
AuthorDate: Mon, 15 Jul 2019 15:25:41 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 29 Jul 2019 18:34:40 -0300
> On Jul 30, 2019, at 9:11 AM, Oleg Nesterov wrote:
>
> I don't understand this code, so I can't review, but.
>
> On 07/29, Song Liu wrote:
>>
>> This patches introduces a new foll_flag: FOLL_SPLIT_PMD. As the name says
>> FOLL_SPLIT_PMD splits huge pmd for given mm_struct, the underlining
Hi Benoit,
good to see you're still around.
On 30.07.2019 10:39, Benoit HOUYERE wrote:
Hi Alexander, Jarkko and Eyal,
A first I2C TCG patch (tpm_tis_i2c.c) has been proposed in the same time as
tpm_tis_spi.c by Christophe 3 years ago.
https://patchwork.kernel.org/patch/8628681/
Thanks for
The removed barrier isn't needed because the writes/reads are strictly
ordered and even if PMC had separate ports for the writes, it wouldn't
matter since the hardware logic takes into effect after triggering CPU's
power-gating and at that point all CPU accesses are guaranteed to be
completed.
The deadline is this Friday, please get your proposals in as soon as
possible and do not procrastinate. The deadline absolutely cannot be
extended.
This is a call for proposals for the 3 day networking track at the
Linux Plumbers Conference in Lisbon, which will be happening on
September
29.07.2019 16:07, Dmitry Osipenko пишет:
> 25.07.2019 14:15, Dmitry Osipenko пишет:
>> 25.07.2019 12:36, Peter De Schrijver пишет:
>>> On Tue, Jul 23, 2019 at 05:35:10AM +0300, Dmitry Osipenko wrote:
The PCLK clock is running off SCLK, which is a critical clock that is
very unlikely to
1.fix bugs when detecting L2 cache sets value.
2.fix bugs when detecting L2 cache ways value.
3.fix bugs when calculate bogoMips and loops_per_jiffy.
Signed-off-by: Zhou Yanjie
---
arch/mips/kernel/cpu-probe.c | 7 ++-
arch/mips/mm/sc-mips.c | 18 +++---
2 files changed,
The PCLK clock is running off SCLK, which is a critical clock that is
very unlikely to randomly change its rate. It is possible to get a
lockup if kernel decides to enter LP2 cpuidle from a clk-notifier, which
happens occasionally in a case of Tegra30 EMC driver that waits for the
clk-change event
1.fix bugs when detecting L2 cache sets value.
2.fix bugs when detecting L2 cache ways value.
3.fix bugs when calculate bogoMips and loops_per_jiffy.
On Fri, 26 Jul 2019 at 10:08, Suzuki K Poulose wrote:
>
> The ACPI bindings for CoreSight has been updated to add the device
> id for non-programmable CoreSight funnels (aka static funnels) as of
> v1.1 [0]. Add the ACPI id for static funnels in the driver.
>
> [0]
On Tue, Jul 30, 2019 at 2:31 AM OGAWA Hirofumi
wrote:
>
> Deepa Dinamani writes:
>
> > +/* DOS dates from 1980/1/1 through 2107/12/31 */
> > +#define FAT_DATE_MIN (0<<9 | 1<<5 | 1)
> > +#define FAT_DATE_MAX (127<<9 | 12<<5 | 31)
> > +#define FAT_TIME_MAX (23<<11 | 59<<5 | 29)
> > +
> > /*
> >
On Tue, Jul 30, 2019 at 08:51:58AM +0300, Christoph Hellwig wrote:
> The pagewalk code already passes the value as the hmask parameter.
>
> Signed-off-by: Christoph Hellwig
> mm/hmm.c | 7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/mm/hmm.c b/mm/hmm.c
> index
Hi Patrice,
If you cc s...@kernel.org on patches you want us to apply, you'll get
them automatically tracked by patchwork.
-Olof
On Mon, Jul 29, 2019 at 3:55 PM wrote:
>
> From: Patrice Chotard
>
> Enable support for QSPI block on STM32 SoCs.
>
> Signed-off-by: Patrice Chotard
> ---
>
On Tue, Jul 30, 2019 at 06:43:10PM +0200, Frederic Weisbecker wrote:
> On Mon, Jul 29, 2019 at 03:32:38PM -0700, Paul E. McKenney wrote:
> > On Wed, Jul 24, 2019 at 06:12:43PM -0700, Paul E. McKenney wrote:
> >
> > The patch below (which includes your patch) does help considerably.
> > However,
Fix/improve a few things for veyron fievel/tiger:
- move 'vccsys' regulator from tiger to fievel, both boards
have it (and tiger includes the fievel .dtsi)
- move 'ext_gmac' node below regulators
- fix GPIO ids of vcc5_host1 and vcc5_host2 regulators
- remove reset configuration from 'gmac'
In preparation for support of pseudo-locked regions spanning two
cache levels the cache line size computation is moved to a utility.
Setting of the cache line size is moved a few lines earlier, before
the C-states are constrained, to reduce the amount of cleanup needed
on failure.
Signed-off-by:
Hi,
On 7/30/19 1:14 AM, Michal Hocko wrote:
> [Sorry for a late reply]
>
> On Mon 15-07-19 17:55:07, Hoan Tran OS wrote:
>> Hi,
>>
>> On 7/12/19 10:00 PM, Michal Hocko wrote:
> [...]
>>> Hmm, I thought this was selectable. But I am obviously wrong here.
>>> Looking more closely, it seems that
From: David Howells
Date: Tue, 30 Jul 2019 15:56:57 +0100
> rxkad sometimes triggers a warning about oversized stack frames when
> building with clang for a 32-bit architecture:
>
> net/rxrpc/rxkad.c:243:12: error: stack frame size of 1088 bytes in function
> 'rxkad_secure_packet'
A cache pseudo-locked region may span more than one level of cache. A
part of the pseudo-locked region that falls on one cache level is
referred to as a pseudo-lock portion that was introduced previously.
Now a pseudo-locked region is allowed to have two portions instead of
the previous limit of
To prevent eviction of pseudo-locked memory it is required that no
other resource group uses any portion of a cache that is in use by
a cache pseudo-locked region.
Introduce a utility that will return a Capacity BitMask (CBM) indicating
all portions of a provided cache instance being used for
Currently cache pseudo-locked regions only consider one cache level but
cache pseudo-locked regions may span multiple cache levels.
In preparation for support of pseudo-locked regions spanning multiple
cache levels pseudo-lock 'portions' are introduced. A 'portion' of a
pseudo-locked region is
Information about a cache pseudo-locked region is maintained in its
struct pseudo_lock_region. One of these properties is the size of the
region that is computed before it is created and does not change over
the pseudo-locked region's lifetime.
When displaying the size of the pseudo-locked region
The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-fixes-20190730
Pulled, thanks David.
Each cache domain (struct rdt_domain) contains a pointer to a
pseudo-locked region that (if set) is associated with it. At the
same time each resource group (struct rdtgroup) also contains a
pointer to a pseudo-locked region that (if set) is associated with
it.
If a pointer from a cache domain to
CPUs associated with a pseudo-locked cache region are prevented
from entering C6 and deeper C-states to ensure that the
power savings associated with those C-states cannot impact
the pseudo-locked region by forcing the pseudo-locked memory to
be evicted.
When supporting pseudo-locked regions that
Cache pseudo-locking is a model specific feature and platforms
supporting this feature are added by adding the x86 model data to the
source code after cache pseudo-locking has been validated for the
particular platform.
Indicating support for cache pseudo-locking for an entire platform is
Changes since V1:
- Rebase onto v5.3-rc2
Dear Maintainers,
Cache pseudo-locking involves preloading a region of physical memory into a
reserved portion of cache that no task or CPU can subsequently fill into and
from that point on will only serve cache hits. At this time it is only
possible to
The properties of a cache pseudo-locked region that are maintained in
its struct pseudo_lock_region include a pointer to the cache domain to
which it belongs. A cache domain is a structure that is associated with
a cache instance and when all CPUs associated with the cache instance go
offline the
Deterministic cache parameters can be learned from CPUID leaf 04H.
Executing CPUID with a particular index in EAX would return the cache
parameters associated with that index in the EAX, EBX, ECX, and EDX
registers.
At this time, when discovering cache parameters for a particular cache
index,
On Tue, Jul 30, 2019 at 8:21 PM Stephen Boyd wrote:
> Quoting Andy Shevchenko (2019-07-30 10:17:46)
> > On Tue, Jul 30, 2019 at 8:16 PM Andy Shevchenko
> > wrote:
> > > On Tue, Jul 30, 2019 at 6:36 PM Stephen Boyd wrote:
> > > > Ok. Let me resend just this patch broken up into many pieces.
> >
From: Philippe Schenker
This adds the proper phy-supply to the fec. This supply is actually
switched by a clock that is now properly stated. This adds the
advantage to add a delay for that particular regulator that is needed.
Signed-off-by: Philippe Schenker
---
From: Philippe Schenker
This adds the possibility to enable a fixed-regulator with a clock.
Signed-off-by:
Signed-off-by: Philippe Schenker
---
drivers/regulator/core.c | 15 +++
drivers/regulator/fixed.c| 6 ++
include/linux/regulator/driver.h | 3 +++
From: Philippe Schenker
On our Colibri iMX6ULL board there is a circuit for switching the
power supply of the ethernet PHY with the 50MHz RMII clock.
This works quite fine but has one big problem. It is quite slow when
switching the supply, so Linux has to wait there. I think this switch
is at
On Mon, Jul 29 2019 at 14:56 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2019-07-29 12:01:39)
On Thu, Jul 25 2019 at 09:44 -0600, Doug Anderson wrote:
>On Thu, Jul 25, 2019 at 8:18 AM Lina Iyer wrote:
>>
>> On Wed, Jul 24 2019 at 17:28 -0600, Doug Anderson wrote:
>> >
>> >Jumping in without
Because of the overlayfs getxattr recursion, the incoming inode fails
to update the selinux sid resulting in avc denials being reported
against a target context of u:object_r:unlabeled:s0.
Solution is to respond to the XATTR_NOSECURITY flag in get xattr
method that calls the __vfs_getxattr
Assumption never checked, should fail if the mounter creds are not
sufficient.
Signed-off-by: Mark Salyzyn
Cc: Miklos Szeredi
Cc: Jonathan Corbet
Cc: Vivek Goyal
Cc: Eric W. Biederman
Cc: Amir Goldstein
Cc: Randy Dunlap
Cc: Stephen Smalley
Cc: linux-unio...@vger.kernel.org
Cc:
From: YueHaibing
Date: Tue, 30 Jul 2019 22:29:59 +0800
> If PHYLIB is not set, build enetc will fails:
>
> drivers/net/ethernet/freescale/enetc/enetc.o: In function `enetc_open':
> enetc.c: undefined reference to `phy_disconnect'
> enetc.c: undefined reference to `phy_start'
>
> On Jul 30, 2019, at 7:59 AM, Kirill A. Shutemov wrote:
>
> On Sun, Jul 28, 2019 at 10:43:34PM -0700, Song Liu wrote:
>> khugepaged needs exclusive mmap_sem to access page table. When it fails
>> to lock mmap_sem, the page will fault in as pte-mapped THP. As the page
>> is already a THP,
From: Jose Abreu
Date: Tue, 30 Jul 2019 15:57:16 +0200
> With recent changes that introduced support for Page Pool in stmmac, Jon
> reported that NFS boot was no longer working on an ARM64 based platform
> that had the IP behind an IOMMU.
>
> As Page Pool API does not guarantee DMA syncing
On Tue, Jul 30, 2019 at 1:27 AM OGAWA Hirofumi
wrote:
>
> Deepa Dinamani writes:
>
> > diff --git a/fs/fat/misc.c b/fs/fat/misc.c
> > index 1e08bd54c5fb..53bb7c6bf993 100644
> > --- a/fs/fat/misc.c
> > +++ b/fs/fat/misc.c
> > @@ -307,8 +307,9 @@ int fat_truncate_time(struct inode *inode, struct
On 30/07/2019 15:58, Mark Brown wrote:
> On Tue, Jul 30, 2019 at 01:09:36PM +0100, Thomas Preston wrote:
>
>> index ..0f82a88bc1a4
>> --- /dev/null
>> +++ b/sound/soc/codecs/tda7802.c
>> @@ -0,0 +1,509 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/*
>> + * tda7802.c -- codec
Hello,
This small series addresses two suspend-resume bugs: one affects Tegra30+
due to a typo in the code, other fixes CPU hang on Tegra30 specifically.
Changelog:
v2: Reworded comment to the code to make it sound better in the patch
"Use WFE for power-gating on Tegra30".
Dmitry Osipenko
Turned out that WFI doesn't work reliably on Tegra30 as a trigger for
the power-gating, it causes CPU hang under some circumstances like having
memory controller running of PLLP. The TRM doc states that WFI should be
used for the Big-Little "Cluster Switch", while WFE for the power-gating.
Hence
There is an unfortunate typo in the code that results in writing to
FLOW_CTLR_HALT instead of FLOW_CTLR_CSR.
Cc:
Acked-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
---
arch/arm/mach-tegra/reset-handler.S | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On Thu 25-07-19 13:18:19, Qian Cai wrote:
> There are many of those warnings.
>
> In file included from ./arch/powerpc/include/asm/paca.h:15,
> from ./arch/powerpc/include/asm/current.h:13,
> from ./include/linux/thread_info.h:21,
> from
On Wed, Jul 31, 2019 at 1:44 AM Denis Efremov wrote:
>
> On 30.07.2019 19:29, Masahiro Yamada wrote:
> > I prefer this, but why do you need to check type?
> >
> > Doesn't this work?
> >
> > for (sym = info.symtab_start; sym < info.symtab_stop; sym++) {
> > unsigned char bind =
Hello,
On Mon, Jul 29, 2019 at 11:16:45PM +0100, Maciej W. Rozycki wrote:
> On Mon, 29 Jul 2019, Nick Desaulniers wrote:
> > The code in question is modifying a variable declared const through
> > pointer manipulation. Such code is explicitly undefined behavior, and
> > is the lone issue
Quoting Andy Shevchenko (2019-07-30 10:17:46)
> On Tue, Jul 30, 2019 at 8:16 PM Andy Shevchenko
> wrote:
> >
> > On Tue, Jul 30, 2019 at 6:36 PM Stephen Boyd wrote:
> > > Quoting Greg Kroah-Hartman (2019-07-29 23:49:17)
> > > > On Mon, Jul 29, 2019 at 10:38:44PM -0700, Stephen Boyd wrote:
> > >
From: Colin King
Date: Tue, 30 Jul 2019 12:47:52 +0100
> From: Colin Ian King
>
> Currently are duplicated checks on orig_egr_types which are
> redundant, I believe this is a typo and should actually be
> orig_ing_types || orig_egr_types instead of the expression
> orig_egr_types ||
On Tue, Jul 30, 2019 at 8:16 PM Andy Shevchenko
wrote:
>
> On Tue, Jul 30, 2019 at 6:36 PM Stephen Boyd wrote:
> > Quoting Greg Kroah-Hartman (2019-07-29 23:49:17)
> > > On Mon, Jul 29, 2019 at 10:38:44PM -0700, Stephen Boyd wrote:
> > > > We don't need dev_err() messages when platform_get_irq()
On Tue, Jul 30, 2019 at 6:36 PM Stephen Boyd wrote:
> Quoting Greg Kroah-Hartman (2019-07-29 23:49:17)
> > On Mon, Jul 29, 2019 at 10:38:44PM -0700, Stephen Boyd wrote:
> > > We don't need dev_err() messages when platform_get_irq() fails now that
> > > platform_get_irq() prints an error message
> -Original Message-
> From: Keith Busch
> Sent: Tuesday, July 30, 2019 9:42 AM
> To: Rafael J. Wysocki
> Cc: Busch, Keith; Limonciello, Mario; Kai-Heng Feng; Christoph Hellwig; Sagi
> Grimberg; linux-nvme; Linux PM; Linux Kernel Mailing List; Rajat Jain
> Subject: Re: [Regression] Commit
On Tue, 2019-07-30 at 19:11 +0200, Greg KH wrote:
> On Tue, Jul 30, 2019 at 06:49:12PM +0200, Johannes Berg wrote:
> > On Tue, 2019-07-30 at 18:45 +0200, Greg KH wrote:
> >
> > > > I mean, you take patches to devcoredump in general?
> > >
> > > I have no idea, run 'scripts/get_maintainer.pl' to
On Tue, Jul 30, 2019 at 06:20:00PM +0200, Hubert Feurstein wrote:
> > Please don't re-write this logic. It is written like that for a reason.
> I used the sja1105_ptp.c as a reference. So it is also wrong there.
I'll let that driver's author worry about that.
Thanks,
Richard
On Tue, 30 Jul 2019 at 03:37, Suzuki K Poulose wrote:
>
> We warn the users of obsolete bindings in the DT for coresight replicator
> and funnel drivers. However we use pr_warn_once() which doesn't give a clue
> about which device it is bound to. Let us use dev_warn_once() to give the
> context.
On Tue, Jul 30, 2019 at 04:40:32PM +0800, Chuhong Yuan wrote:
> strncpy(dest, src, strlen(src)) leads to unterminated
> dest, which is dangerous.
> Fix it by using strscpy.
>
> Signed-off-by: Chuhong Yuan
> ---
> drivers/gpu/drm/drm_modes.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Tue, Jul 30, 2019 at 06:49:12PM +0200, Johannes Berg wrote:
> On Tue, 2019-07-30 at 18:45 +0200, Greg KH wrote:
>
> > > I mean, you take patches to devcoredump in general?
> >
> > I have no idea, run 'scripts/get_maintainer.pl' to be sure :)
>
> That actually points to me :-)
>
> So really
On 30/07/2019 16.57, Christian Borntraeger wrote:
>
>
> On 30.07.19 12:01, Thomas Huth wrote:
>> To run the dirty_log_test on s390x, we have to make sure that we
>> access the dirty log bitmap with little endian byte ordering and
>> we have to properly align the memslot of the guest.
>> Also all
On Sun, Jul 28, 2019 at 12:58:41AM +0900, Joonwon Kang wrote:
> Before this, there were false negatives in the case where a struct
> contains other structs which contain only function pointers because
> of unreachable code in is_pure_ops_struct().
Ah, very true. Something like:
struct internal {
Hello,
I was spending quite some time recently trying to hunt down CPU-suspend
bug on Tegra30 SoC and in the end it was nailed. During that time I
realized that the CPU Idle drivers could get some polish and gain new
features, thus that's what this series does:
1. Unifies Tegra20/30/114
501 - 600 of 1291 matches
Mail list logo