On Wed, Oct 14, 2020 at 03:54:11PM +0100, Richard Fitzgerald wrote:
> This set of patches provides support for using the Cirrus Logic
> Lochnagar audio development platform plus Cirrus Logic Madera/Arizona
> codecs with the simple-card machine driver and a Raspberry Pi4. The
> ultimate aim is to pr
Le mer. 14 oct. 2020 à 13:14, Serge Semin
a écrit :
In accordance with the Generic EHCI/OHCI bindings the corresponding
node
name is suppose to comply with the Generic USB HCD DT schema, which
requires the USB nodes to have the name acceptable by the regexp:
"^usb(@.*)?" . Let's fix the DTS
On Tue, Oct 13, 2020 at 06:58:40PM -0700, Paul E. McKenney wrote:
> On Tue, Oct 13, 2020 at 12:38:36PM -0400, Alan Stern wrote:
> > On Tue, Oct 13, 2020 at 09:33:54AM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 13, 2020 at 02:14:29PM +0200, Mauro Carvalho Chehab wrote:
> > > > - The sysfs.txt
Fixes:
Don't run keep alive work with zero kato.
"Fixes" tags need to have a git commit id followed by the commit
subject. I can't find any commit with that subject, though.
Fixes: 0d3b6a8d213a ("nvmet: Disable keep-alive timer when kato is
cleared to 0h")
Anant,
On Wed, Oct 14, 2020 at 6:31 PM Anant Thazhemadam
wrote:
> In gfs2_check_sb(), no validation checks are performed with regards to
> the size of the superblock.
> syzkaller detected a slab-out-of-bounds bug that was primarily caused
> because the block size for a superblock was set to zero.
On Wed, Oct 14, 2020 at 02:16:24PM +, Tomasz Figa wrote:
> Fixes a boot crash on a HP Chromebook x2:
>
> [ 16.582225] BUG: kernel NULL pointer dereference, address: 0050
> [ 16.582231] #PF: supervisor read access in kernel mode
> [ 16.582233] #PF: error_code(0x) - not-pr
On Tue, Oct 13, 2020 at 8:54 PM Kalesh Singh wrote:
>
Hi kselftest maintainers,
Could someone ACK this mremap test if there isn't any other concern?
Thanks,
Kalesh
> Test mremap on regions of various sizes and alignments and validate
> data after remapping. Also provide total time for remappin
On 10/14/20 8:05 AM, Cristian Marussi wrote:
> Extend common protocol registration routines and provide some new generic
> protocols' init/deinit helpers that tracks protocols' users and automatically
> perform the proper initialization/de-initialization on demand.
>
> Convert all protocols to use
On Wed, Oct 14, 2020 at 12:43:08PM -0500, David Lechner wrote:
> On 9/26/20 9:18 PM, William Breathitt Gray wrote:
> > diff --git a/drivers/counter/counter-chrdev.c
> > b/drivers/counter/counter-chrdev.c
> > new file mode 100644
> > index ..2be3846e4105
> > --- /dev/null
> > +++ b/driv
On Wed, Oct 14, 2020 at 11:47 PM Trond Myklebust
wrote:
>
> On Tue, 2020-10-06 at 08:14 -0700, Ashish Sangwan wrote:
> > Request for mode bits and nlink count in the nfs4_get_referral call
> > and if server returns them use them instead of hard coded values.
> >
> > CC: sta...@vger.kernel.org
> >
SLAB objects which outlive their memcg are moved to their parent
memcg where they may be uncharged. However if they are moved to the
root memcg, uncharging will result in negative page counter values as
root has no page counters.
To prevent this, we check whether we are about to uncharge the root
On Tue, 13 Oct 2020 23:13:17 +
Nícolas F. R. A. Prado wrote:
> The warnings were caused by the expressions matching words in the
> translated versions of the documentation, since any unicode character
> was matched.
>
> Fix the regular expression by making the C regexes use ASCII
I don't qu
Introduce a test for of_dma_get_max_cup_address(), it uses the same DT
data as the rest of dma-ranges unit tests.
Signed-off-by: Nicolas Saenz Julienne
---
drivers/of/unittest.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/of/unittest.c b/drivers/of/unittest.
The default behavior for arm64 changed, so reflect that.
Signed-off-by: Nicolas Saenz Julienne
Acked-by: Catalin Marinas
---
include/linux/mmzone.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index fb3bf696c05e..4ee230
Set zone_dma_bits default value through a define so as for architectures
to be able to override it with their default value.
Signed-off-by: Nicolas Saenz Julienne
---
include/linux/dma-direct.h | 3 +++
kernel/dma/direct.c| 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --gi
Hi Sergey,
> arch/arc/boot/dts/axs10x_mb.dtsi | 4 ++--
> arch/arc/boot/dts/hsdk.dts | 4 ++--
> arch/arc/boot/dts/vdk_axs10x_mb.dtsi | 2 +-
For ARC boards
Acked-by: Alexey Brodkin
From: Ard Biesheuvel
We recently introduced a 1 GB sized ZONE_DMA to cater for platforms
incorporating masters that can address less than 32 bits of DMA, in
particular the Raspberry Pi 4, which has 4 or 8 GB of DRAM, but has
peripherals that can only address up to 1 GB (and its PCIe host
bridge c
crashkernel might reserve memory located in ZONE_DMA. We plan to delay
ZONE_DMA's initialization after unflattening the devicetree and ACPI's
boot table initialization, so move it later in the boot process.
Specifically into mem_init(), this is the last place crashkernel will be
able to reserve the
Using two distinct DMA zones turned out to be problematic. Here's an
attempt go back to a saner default.
I tested this on both a RPi4 and QEMU.
---
Changes since v2:
- Introduce Ard's patch
- Improve OF dma-ranges parsing function
- Add unit test for OF function
- Address small changes
- Mo
On Thu, 8 Oct 2020 at 12:45, Mark Rutland wrote:
> On Thu, Oct 08, 2020 at 11:40:52AM +0200, Marco Elver wrote:
> > On Thu, 1 Oct 2020 at 19:58, Mark Rutland wrote:
> > [...]
> > > > > If you need virt_to_page() to work, the address has to be part of the
> > > > > linear/direct map.
> > [...]
> >
zone_dma_bits's initialization happens earlier that it's actually
needed, in arm64_memblock_init(). So move it into the more suitable
zone_sizes_init().
Signed-off-by: Nicolas Saenz Julienne
---
arch/arm64/mm/init.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/
We recently introduced a 1 GB sized ZONE_DMA to cater for platforms
incorporating masters that can address less than 32 bits of DMA, in
particular the Raspberry Pi 4, which has 4 or 8 GB of DRAM, but has
peripherals that can only address up to 1 GB (and its PCIe host
bridge can only access the bott
Introduce of_dma_get_max_cpu_address(), which provides the highest CPU
physical address addressable by all DMA masters in the system. It's
specially useful for setting memory zones sizes at early boot time.
Signed-off-by: Nicolas Saenz Julienne
---
Changes since v2:
- Use PHYS_ADDR_MAX
- retu
On 14/10/2020 20:52, Mickaël Salaün wrote:
>
> On 14/10/2020 20:07, James Morris wrote:
>> On Thu, 8 Oct 2020, Mickaël Salaün wrote:
>>
>>> +config ARCH_EPHEMERAL_STATES
>>> + def_bool n
>>> + help
>>> + An arch should select this symbol if it does not keep an internal
>>> kernel
>>> +
On 2020-10-14 8:28 a.m., Ingo Molnar wrote:
* Ankur Arora wrote:
Uncached writes are suitable for circumstances where the region written to
is not expected to be read again soon, or the region written to is large
enough that there's no expectation that we will find the writes in the
cache.
A
On Tue, Oct 13, 2020 at 9:04 AM Joerg Roedel wrote:
>
> there is a minor conflict this time in include/linux/iommu.h which
> should be easy to resolve. I would attach my resolution, but somehow git
> [show|log] didn't show it to me.
So when a resolution takes one side over the other (as opposed t
The pull request you sent on Tue, 13 Oct 2020 18:03:58 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
> tags/iommu-updates-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/531d29b0b674036347a04c08c0898ff1aa522180
Thank you!
--
Deet-doot-d
On 10/14/20 8:05 AM, Cristian Marussi wrote:
> Protocols private data were meant to be used exclusively by protocol code
> but they are currently exposed through the handle, so available also to
> SCMI drivers: move them away from handle into instance specific data and
> provide internal helpers to
On Wed, 14 Oct 2020 11:56:44 +0200
Mauro Carvalho Chehab wrote:
> > To make the first step possible, disable the parallel_read_safe option
> > in Sphinx, since the dictionary that maps the files to the C namespaces
> > can't be concurrently updated. This unfortunately increases the build
> > time
On 2020-10-14 8:31 a.m., Ingo Molnar wrote:
* Ankur Arora wrote:
System: Oracle X6-2
CPU: 2 nodes * 10 cores/node * 2 threads/core
Intel Xeon E5-2630 v4 (Broadwellx, 6:79:1)
Memory: 256 GB evenly split between nodes
Microcode:0xb2
Add ports 5 and 7 which are connected to gmac cores 1 & 2.
These will be disabled for now.
Signed-off-by: Vivek Unune
---
.../boot/dts/bcm47094-linksys-panamera.dts| 24 +++
1 file changed, 24 insertions(+)
diff --git a/arch/arm/boot/dts/bcm47094-linksys-panamera.dts
b/arch
The pull request you sent on Tue, 13 Oct 2020 09:41:31 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.10-merge-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/37187df45af7d28d27b5c130c23f407ca9dbefa2
Thank you!
--
Deet-doot-dot, I am a bot.
On Wed, Oct 14, 2020 at 2:04 PM Andrew Cooper wrote:
>
> On 14/10/2020 18:53, Jason Andryuk wrote:
> > A Xen PVH domain doesn't have a PCI bus or devices,
>
> [*] Yet.
:)
> > so it doesn't need PCI support built in.
>
> Untangling the dependences is a good thing, but eventually we plan to
> put
Francesco Ruggeri wrote:
> On Wed, Oct 14, 2020 at 1:23 AM Florian Westphal wrote:
> >
> > Pablo Neira Ayuso wrote:
> > > Legacy would still be flawed though.
> >
> > Its fine too, new rule blob gets handled (and match/target checkentry
> > called) before old one is dismantled.
> >
> > We only h
Add a barrier to wait for all device_links SRCU sections to complete.
Signed-off-by: Michael Auchter
---
drivers/base/core.c| 10 ++
include/linux/device.h | 1 +
2 files changed, 11 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index bb5806a2bd4c..ef4429c4b1
This adds a unittest to test applying/reverting an overlay that contains
a link between two devices.
Signed-off-by: Michael Auchter
---
drivers/of/unittest-data/Makefile | 1 +
drivers/of/unittest-data/overlay_16.dts | 26 +
drivers/of/unittest.c
Signed-off-by: Michael Auchter
---
drivers/of/dynamic.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c
index 7478bfc8d440..a4e2881524e9 100644
--- a/drivers/of/dynamic.c
+++ b/drivers/of/dynamic.c
@@ -14,6 +14,7 @@
#include
#include
#includ
After updating to v5.9, I've started seeing errors in the kernel log
when using device tree overlays. Specifically, the problem seems to
happen when removing a device tree overlay that contains two devices
with some dependency between them (e.g., a device that provides a clock
and a device that con
On Wed, Oct 14, 2020 at 04:09:12PM +0200, Lukas Wunner wrote:
> Apparently the problem is that spi_unregister_controller() drops the
> last ref on the controller, causing it to be freed, and afterwards we
> access the controller's private data, which is part of the same
> allocation as struct spi_c
On 10/14/20 11:35 AM, Joe Perches wrote:
[...]
Here are 2 patches against the 'modules-next' branch of Jessica Yu's
'linux.git' repo.
I'm doing some little refactoring in module_sig_check()...
[1/2] module: merge repetitive strings in module_sig_check()
[2/2] module:
On Tue, Sep 22, 2020 at 10:39:32AM +0200, Dietmar Eggemann wrote:
> Two of the 102 elements of the cpu priority vector, among them the one
> for MAX_PRIO (140) representing the IDLE task, are never used.
>
> Remove them and adapt the cpupri implementation accordingly.
>
> Dietmar Eggemann (2):
>
"Serge E. Hallyn" writes:
> On Mon, Oct 12, 2020 at 12:01:09AM -0500, Eric W. Biederman wrote:
>> Andy Lutomirski writes:
>>
>> > On Sun, Oct 11, 2020 at 1:53 PM Josh Triplett
>> > wrote:
>> >>
>> >> On Fri, Oct 09, 2020 at 11:26:06PM -0500, Serge E. Hallyn wrote:
>> >> > > 3. Find a way to a
This makes the mapping continuous and frees up 100 for other usage.
Prev mapping:
p->rt_priority p->prio newpri cpupri
-1 -1 (CPUPRI_INVALID)
1000 (CPUPRI_NORMAL)
198 981
Add CPUPRI_HIGHER above the RT99 priority to denote the CPU is in use
by higher priority tasks (specifically deadline).
XXX: we should probably drive PUSH-PULL from cpupri, that would
automagically result in an RT-PUSH when DL sets cpupri to CPUPRI_HIGHER.
Signed-off-by: Peter Zijlstra (Intel)
On Wed, Oct 14, 2020 at 01:32:55AM -0700, Ankur Arora wrote:
> This can potentially improve page-clearing bandwidth (see below for
> performance numbers for two microarchitectures where it helps and one
> where it doesn't) and can help indirectly by consuming less cache
> resources.
>
> Any perfor
On Wed, Oct 14, 2020 at 08:45:37AM -0700, Andy Lutomirski wrote:
> On Wed, Oct 14, 2020 at 1:33 AM Ankur Arora wrote:
> >
> > Define clear_page_uncached() as an alternative_call() to clear_page_nt()
> > if the CPU sets X86_FEATURE_NT_GOOD and fallback to clear_page() if it
> > doesn't.
> >
> > Sim
James Bottomley writes:
> On Wed, 2020-10-14 at 19:57 +0200, Dirk Gouders wrote:
>> On my laptop the check introduced with 55707d531af62b (tpm_tis: Add a
>> check for invalid status) triggered the warning (output below).
>>
>> So, my laptop seems to be a candidate for testing.
>
> I'm afraid thi
On Wed, Oct 14, 2020 at 11:16:10AM -0700, Ian Rogers wrote:
> There were some issues in the original patch, they should be easy to
> fix. I'm more concerned that Peter's issues are addressed about the
> general direction of the patch, verbosity and testing frameworks. I
> see Vitor followed up wit
Hello,
in v3 Johan still found some inconsistencies in how I sorted (or didn't
sort) the device tree properties. The rules I applied now are:
at the beginning of a node: compatible, reg and interrupt stuff
status and #* at the end
i2c-scl-rising-time-ns before i2c-scl-fall
The prefix is already used in arm/armada-388-helios4.dts.
Signed-off-by: Uwe Kleine-König
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree/bindings/v
The hardware is described in detail on Kobol's wiki at
https://wiki.kobol.io/helios64/intro/.
Up to now the following peripherals are working:
- UART
- Micro-SD card
- eMMC
- ethernet port 1
- status LED
- temperature sensor on i2c bus 2
Signed-off-by: Uwe Kleine-König
---
arch/arm64/boo
On Wed, Oct 14, 2020 at 5:00 PM Peter Zijlstra wrote:
>
> On Wed, Oct 14, 2020 at 11:16:10AM -0700, Ian Rogers wrote:
>
> > There were some issues in the original patch, they should be easy to
> > fix. I'm more concerned that Peter's issues are addressed about the
> > general direction of the patc
On Wed, 14 Oct 2020 at 19:16, Serge Semin
wrote:
>
> On Wed, Oct 14, 2020 at 12:33:25PM +0200, Krzysztof Kozlowski wrote:
> > On Wed, 14 Oct 2020 at 12:23, Serge Semin
> > wrote:
> > >
> > > In accordance with the DWC USB3 bindings the corresponding node name is
> > > suppose to comply with Gener
Hi Richard!
> SLAB objects which outlive their memcg are moved to their parent
> memcg where they may be uncharged. However if they are moved to the
> root memcg, uncharging will result in negative page counter values as
> root has no page counters.
>
> To prevent this, we check whether we are ab
On Wed Oct 14, 2020 at 4:11 PM -03, Jonathan Corbet wrote:
>
> On Tue, 13 Oct 2020 23:13:17 +
> Nícolas F. R. A. Prado wrote:
>
> > The warnings were caused by the expressions matching words in the
> > translated versions of the documentation, since any unicode character
> > was matched.
> >
>
Hello,
syzbot found the following issue on:
HEAD commit:c77fb07f Merge branch 'netlink-export-policy-on-validation..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1722ff0050
kernel config: https://syzkaller.appspot.com/x/.config?x=fa2bf4058104211
dash
On Wed, 14 Oct 2020 20:09:10 +
Nícolas F. R. A. Prado wrote:
> One I had noted down was:
>
> WARNING: Unparseable C cross-reference: '调用debugfs_rename'
>
> which I believe occurred in the chinese translation.
>
> I think the problem is that in chinese there normally isn't space between the
Hi all,
In commit
e965857201e0 ("f2fs: wait for sysfs kobject removal before freeing
f2fs_sb_info")
Fixes tag
Fixes: bf9e697ecd4 ("f2fs: expose features to sysfs entry")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or mor
On 10/8/20 11:44 PM, Jarkko Sakkinen wrote:
>> Why is this so special that you need a subdirectory for a single driver
>> with a mere 2 device nodes? Do any other misc drivers have a new
>> subdirectory in /dev/ for them?
> Absolutely nothing as far as I'm concerned. Should have done that
> alread
On Wed, Oct 14, 2020 at 01:13:53PM +0300, Serge Semin wrote:
> The DWC USB3 driver and some DTS files like Exynos 5250, Keystone k2e, etc
> expects the DWC USB3 DT node to have the compatible string with the
> "synopsys" vendor prefix. Let's add the corresponding compatible string to
> the controll
On Wed, Oct 14, 2020 at 12:03:45PM -0700, Florian Fainelli wrote:
> On 10/14/20 8:05 AM, Cristian Marussi wrote:
> > Extend common protocol registration routines and provide some new generic
> > protocols' init/deinit helpers that tracks protocols' users and
> > automatically
> > perform the prope
Thanks,
I fixed it in f2fs-next branch.
Thanks,
On 10/15, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> e965857201e0 ("f2fs: wait for sysfs kobject removal before freeing
> f2fs_sb_info")
>
> Fixes tag
>
> Fixes: bf9e697ecd4 ("f2fs: expose features to sysfs entry")
>
> has these
On Wed, Oct 14, 2020 at 10:40:35PM +0300, Vladimir Oltean wrote:
> On Wed, Oct 14, 2020 at 04:09:12PM +0200, Lukas Wunner wrote:
> > Apparently the problem is that spi_unregister_controller() drops the
> > last ref on the controller, causing it to be freed, and afterwards we
> > access the control
On Tue, 13 Oct 2020 14:31:09 +0100, Cristian Marussi wrote:
> When a protocol registers its events the notification core takes care to
> re-scan the hashtable of pending event handlers and activate all the
> possibly existent handlers that refer to any of the events just registered
> by the new pro
On Tue, 13 Oct 2020 19:17:37 -0700, Florian Fainelli wrote:
> When more than a single SCMI device are present in the system, the
> creation of the notification workqueue with the WQ_SYSFS flag will lead
> to the following sysfs duplicate node warning:
>
> [9.259990] sysfs: cannot create duplic
On some platforms (eg armv7 due to the CONFIG_ARM_DMA_MEM_BUFFERABLE)
MMIO R/W operations always add memory barriers which can increase load,
decrease battery life or in general reduce performance unnecessarily
on devices which access a lot of configuration registers and where
ordering does not mat
Add set_alloc_info() helper and move kasan_set_track() into it. This will
simplify the code for one of the upcoming changes.
No functional changes.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/I0316193cbb4ecc9b87b7c2eee0dd79f8ec908c1a
---
mm/kasan/common.c | 7
Move get_free_info() call into quarantine_put() to simplify the call site.
No functional changes.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/Iab0f04e7ebf8d83247024b7190c67c3c34c7940f
---
mm/kasan/common.c | 2 +-
mm/kasan/kasan.h | 5 ++---
mm/kasan
This patchset is not complete (see particular TODOs in the last patch),
and I haven't performed any benchmarking yet, but I would like to start the
discussion now and hear people's opinions regarding the questions mentioned
below.
=== Overview
This patchset adopts the existing hardware tag-based
Rename get_alloc_info() and get_free_info() to kasan_get_alloc_meta()
and kasan_get_free_meta() to better reflect what those do, and avoid
confusion with kasan_set_free_info().
No functional changes.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/Ib6e4ba61c8b1211
Similarly to kasan_init() mark kasan_init_tags() as __init.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/I8792e22f1ca5a703c5e979969147968a99312558
---
include/linux/kasan.h | 4 ++--
mm/kasan/hw_tags.c| 2 +-
mm/kasan/sw_tags.c| 2 +-
3 files changed, 4
There's a config option CONFIG_KASAN_STACK that has to be enabled for
KASAN to use stack instrumentation and perform validity checks for
stack variables.
There's no need to unpoison stack when CONFIG_KASAN_STACK is not enabled.
Only call kasan_unpoison_task_stack[_below]() when CONFIG_KASAN_STACK
TODO: no meaningful description here yet, please see the cover letter
for this RFC series.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/If7d37003875b2ed3e0935702c8015c223d6416a4
---
mm/kasan/common.c | 69 +-
m
Add a helper that exposes information about whether the system supports
memory tagging to be called in generic code.
Signed-off-by: Andrey Konovalov
Link:
https://linux-review.googlesource.com/id/Ib4b56a42c57c6293df29a0cdfee334c3ca7bdab4
---
arch/arm64/include/asm/memory.h | 1 +
mm/kasan/kasan
Tag-based KASAN modes are initialized with kasan_init_tags() instead of
kasan_init() for the generic mode. Move the initialization message for
tag-based modes into kasan_init_tags().
Also fix pr_fmt() usage for KASAN code: generic mode doesn't need it,
tag-based modes should use "kasan:" instead o
Fix data race in prepend_path() with re-reading mnt->mnt_ns twice without
holding the lock. is_mounted() does check for NULL, but is_anon_ns(mnt->mnt_ns)
might re-read the pointer again which could be NULL already, if in between
reads one of kern_unmount()/kern_unmount_array()/umount_tree() sets mn
On Wed, 14 Oct 2020, Mickaël Salaün wrote:
>
> On 14/10/2020 20:52, Mickaël Salaün wrote:
> >
> > On 14/10/2020 20:07, James Morris wrote:
> >> On Thu, 8 Oct 2020, Mickaël Salaün wrote:
> >>
> >>> +config ARCH_EPHEMERAL_STATES
> >>> + def_bool n
> >>> + help
> >>> + An arch should select this
I'm afraid that the macro does not compile under MSVC:
warning C4067: unexpected tokens following preprocessor directive - expected a
newline (compiling source file ..\..\source\tools\acpiexec\aetests.c)
It looks like "__has_attribute" is not supported.
-Original Message-
From: Joe Per
On Wed, 2020-10-14 at 22:44 +0300, Sergey Shtylyov wrote:
> On 10/14/20 11:35 AM, Joe Perches wrote:
>
> [...]
> > > > > Here are 2 patches against the 'modules-next' branch of Jessica Yu's
> > > > > 'linux.git' repo.
> > > > > I'm doing some little refactoring in module_sig_check()...
> > > > >
Hi Linus,
Please pull this first large pile of new stuff for 5.10. The biggest
changes are two new features for the ondisk metadata: one to record the
sizes of the inode btrees in the AG to increase redundancy checks and to
improve mount times; and a second new feature to support timestamps
until
Hello Serge,
> > @@ -146,6 +150,9 @@ void __init plat_mem_setup(void)
> >
> > ioport_resource.start = ~0UL;
> > ioport_resource.end = 0UL;
> > +
> > + /* Stay away from the firmware working memory area for now. */
>
> > + memblock_reserve(PHYS_OFFSET, __pa_symbol(&_text));
>
> Shou
On 2020-10-14 8:45 a.m., Andy Lutomirski wrote:
On Wed, Oct 14, 2020 at 1:33 AM Ankur Arora wrote:
Define clear_page_uncached() as an alternative_call() to clear_page_nt()
if the CPU sets X86_FEATURE_NT_GOOD and fallback to clear_page() if it
doesn't.
Similarly define clear_page_uncached_flus
On 2020-10-14 12:56 p.m., Borislav Petkov wrote:
On Wed, Oct 14, 2020 at 01:32:55AM -0700, Ankur Arora wrote:
This can potentially improve page-clearing bandwidth (see below for
performance numbers for two microarchitectures where it helps and one
where it doesn't) and can help indirectly by con
On Wed, Oct 14, 2020 at 02:07:30PM -0700, Andy Lutomirski wrote:
> I assume it’s for a little optimization of clearing more than one
> page per SFENCE.
>
> In any event, based on the benchmark data upthread, we only want to do
> NT clears when they’re rather large, so this shouldn’t be just an
> al
On Wed, 2020-10-14 at 20:48 +, Moore, Robert wrote:
> I'm afraid that the macro does not compile under MSVC:
>
> warning C4067: unexpected tokens following preprocessor directive - expected
> a newline (compiling source file ..\..\source\tools\acpiexec\aetests.c)
>
> It looks like "__has_at
From: Tom Rix
Remove the trailing error message from the fixed lines
Signed-off-by: Tom Rix
---
scripts/checkpatch.pl | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index fab38b493cef..7d3db096bc44 100755
--- a/scripts/c
From: Tom Rix
Representative checkpatch.pl warning
WARNING: adding a line without newline at end of file
30: FILE: drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.h:30:
+#endif
Signed-off-by: Tom Rix
---
drivers/gpu/drm/amd/include/asic_reg/gc/gc_9_4_1_sh_mask.h | 2 +-
drivers/gpu/drm/amd/pm
On Wed, Oct 14, 2020 at 11:41:17AM -0700, Florian Fainelli wrote:
> On 10/14/20 11:11 AM, Serge Semin wrote:
> > On Wed, Oct 14, 2020 at 11:00:45AM -0700, Florian Fainelli wrote:
> >> On 10/14/20 3:14 AM, Serge Semin wrote:
> >>> In accordance with the Generic EHCI/OHCI bindings the corresponding n
On Wed, Oct 14, 2020 at 01:35:16PM -0500, Rob Herring wrote:
> On Wed, Oct 14, 2020 at 9:37 AM Serge Semin
> wrote:
> >
> > On Wed, Oct 14, 2020 at 05:09:37PM +0300, Felipe Balbi wrote:
> > >
> > > Hi Serge,
> > >
> > > Serge Semin writes:
> > > > In accordance with the DWC USB3 bindings the corr
On 10/13/20 3:16 AM, Catalin Marinas wrote:
> On Mon, Oct 12, 2020 at 01:14:50PM -0600, Khalid Aziz wrote:
>> On 10/12/20 11:22 AM, Catalin Marinas wrote:
>>> On Mon, Oct 12, 2020 at 11:03:33AM -0600, Khalid Aziz wrote:
On 10/10/20 5:09 AM, Catalin Marinas wrote:
> On Wed, Oct 07, 2020 at
Quoting Greg Kroah-Hartman (2020-10-03 03:56:53)
> On Fri, Oct 02, 2020 at 02:22:17PM -0700, Stephen Boyd wrote:
> > Quoting Mauro Carvalho Chehab (2020-09-28 23:22:11)
> > > Hi Stephen,
> > >
> > > While double-checking against yesterday's linux-next, I noticed
> > > that those two patches weren'
Commit
815f0ddb346c ("include/linux/compiler*.h: make compiler-*.h mutually
exclusive")
neglected to copy barrier_data() from compiler-gcc.h into
compiler-clang.h. The definition in compiler-gcc.h was really to work
around clang's more aggressive optimization, so this broke
barrier_data() on cl
From: Matteo Croce
The kernel cmdline reboot= argument allows to specify the CPU used
for rebooting, with the syntax `s` among the other flags, e.g.
reboot=soft,s4
reboot=warm,s31,force
In the early days the parsing was done with simple_strtoul(), later
deprecated in favor of the safer
Konstantin, writing to you based on 'git blame' :-)
The maintainer guide recommends using paperkey for the PGP master key,
which is a prefectly sane method.
I was just wondering that isn't a backup to a USB stick a reasonable
option? E.g. get a few USB sticks (new, unweared), store your master ke
On Wed, Oct 14, 2020 at 10:18:18PM +0200, Krzysztof Kozlowski wrote:
> On Wed, Oct 14, 2020 at 01:13:53PM +0300, Serge Semin wrote:
> > The DWC USB3 driver and some DTS files like Exynos 5250, Keystone k2e, etc
> > expects the DWC USB3 DT node to have the compatible string with the
> > "synopsys" v
Fix a crash on DEC platforms starting with:
VFS: Mounted root (nfs filesystem) on device 0:11.
Freeing unused PROM memory: 124k freed
BUG: Bad page state in process swapper pfn:1
page:(ptrval) refcount:0 mapcount:-128 mapping: index:0x1 pfn:0x1
flags: 0x0()
raw: 0100
Extract the logic needed to add a single cell described by a device tree
node from nvmem_add_cells_from_of, and call this new function for each
child node.
Signed-off-by: Michael Auchter
---
drivers/nvmem/core.c | 84 +---
1 file changed, 48 insertions(+),
This patchset adds the ability to add/remove nvmem cells to an nvmem
device using device tree overlays. This can be useful in situations
where an nvmem device is present in the base device tree and the
specific overlay that's loaded knows how to interpret the data within
the nvmem device.
Michael
CONFIG_OF_DYNAMIC allows runtime changes to the device tree. This patch
adds a OF_RECONFIG handler to receive notifications on tree changes to
support adding/removing cells from an nvmem device based on these
changes.
Signed-off-by: Michael Auchter
---
drivers/nvmem/core.c | 61 +
The pull request you sent on Wed, 14 Oct 2020 10:59:48 +0200:
> g...@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux
> tags/threads-v5.10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4da9af0014b51c8b015ed8c622440ef28912efe6
Thank you!
--
Deet-doot-dot,
801 - 900 of 1201 matches
Mail list logo
