On Wed, Feb 17, 2021 at 10:29:08PM +0530, Atul Gopinathan wrote:
> Resolve the following warning generated by sparse:
>
> drivers/staging//comedi/comedi_fops.c:2956:23: warning: incorrect type in
> assignment (different address spaces)
> drivers/staging//comedi/comedi_fops.c:2956:23:expected
On 17/02/21 18:29, Sean Christopherson wrote:
All that being said, I'm pretty we can eliminate setting
inject_page_fault dynamically. I think that would yield more
maintainable code. Following these flows is a nightmare. The change
itself will be scarier, but I'm pretty sure the end result
Quoting Kuogee Hsieh (2021-02-17 08:58:42)
> Add hbr3_hbr2 voltage and pre-emphasis swing table to support
> HBR3 link rate
>
> Signed-off-by: Kuogee Hsieh
> ---
> drivers/gpu/drm/msm/dp/dp_panel.c | 4
> drivers/phy/qualcomm/phy-qcom-qmp.c | 24 ++--
This spans to
On 17.02.21 18:26, Minchan Kim wrote:
On Wed, Feb 17, 2021 at 05:51:27PM +0100, David Hildenbrand wrote:
On 17.02.21 17:36, Minchan Kim wrote:
alloc_contig_range is usually used on cma area or movable zone.
It's critical if the page migration fails on those areas so
dump more debugging message
On Wed, Feb 17, 2021 at 5:36 PM Alex Ghiti wrote:
>
> Le 2/16/21 à 11:42 PM, Dmitry Vyukov a écrit :
> > On Tue, Feb 16, 2021 at 9:42 PM Alex Ghiti wrote:
> >>
> >> Hi Dmitry,
> >>
> >> Le 2/16/21 à 6:25 AM, Dmitry Vyukov a écrit :
> >>> On Tue, Feb 16, 2021 at 12:17 PM Dmitry Vyukov wrote:
>
From: Roderick Colenbrander
The DualSense controller has a built-in microphone exposed as an
audio device over USB (or HID using Bluetooth). A dedicated
button on the controller handles mute, but software has to configure
the device to mute the audio stream.
This patch captures the mute button
From: Roderick Colenbrander
Provide initial support for the DualSense lightbar and configure it
with a default PlayStation blue color.
Signed-off-by: Roderick Colenbrander
Reviewed-by: Barnabás Pőcze
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-playstation.c | 65
From: Roderick Colenbrander
The DualSense features 5 player LEDs below its touchpad, which are
meant as player id indications. The LEDs are configured with a
player ID determined by an ID allocator, which assign player ids
to ps_device instances.
This patch is a combination of the following
From: Roderick Colenbrander
The ret variable in ps_battery_get_property is set in an error path,
but never actually returned. Change the function to return ret.
Reported-by: kernel test robot
Signed-off-by: Roderick Colenbrander
Signed-off-by: Benjamin Tissoires
---
From: Roderick Colenbrander
Retrieve DualSense hardware and firmware information using a vendor
specific feature report. Report the data through sysfs and also
report using hid_info as there can be signficant differences between
versions.
Signed-off-by: Roderick Colenbrander
Reviewed-by:
Compaction always operates on pages from a single given zone when isolating
both pages to migrate and freepages. Pageblock boundaries are intersected with
zone boundaries to be safe in case zone starts or ends in the middle of
pageblock. The use of pageblock_pfn_to_page() protects against
From: Roderick Colenbrander
This reverts commit 05afe02ac24f ("HID: playstation: DualSense
set LEDs to default player id.")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
patches from linux-next.
This is not a big deal,
This reverts commit 1f902f8636e4 ("HID: playstation: report DualSense
hardware and firmware version.")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
LEDs patches from linux-next.
To have a cleaner merge with the new
From: Roderick Colenbrander
This reverts commit ebbe998a4a52 ("HID: playstation: add
DualSense lightbar support")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
patches from linux-next.
This is not a big deal, they are
From: Roderick Colenbrander
This reverts commit c240f0cb88ec ("HID: playstation: add
DualSense player LEDs support.")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
patches from linux-next.
This is not a big deal, they
From: Roderick Colenbrander
This reverts commit d5f7af85a537 ("HID: playstation: add microphone
mute support for DualSense.")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
patches from linux-next.
This is not a big
This reverts commit 3847d15b41ce ("HID: playstation: fix unused variable
in ps_battery_get_property.")
There is currently an ongoing discussion on linux-leds LKML,
and so to give us more room, we need to revert those related
LEDs patches from linux-next.
To have a cleaner merge with the new
Hey Adrien,
Thanks for submitting this!
On Mon, 15 Feb 2021 at 00:31, Adrien Grassein wrote:
>
> Lontium Lt8912 is a DSI to HDMI bridge.
>
> Signed-off-by: Adrien Grassein
> ---
> MAINTAINERS | 1 +
> drivers/gpu/drm/bridge/Kconfig | 14 +
>
[sending those patches on behalf of Roderick]
There is a current thread on LED LKML which basically means that
we have to revert the LED class exposure until things are settled.
I am sending here the full series that will end up in linux-next.
But with some git magic, the final PR to Linus will
These were untouched since 2.3.99-pre3, and the explanatory comment for
HID_DG_TIPPRESSURE is TipPressure on other places
Signed-off-by: Ahelenia Ziemiańska
---
drivers/hid/hid-input.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/hid/hid-input.c
This patchset adds support for stylus-on-touchscreen devices as found on
the OneMix 3 Pro and Dell Inspiron 15 7000 2-in-1 (7591), among others;
with it, they properly behave like a drawing tablet.
Patches 2 and 4 funxionally depend on patch 1.
Patch 4 needs patch 3 to apply.
The output of this
With this, these devices now behave as tablets as expected by userspace
Signed-off-by: Ahelenia Ziemiańska
---
drivers/hid/hid-input.c | 41 +
1 file changed, 41 insertions(+)
diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index
This re-adds the suffix to Win8 stylus-on-touchscreen devices,
now that they aren't erroneously marked as MT
Signed-off-by: Ahelenia Ziemiańska
---
drivers/hid/hid-multitouch.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/hid/hid-multitouch.c
This effectively changes collection_is_mt from
contact ID in report->field
to
(device is Win8 => collection is finger) && contact ID in report->field
Some devices erroneously report Pen for fingers,
and Win8 stylus-on-touchscreen devices report contact ID,
but mark the accompanying
Hello,
syzbot found the following issue on:
HEAD commit:c48f8607 Merge branch 'PTP-for-DSA-tag_ocelot_8021q'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16525cb0d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:9ec5eea5 lib/parman: Delete newline
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=107fb9d2d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link:
Hello,
syzbot found the following issue on:
HEAD commit:966df6de lan743x: sync only the received area of an rx rin..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11afe082d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
Hello,
syzbot found the following issue on:
HEAD commit:9ec5eea5 lib/parman: Delete newline
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11380d24d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link:
Hello,
syzbot found the following issue on:
HEAD commit:773dc50d Merge branch 'Xilinx-axienet-updates'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1744ba4cd0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link:
On Wed, Feb 17, 2021, Maxim Levitsky wrote:
> This fixes a (mostly theoretical) bug which can happen if ept=0
> on host and we run a nested guest which triggers a mmu context
> reset while running nested.
> In this case the .inject_page_fault callback will be lost.
>
> Signed-off-by: Maxim
modified QFPROM controller CORRECTED region size as per RAW region size
Signed-off-by: Ravi Kumar Bokka
---
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi
b/arch/arm64/boot/dts/qcom/sc7180.dtsi
index
On Wed, Feb 17, 2021 at 05:51:27PM +0100, David Hildenbrand wrote:
> On 17.02.21 17:36, Minchan Kim wrote:
> > alloc_contig_range is usually used on cma area or movable zone.
> > It's critical if the page migration fails on those areas so
> > dump more debugging message like memory_hotplug unless
A regression has been reported by Nicolas Boichat, found while using the
copy_file_range syscall to copy a tracefs file. Before commit
5dae222a5ff0 ("vfs: allow copy_file_range to copy across devices") the
kernel would return -EXDEV to userspace when trying to copy a file across
different
Hi Mate,
On Wednesday 17 Feb 2021 at 17:27:07 (+0100), Mate Toth-Pal wrote:
> We tested the pKVM changes pulled from here:
>
>
> > https://android-kvm.googlesource.com/linux qperret/host-stage2-v2
>
>
> We were using a target with Arm architecture with FEAT_S2FWB, and found that
> there
+CC linux-api, please do on further revisions.
Keeping rest of the e-mail.
On 2/17/21 4:48 PM, David Hildenbrand wrote:
> When we manage sparse memory mappings dynamically in user space - also
> sometimes involving MADV_NORESERVE - we want to dynamically populate/
> discard memory inside such a
On Wed, Feb 17, 2021 at 01:31:36PM +0200, Eli Cohen wrote:
> Allow to control vdpa device creation and destruction using the vdpa
> management tool.
>
> Examples:
> 1. List the management devices
> $ vdpa mgmtdev show
> pci/:3b:00.1:
> supported_classes net
>
> 2. Create vdpa instance
> $
On Wed, 17 Feb 2021, Petr Mladek wrote:
> On Mon 2021-02-15 16:39:26, Andy Shevchenko wrote:
>> +Cc: Sakari and printk people
>>
>> On Mon, Feb 15, 2021 at 4:28 PM Christian König
>> wrote:
>> > Am 15.02.21 um 15:21 schrieb Andy Shevchenko:
>> > > We have already few similar implementation and
On 17.02.21 17:46, Dave Hansen wrote:
On 2/17/21 7:48 AM, David Hildenbrand wrote:
While MADV_DONTNEED and FALLOC_FL_PUNCH_HOLE provide us ways to reliably
discard memory, there is no generic approach to populate ("preallocate")
memory.
Although mmap() supports MAP_POPULATE, it is not
On Wed, Feb 17, 2021 at 10:14:11PM +0530, Neeraj Upadhyay wrote:
> Add the MIDR part number info for the Arm Cortex-A78.
>
> Signed-off-by: Neeraj Upadhyay
> ---
> arch/arm64/include/asm/cputype.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/include/asm/cputype.h
>
Resolve the following warning generated by sparse:
drivers/staging//comedi/comedi_fops.c:2956:23: warning: incorrect type in
assignment (different address spaces)
drivers/staging//comedi/comedi_fops.c:2956:23:expected unsigned int
*chanlist
drivers/staging//comedi/comedi_fops.c:2956:23:
On Wed, Feb 17, 2021 at 07:54:47AM -0800, Paul E. McKenney wrote:
> On Wed, Feb 17, 2021 at 04:32:53PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2021-02-16 10:36:09 [-0800], Paul E. McKenney wrote:
> > > Hello, Sebastian,
> >
> > Hi Paul,
> >
> > > I punted on this for the moment by making
On 2/17/21 7:28 AM, cristian.bir...@microchip.com wrote:
> Hi Heikki,
>
> On 2/16/21 11:12 AM, Heikki Krogerus wrote:
>>
>> Hi Cristian,
>>
>> On Mon, Feb 15, 2021 at 05:25:29PM +, cristian.bir...@microchip.com
>> wrote:
>>> My name is Cristian and I'm working on bringing up a USB Type-C
Since CMA is used more widely, it's worth to have CMA
allocation statistics into vmstat. With it, we could
know how agressively system uses cma allocation and
how often it fails.
Signed-off-by: Minchan Kim
---
include/linux/vm_event_item.h | 3 +++
mm/cma.c | 12
Add hbr3_hbr2 voltage and pre-emphasis swing table to support
HBR3 link rate
Signed-off-by: Kuogee Hsieh
---
drivers/gpu/drm/msm/dp/dp_panel.c | 4
drivers/phy/qualcomm/phy-qcom-qmp.c | 24 ++--
2 files changed, 22 insertions(+), 6 deletions(-)
diff --git
Matthew has looked at how I'm fumbling about
trying to deal with Orangefs's need for much larger
than page-sized IO...
I think I need to implement orangefs_readahead
and from there fire off an asynchronous read
and while that's going I'll call readahead_page
with a rac that I've cranked up with
The function sync_runqueues_membarrier_state() should copy the
membarrier state from the @mm received as parameter to each runqueue
currently running tasks using that mm.
However, the use of smp_call_function_many() skips the current runqueue,
which is unintended. Replace by a call to
Add a new verbose mode to checkpatch.pl to emit additional verbose
test descriptions. The verbose mode is optional and can be enabled
by the flag -v or --verbose.
The test descriptions are parsed from the checkpatch documentation
file at `Documentation/dev-tools/checkpatch.rst`. The test
Add documentation for kernel script checkpatch.pl.
This documentation is also parsed by checkpatch to
enable a verbose mode.
The checkpatch message types are grouped by usage. Under
each group the types are described briefly. 34 of such
types are documented.
Signed-off-by: Dwaipayan Ray
---
Add a new verbose mode to checkpatch. The verbose test
descriptions are read from the checkpatch documentation
file at `Documentation/dev-tools/checkpatch.rst`.
The verbose mode is optional and can be enabled by the
flag -v or --verbose.
The documentation file is only parsed by checkpatch.pl
if
On 17.02.21 17:36, Minchan Kim wrote:
alloc_contig_range is usually used on cma area or movable zone.
It's critical if the page migration fails on those areas so
dump more debugging message like memory_hotplug unless user
specifiy __GFP_NOWARN.
Signed-off-by: Minchan Kim
---
mm/page_alloc.c
The kernel test robot reports when building with Kconfig
CONFIG_INTEGRITY_PLATFORM_KEYRING defined and
CONFIG_SYSTEM_DATA_VERIFICATION undefined:
ld.lld: error: undefined symbol: pkcs7_validate_trust
referenced by blacklist.c:128 (certs/blacklist.c:128)
Hi Mathieu,
Please see my replies to your questions inline
Again thanks for the continued review of this set
Cheers
Ben
> -Original Message-
> From: Mathieu Poirier
> Sent: Tuesday, February 16, 2021 10:48 AM
> To: Ben Levinsky
> Cc: devicet...@vger.kernel.org;
On 2/17/21 7:48 AM, David Hildenbrand wrote:
> While MADV_DONTNEED and FALLOC_FL_PUNCH_HOLE provide us ways to reliably
> discard memory, there is no generic approach to populate ("preallocate")
> memory.
>
> Although mmap() supports MAP_POPULATE, it is not applicable to the concept
> of sparse
On 2/17/21 8:26 AM, Jeffrey Hugo wrote:
From: Fan Wu
Currently ENOMEM is returned when MHI ring is full. This error code is
very misleading. Change to EAGAIN instead.
Signed-off-by: Fan Wu
Signed-off-by: Jeffrey Hugo
---
Reviewed-by: Hemant Kumar
--
The Qualcomm Innovation Center, Inc.
Add the MIDR part number info for the Arm Cortex-A78.
Signed-off-by: Neeraj Upadhyay
---
arch/arm64/include/asm/cputype.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/include/asm/cputype.h b/arch/arm64/include/asm/cputype.h
index ef5b040..3aced88 100644
---
We cannot process a power_down if the power state is DISABLED. There is
no valid mhi_ctxt in that case, so attepting to process the power_down
will likely result in a null pointer dereference. If the power state is
DISABLED, there is nothing to do anyways, so just bail early.
Signed-off-by:
Le 2/16/21 à 11:42 PM, Dmitry Vyukov a écrit :
On Tue, Feb 16, 2021 at 9:42 PM Alex Ghiti wrote:
Hi Dmitry,
Le 2/16/21 à 6:25 AM, Dmitry Vyukov a écrit :
On Tue, Feb 16, 2021 at 12:17 PM Dmitry Vyukov wrote:
On Fri, Jan 29, 2021 at 9:11 AM Dmitry Vyukov wrote:
I was fixing KASAN
alloc_contig_range is usually used on cma area or movable zone.
It's critical if the page migration fails on those areas so
dump more debugging message like memory_hotplug unless user
specifiy __GFP_NOWARN.
Signed-off-by: Minchan Kim
---
mm/page_alloc.c | 16 +++-
1 file changed, 15
Chris Down writes:
open(f);
debugfs_file_get(f);
fops->open();
inode->private = ps;
debugfs_file_put(f);
remove_printk_fmt_sec(); /* kfree ps */
read(f);
debugfs_file_get(f);
fops->read();
ps = inode->private; /* invalid */
debugfs_file_put(f);
Er, sorry, inode->private is
Huge pmd sharing for hugetlbfs is racy with userfaultfd-wp because
userfaultfd-wp is always based on pgtable entries, so they cannot be shared.
Walk the hugetlb range and unshare all such mappings if there is, right before
UFFDIO_REGISTER will succeed and return to userspace.
This will pair with
It is a preparation work to be able to behave differently in the per
architecture huge_pte_alloc() according to different VMA attributes.
Pass it deeper into huge_pmd_share() so that we can avoid the find_vma() call.
Suggested-by: Mike Kravetz
Reviewed-by: Mike Kravetz
Signed-off-by: Peter Xu
Huge pmd sharing could bring problem to userfaultfd. The thing is that
userfaultfd is running its logic based on the special bits on page table
entries, however the huge pmd sharing could potentially share page table
entries for different address ranges. That could cause issues on either:
-
Prepare for it to be called outside of mm/hugetlb.c.
Reviewed-by: Mike Kravetz
Signed-off-by: Peter Xu
---
include/linux/hugetlb.h | 8
mm/hugetlb.c| 8
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/hugetlb.h
This series tries to disable huge pmd unshare of hugetlbfs backed memory for
uffd-wp. Although uffd-wp of hugetlbfs is still during rfc stage, the idea of
this series may be needed for multiple tasks (Axel's uffd minor fault series,
and Mike's soft dirty series), so I picked it out from the
On 17/02/21 17:21, Sean Christopherson wrote:
On Wed, Feb 17, 2021, Maxim Levitsky wrote:
On Wed, 2021-02-17 at 17:06 +0100, Paolo Bonzini wrote:
On 17/02/21 15:57, Maxim Levitsky wrote:
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index b3e36dc3f164..e428d69e21c0 100644
---
Hi, Andrew,
On Wed, 17 Feb 2021 at 16:22, Andrew Lunn wrote:
>
> Hi Rui
>
> I don't know all the details for the MBus Windows...
Neither do I, I just followed the examples in other device trees
(namely armada-385-linksys.dtsi). I wanted to get hardware buffer
management working on my Omnia, in
On 17/02/21 9:23 pm, Greg KH wrote:
> On Wed, Feb 17, 2021 at 09:12:55PM +0530, Pritthijit Nath wrote:
>> This change fixes a sparse warning "incorrect type in argument 1
>> (different address spaces)".
>>
>> Signed-off-by: Pritthijit Nath
>> ---
>> drivers/staging/wlan-ng/p80211netdev.c | 2 +-
Hi Quentin,
On 2021-01-08 13:14, Quentin Perret wrote:
Hi all,
This is the v2 of the series previously posted here:
https://lore.kernel.org/kvmarm/20201117181607.1761516-1-qper...@google.com/
This basically allows us to wrap the host with a stage 2 when running in
nVHE, hence paving the
On Wed, 17 Feb 2021 17:22:17 +0100
Andrew Lunn wrote:
> On Wed, Feb 17, 2021 at 03:30:38PM +, Rui Salvaterra wrote:
> > Hardware buffer management has never worked on the Turris Omnia, as the
> > required MBus window hadn't been reserved. Fix thusly.
>
> Hi Rui
>
> I don't know all the
The 02/17/2021 11:14, Vladimir Oltean wrote:
>
> On Tue, Feb 16, 2021 at 10:42:03PM +0100, Horatiu Vultur wrote:
> > Add basic support for MRP. The HW will just trap all MRP frames on the
> > ring ports to CPU and allow the SW to process them. In this way it is
> > possible to for this node to
From: Fan Wu
Currently ENOMEM is returned when MHI ring is full. This error code is
very misleading. Change to EAGAIN instead.
Signed-off-by: Fan Wu
Signed-off-by: Jeffrey Hugo
---
v3: Fix subject
v2: Change from EBUSY to EAGAIN
drivers/bus/mhi/core/main.c | 2 +-
1 file changed, 1
Petr Mladek writes:
What about storing the pointer to struct pf_object into
struct printk_fmt_sec *ps into the s->file->f_inode->i_private?
Then we would not need any global list/table at all.
Unless I'm misreading the debugfs code, I think the following is possible:
open(f);
On Wed, Feb 10, 2021 at 04:03:18PM -0800, Mike Kravetz wrote:
> Add interfaces to set and clear soft dirty in hugetlb ptes. Make
> hugetlb interfaces needed for /proc clear_refs available outside
> hugetlb.c.
>
> arch/s390 has it's own version of most routines in asm-generic/hugetlb.h,
> so add
On Wed, Feb 17, 2021 at 03:30:38PM +, Rui Salvaterra wrote:
> Hardware buffer management has never worked on the Turris Omnia, as the
> required MBus window hadn't been reserved. Fix thusly.
Hi Rui
I don't know all the details for the MBus Windows...
Can this be set once in armada-385.dtsi
When parsing the structures in the shared memory, there are values which
come from the remote device. For example, a transfer completion event
will have a pointer to the tre in the relevant channel's transfer ring.
Such values should be considered to be untrusted, and validated before
use. If we
On Wed, Feb 17, 2021, Maxim Levitsky wrote:
> On Wed, 2021-02-17 at 17:06 +0100, Paolo Bonzini wrote:
> > On 17/02/21 15:57, Maxim Levitsky wrote:
> > > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> > > index b3e36dc3f164..e428d69e21c0 100644
> > > --- a/arch/x86/kvm/vmx/vmx.c
> >
On Tue, 2021-02-16 at 18:16 +0100, David Hildenbrand wrote:
[...]
> > > The discussion regarding migratability only really popped up
> > > because this is a user-visible thing and not being able to
> > > migrate can be a real problem (fragmentation, ZONE_MOVABLE, ...).
> >
> > I think the
The 02/17/2021 10:59, Vladimir Oltean wrote:
>
> On Tue, Feb 16, 2021 at 10:42:02PM +0100, Horatiu Vultur wrote:
> > diff --git a/net/bridge/br_mrp.c b/net/bridge/br_mrp.c
> > index 01c67ed727a9..12487f6fe9b4 100644
> > --- a/net/bridge/br_mrp.c
> > +++ b/net/bridge/br_mrp.c
> > @@ -639,7 +639,7
On Wed, 2021-02-17 at 17:06 +0100, Paolo Bonzini wrote:
> On 17/02/21 15:57, Maxim Levitsky wrote:
> > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> > index b3e36dc3f164..e428d69e21c0 100644
> > --- a/arch/x86/kvm/vmx/vmx.c
> > +++ b/arch/x86/kvm/vmx/vmx.c
> > @@ -6921,13 +6921,15
On Mon, Feb 15, 2021 at 03:44:52PM +, David Howells wrote:
> +++ b/include/linux/pagemap.h
> @@ -761,6 +761,8 @@ extern void __delete_from_page_cache(struct page *page,
> void *shadow);
> int replace_page_cache_page(struct page *old, struct page *new, gfp_t
> gfp_mask);
> void
On 2/17/21 6:47 AM, Perry Yuan wrote:
Hi Pierre:
On 2021/2/16 22:56, Pierre-Louis Bossart wrote:
+static const struct acpi_device_id privacy_acpi_device_ids[] = {
+ {"PNP0C09", 0},
+ { },
+};
+MODULE_DEVICE_TABLE(acpi, privacy_acpi_device_ids);
+
+static struct platform_driver
Hi again, Marek,
On Wed, 17 Feb 2021 at 16:10, Marek Behún wrote:
>
> Rui, in the future make the subject prefix
> [PATCH mvebu-dt]
> or
> [PATCH mvebu/dt]
>
> so that Gregory knows its for him and for which branch.
Thanks, will do!
Cheers,
Rui
On Wed, Feb 17, 2021, Kalra, Ashish wrote:
> From: Sean Christopherson
> On Thu, Feb 04, 2021, Ashish Kalra wrote:
> > From: Brijesh Singh
> >
> > The ioctl is used to retrieve a guest's shared pages list.
>
> >What's the performance hit to boot time if KVM_HC_PAGE_ENC_STATUS is passed
>
This driver is used by the Nitrogen8m Mini SBC.
Signed-off-by: Adrien Grassein
Reviewed-by: Krzysztof Kozlowski
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 292c00f893fc..bd310e91d4ed
Add audio description and pin muxing.
Signed-off-by: Adrien Grassein
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 86 +++
1 file changed, 86 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
Add FlexSPI description an pin muxing.
Signed-off-by: Adrien Grassein
Reviewed-by: Krzysztof Kozlowski
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
When parsing the structures in the shared memory, there are values which
come from the remote device. For example, a transfer completion event
will have a pointer to the tre in the relevant channel's transfer ring.
Such values should be considered to be untrusted, and validated before
use. If we
Add the description for espi support.
Signed-off-by: Adrien Grassein
Reviewed-by: Krzysztof Kozlowski
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 30 +++
1 file changed, 30 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
Add description and pin muxing for UARTs.
Signed-off-by: Adrien Grassein
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 50 ++-
1 file changed, 48 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
Add description for the four PWMs.
Signed-off-by: Adrien Grassein
Reviewed-by: Krzysztof Kozlowski
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 51 +++
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
Add usdhc3 description which corresponds to the wifi/bt chip
Signed-off-by: Adrien Grassein
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 31 +++
1 file changed, 31 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mm-nitrogen-r2.dts
Add description of USB.
usbotg2 seems to not working on all boards (including ones
from variscite).
Signed-off-by: Adrien Grassein
Reviewed-by: Krzysztof Kozlowski
---
.../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 42 +++
1 file changed, 42 insertions(+)
diff --git
Rui, in the future make the subject prefix
[PATCH mvebu-dt]
or
[PATCH mvebu/dt]
so that Gregory knows its for him and for which branch.
Marek
Le mer. 17 févr. 2021 à 15:22, Krzysztof Kozlowski a écrit :
>
> On Tue, Feb 16, 2021 at 12:19:39AM +0100, Adrien Grassein wrote:
> > Add description and pinmuxing for uarts.
> >
> > Signed-off-by: Adrien Grassein
> > ---
> > .../boot/dts/freescale/imx8mm-nitrogen-r2.dts | 53
Hi,
this patch set is to add several peripheral support for the
imx8mm-nitrogen-r2 board.
Thanks,
Update in v2:
- Fix some typo found in v1;
- Fix UART description
Adrien Grassein (8):
arm64: dts: imx8mm-nitrogen-r2: add wifi/bt chip
arm64: dts: imx8mm-nitrogen-r2: add USB support
On Tue 2021-02-16 17:27:08, Chris Down wrote:
> Petr Mladek writes:
> > > +/*
> > > + * Stores .printk_fmt section boundaries for vmlinux and all loaded
> > > modules.
> > > + * Add entries with store_printk_fmt_sec, remove entries with
> > > + * remove_printk_fmt_sec.
> > > + */
> > > +static
On Wed, Feb 17, 2021 at 04:58:45PM +0100, Horatiu Vultur wrote:
> > If a driver implements full MRP offload for a ring/interconnect
> > manager/automanager, should it return -EOPNOTSUPP when sw_backup=false?
>
> In that case it should return 0.
> So if the driver can:
> - fully support MRP, when
On 17/02/21 15:57, Maxim Levitsky wrote:
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index b3e36dc3f164..e428d69e21c0 100644
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -6921,13 +6921,15 @@ static fastpath_t vmx_vcpu_run(struct kvm_vcpu *vcpu)
if
On Tue, Feb 16, 2021 at 08:01:11PM -0800, Daniel Rosenberg wrote:
> I'm not sure what the conflict is, at least format-wise. Naturally,
> there would need to be some work to reconcile the two patches, but my
> patch only alters the format for directories which are encrypted and
> casefolded, which
On Wed, 17 Feb 2021 at 16:06, Jeffrey Hugo wrote:
>
> On 2/17/2021 8:02 AM, Loic Poulain wrote:
> > On Tue, 16 Feb 2021 at 19:50, Jeffrey Hugo wrote:
> >>
> >> From: Fan Wu
> >>
> >> Currently ENOMEM is returned when MHI ring is full. This error code is
> >> very misleading. Change to EBUSY
501 - 600 of 1042 matches
Mail list logo
