Move tag/untag action at the end of the function to avoid
tagging or untagging traffic if only vlan 0 is handled.
Signed-off-by: Gilles DOFFE
---
drivers/net/dsa/microchip/ksz8795.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/dsa/microchip/ksz8795.c
b/dri
If a VLAN is removed, the tagging policy should not be changed as
still active VLANs could be impacted.
Signed-off-by: Gilles DOFFE
---
drivers/net/dsa/microchip/ksz8795.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/dsa/microchip/ksz8795.c
b/drivers/net/dsa/microchip/ksz87
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert HDMI PHY binding to YAML schema mediatek,hdmi-phy.yaml
Applied, thanks
--
~Vinod
On Wed, Jan 13, 2021 at 09:30:28PM +0900, William Breathitt Gray wrote:
> On Wed, Jan 13, 2021 at 01:02:20PM +0100, Linus Walleij wrote:
> > On Wed, Jan 13, 2021 at 11:27 AM Andy Shevchenko
> > wrote:
> > > On Mon, Jan 11, 2021 at 11:55 AM David Laight
> > > wrote:
> >
> > > > basically 486 but
On Wed, Jan 13, 2021 at 03:32:32PM +0300, Kirill A. Shutemov wrote:
> On Tue, Jan 12, 2021 at 07:31:07PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 12, 2021 at 6:16 PM Matthew Wilcox wrote:
> > >
> > > The thing about the speculative page cache references is that they can
> > > temporarily bump
Boris, is it possible to have a topic branch for this patch?
Just take it through your tree pls.
Acked-by: Borislav Petkov
Paolo, Boris has acked this kernel patch, and if i need send new patchset to add this
acked-by info ? or kvm tree will directly pull this patchset? thanks.
I
On 11.01.21 20:40, Mike Rapoport wrote:
> From: Mike Rapoport
>
> The first 4Kb of memory is a BIOS owned area and to avoid its allocation
> for the kernel it was not listed in e820 tables as memory. As the result,
> pfn 0 was never recognised by the generic memory management and it is not a
> pa
On 2021/1/13 19:10, Peter Zijlstra wrote:
On Tue, Jan 12, 2021 at 11:38:12PM +0800, Lai Jiangshan wrote:
But the hard problem is "how to suppress the warning of
online&!active in __set_cpus_allowed_ptr()" for late spawned
unbound workers during hotplug.
I cannot see create_worker() go bad l
Il giorno lun 7 dic 2020 alle ore 07:43 Dmitry Torokhov
ha scritto:
>
> Hi AngeloGioacchino,
>
> On Wed, Oct 28, 2020 at 11:13:01PM +0100, khol...@gmail.com wrote:
> > +/**
> > + * nt36xxx_set_page - Set page number for read/write
> > + * @ts: Main driver structure
> > + *
> > + * Return: Always z
From: Tianjia Zhang
On the following call path, `sig->pkey_algo` is not assigned
in asymmetric_key_verify_signature(), which causes runtime
crash in public_key_verify_signature().
keyctl_pkey_verify
asymmetric_key_verify_signature
verify_signature
public_key_verify_signature
On Wed, Jan 13, 2021 at 5:23 AM Ferry Toth wrote:
>
> On Intel Tangier B0 and Anniedale the interrupt line, disregarding
> to have different numbers, is shared between HSU DMA and UART IPs.
> Thus on such SoCs we are expecting that IRQ handler is called in
> UART driver only. hsu_pci_irq was handl
On Wed, 13 Jan 2021 at 11:57, wrote:
>
> From: Ricky Wu
>
> Make sure voltage below 0.5V before power on
> when do power cycle
> At mmc-core recognition card phase will do
> power cycle quickly so our device need at least 100ms
> to make voltage down to below 0.5V
>
> Signed-off-by: Ricky Wu
Ap
On Wed, 13 Jan 2021 at 12:59, Aswath Govindraju wrote:
>
> The following series of patches,
> - Adds new compatible string for AM64 SoC
> - Adds support for AM64 SoC in sdhci_am654 driver
>
> This patch series is a combination of the patches [1] and [2].
>
> [1] - https://lore.kernel.org/patchwork
From: Tianjia Zhang
On the following call path, `sig->pkey_algo` is not assigned
in asymmetric_key_verify_signature(), which causes runtime
crash in public_key_verify_signature().
keyctl_pkey_verify
asymmetric_key_verify_signature
verify_signature
public_key_verify_signature
On Wed, 13 Jan 2021 at 12:34, Yue Hu wrote:
>
> From: Yue Hu
>
> Since they will always being in successful path to return 0 directly,
> no need to set err = 0.
>
> Signed-off-by: Yue Hu
Applied for next, thanks!
Kind regards
Uffe
> ---
> drivers/mmc/core/mmc.c | 4
> 1 file changed, 4
I found that on the syzbot dashboard, “WARNING: locking bug in
do_ipv6_setsockopt”(https://syzkaller.appspot.com/bug?id=6a970baf20aa5a64455be86fb920f468def703c6)
and
"WARNING: locking bug in do_ipv6_getsockopt"
(https://syzkaller.appspot.com/bug?id=e97be0bf4d30813e951bcc6249e72c592a790164)
should s
On 1/13/21 2:21 AM, Geert Uytterhoeven wrote:
> Hi Rob,
>
> On Wed, Jan 13, 2021 at 8:58 AM Rob Landley wrote:
>> On 1/12/21 4:46 PM, Linus Walleij wrote:
>>> On Tue, Jan 12, 2021 at 3:45 PM John Paul Adrian Glaubitz
>>> wrote:
Yeah, I have the same impression that's the strong commercial i
Changes since RFC:
- lockdep didn't like reintroducing slab_mutex in kmem_cache_shrink(), so
instead explain why it's not needed after all (in Patch 2)
- the above is only safe with Patch 1 already in place, so order it first
(current Patch 1 was Patch 3 in RFC)
Some related work caused me to
Commit e4f8e513c3d3 ("mm/slub: fix a deadlock in show_slab_objects()") has
fixed a problematic locking order by removing the memory hotplug lock
get/put_online_mems() from show_slab_objects(). During the discussion, it was
argued [1] that this is OK, because existing slabs on the node would prevent
Since commit 03afc0e25f7f ("slab: get_online_mems for
kmem_cache_{create,destroy,shrink}") we are taking memory hotplug lock for SLAB
and SLUB when creating, destroying or shrinking a cache. It is quite a heavy
lock and it's best to avoid it if possible, as we had several issues with
lockdep compla
SLAB has been using get/put_online_cpus() around creating, destroying and
shrinking kmem caches since 95402b382901 ("cpu-hotplug: replace per-subsystem
mutexes with get_online_cpus()") in 2008, which is supposed to be replacing
a private mutex (cache_chain_mutex, called slab_mutex today) with syste
Hello all,
On Sat, Jan 09, 2021 at 04:01:05AM +0200, Laurent Pinchart wrote:
> Hi Peter, Steven and Sergey,
>
> Could you please let us know if you're fine with this patch getting
> merged in v5.12 through the linux-media tree ? The cover letter contains
> additional details (in a nutshell, this
On Tue, Jan 12, 2021 at 10:51 PM Peter Zijlstra wrote:
>
> Mark the per-cpu workqueue workers as KTHREAD_IS_PER_CPU.
>
> Workqueues have unfortunate semantics in that per-cpu workers are not
> default flushed and parked during hotplug, however a subset does
> manual flush on hotplug and hard relie
please ignore, that was accidentially sent.
On Wed, 13 Jan 2021 00:15:47 +0100
Andreas Kemnade wrote:
> Configuration was correct enough to work with the pre-configuration done by
> uboot. While at it, also document the location.
>
> Signed-off-by: Andreas Kemnade
> ---
> arch/arm/boot/dts/im
Ich bin Manuel Franco und habe am 23. April 2019 den Power Ball
Jackpot im Wert von 758,7 Millionen Dollar gewonnen. Ich gewähre 5
Personen jeweils 500.000,00 Euro und Sie gehören zu den 5 glücklichen
Gewinnern, die ausgewählt wurden, um meine Spende von 500.000,00 Euro
zu erhalten.
Kontaktieren S
The current fixed metadata version format (version 0), means that adding
metadata parameter items renders files from a previous version of perf
unreadable. Per CPU parameters appear in a fixed order, but there is no
field to indicate the number of ETM parameters per CPU.
This patch updates the per
Currently, all sorts of skb allocation always do allocate
skbuff_heads one by one via kmem_cache_alloc().
On the other hand, we have percpu napi_alloc_cache to store
skbuff_heads queued up for freeing and flush them by bulks.
We can use this cache not only for bulk-wiping, but also to obtain
heads
Instead of calling kmem_cache_alloc() every time when building a NAPI
skb, (re)use skbuff_heads from napi_alloc_cache.skb_cache. Previously
this cache was only used for bulk-freeing skbuff_heads consumed via
napi_consume_skb() or __kfree_skb_defer().
Typical path is:
- skb is queued for freeing f
Instead of immediate freeing, recycle GRO_MERGED_FREE skbs into
NAPI skb cache. This is safe, because napi_gro_receive() and
napi_gro_frags() are called only inside NAPI softirq context.
As many drivers call napi_alloc_skb()/napi_get_frags() on their
receive path, this becomes especially useful.
S
In preparation for skbuff_heads caching and reusing, open-code
__build_skb() inside __napi_alloc_skb() with factoring out
the skbbuff_head allocation itself.
Note that the return value of __build_skb_around() is not checked
since it never returns anything except the given skb.
Signed-off-by: Alexa
Now that my little helper has landed, use it more. On top of the
existing check this also uses lockdep through the fs_reclaim
annotations.
Signed-off-by: Daniel Vetter
Cc: Andrew Morton
Cc: linux...@kvack.org
---
mm/dmapool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/m
Now that my little helper has landed, use it more. On top of the
existing check this also uses lockdep through the fs_reclaim
annotations.
Signed-off-by: Daniel Vetter
Cc: Andrew Morton
Cc: linux...@kvack.org
---
mm/backing-dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Linus,
Are you willing to take this between merge windows - or does it need to wait
for the next merge window? It's not technically a bug fix to the kernel, but
it does have a CVE attached to it.
Note that I've also updated Jarkko's address in his Reviewed-by since his
Intel address no longer
On Tue, Jan 12, 2021 at 10:23:12AM +, Mark Rutland wrote:
> On Fri, Jan 08, 2021 at 09:39:53PM +0100, Peter Zijlstra wrote:
> > On Fri, Jan 08, 2021 at 09:32:58AM +, Will Deacon wrote:
> > > Hi Arnd,
> > >
> > > On Fri, Jan 08, 2021 at 10:19:56AM +0100, Arnd Bergmann wrote:
> > > > From: A
On Wed, Jan 13, 2021 at 1:02 PM Linus Walleij wrote:
> On Wed, Jan 13, 2021 at 11:27 AM Andy Shevchenko
> wrote:
> > On Mon, Jan 11, 2021 at 11:55 AM David Laight
> > wrote:
> > > basically 486 but have a few extra instructions - probably just cpuid
> > > and (IIRC) rdtsc.
> > > Designed for l
In case of a PTRACE_SEIZE request, the PT_SEIZED flag is always set
at the beginning of ptrace_attach. Hence, there is no need to set
it again (neither "flags" nor "seize" are modified in between/after
the initial assignment).
Signed-off-by: Marcus Huewe
---
kernel/ptrace.c | 2 --
1 file change
On Fri, Jan 8, 2021 at 5:34 AM Chunyan Zhang wrote:
>
> On Fri, 8 Jan 2021 at 10:25, Rob Herring wrote:
> >
> > On Wed, Dec 23, 2020 at 07:16:32PM +0800, Chunyan Zhang wrote:
> > > From: Chunyan Zhang
> > >
> > > This patch only adds bindings to support display iommu, support for others
> > > wo
On Wed, Jan 13, 2021 at 7:39 AM wrote:
> From 82ebcf43481be21ee3e32ec1749b42f651737880 Mon Sep 17 00:00:00 2001
> From: Yang Yang
> Date: Wed, 13 Jan 2021 20:18:04 +0800
> Subject: [PATCH] [RFC,v1,1/1] speed up syscall rule match while exiting
> syscall
> If user add any syscall rule, in all sy
Now that my little helper has landed, use it more. On top of the
existing check this also uses lockdep through the fs_reclaim
annotations.
Signed-off-by: Daniel Vetter
Cc: Andrew Morton
Cc: linux...@kvack.org
--
v2: git add everything ... :-/
---
mm/dmapool.c | 3 ++-
1 file changed, 2 insertio
Now that my little helper has landed, use it more. On top of the
existing check this also uses lockdep through the fs_reclaim
annotations.
Signed-off-by: Daniel Vetter
Cc: Andrew Morton
Cc: linux...@kvack.org
--
v2: git add everything ... oops
---
mm/backing-dev.c | 2 +-
1 file changed, 1 inse
Hi Ulf,
Thanks.
>-Original Message-
>From: Ulf Hansson
>Sent: Wednesday, January 13, 2021 7:26 PM
>To: Zulkifli, Muhammad Husaini
>Cc: Michal Simek ; linux-...@vger.kernel.org;
>Linux ARM ; Linux Kernel Mailing List
>; Hunter, Adrian ;
>Shevchenko, Andriy
>Subject: Re: [PATCH v1 0/2]
On Fri, Jan 08, 2021 at 03:34:16PM +0200, Matti Vaittinen wrote:
> The BD71828 allows configuring the clk32kout pin mode to CMOS or
> open-drain. Add device-tree property for specifying the preferred mode.
>
> Signed-off-by: Matti Vaittinen
> ---
> .../devicetree/bindings/mfd/rohm,bd71828-pmic.y
On Tue, Jan 12, 2021 at 08:10:14AM +0200, Matti Vaittinen wrote:
>
> On Mon, 2021-01-11 at 13:09 -0600, Rob Herring wrote:
> > On Fri, Jan 08, 2021 at 03:36:38PM +0200, Matti Vaittinen wrote:
> > > Add binding documentation for regulators on ROHM BD71815 PMIC.
> > > 5 bucks, 7 LDOs and a boost for
On Mon, Jan 11, 2021 at 01:01:50PM -0800, Mike Kravetz wrote:
> As hugetlbfs evolved, state information about hugetlb pages was added.
> One 'convenient' way of doing this was to use available fields in tail
> pages. Over time, it has become difficult to know the meaning or contents
> of fields si
During system resume/suspend, hba could be NULL. In this case, do not touch
eh_sem.
Fixes: 88a92d6ae4fe ("scsi: ufs: Serialize eh_work with system PM events and
async scan")
Acked-by: Stanley Chu
Signed-off-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 17 ++---
1 file changed, 14 i
User layer may access sysfs nodes when system PM ops or error handling
is running, which can cause various problems. Rename eh_sem to host_sem
and use it to protect PM ops and error handling from user layer intervene.
Acked-by: Avri Altman
Reviewed-by: Stanley Chu
Signed-off-by: Can Guo
---
dr
Hi All,
On Tue, 2021-01-12 at 16:03 -0800, Florian Fainelli wrote:
> On 1/5/21 7:41 PM, Claire Chang wrote:
> > Add the initialization function to create restricted DMA pools from
> > matching reserved-memory nodes in the device tree.
> >
> > Signed-off-by: Claire Chang
> > ---
> > include/linu
On 07-01-21, 23:49, Mathias Kresin wrote:
> Commit 65dc2e725286 ("usb: dwc2: Update Core Reset programming flow.")
> revealed that the phy isn't ready immediately after enabling it's
> clocks. The dwc2_check_core_version() fails and the dwc2 usb driver
> errors out.
>
> Add a short delay to let th
- Le 13 Jan 21, à 13:45, Gilles Doffe gilles.do...@savoirfairelinux.com a
écrit :
> The FID (Filter ID) is a 7 bits field used to link the VLAN table
> to the static and dynamic mac address tables.
> Until now the KSZ8795 driver could only add one VLAN as the FID was
> always set to 1.
> This
On 24-12-20, 17:12, Kishon Vijay Abraham I wrote:
> The frequency of the txmclk between PCIe and SERDES has
> changed to 250MHz from 500MHz. Configure full rate divider
> for AM64 accordingly.
>
> Signed-off-by: Kishon Vijay Abraham I
> ---
> drivers/phy/ti/phy-j721e-wiz.c | 43 +
Hello, Sergei
On Tue, Jan 12, 2021 at 7:15 PM Sergei Shtylyov
wrote:
>
> Hello!
>
> On 1/12/21 5:36 AM, menglong8.d...@gmail.com wrote:
>
[]
> > irq = platform_get_irq(pdev, 0);
> > - if (irq <= 0) {
> > - dev_err(&pdev->dev, "no IRQ resource found\n");
> > + if (irq
should_proactive_compact_node() returns true when sum of the
fragmentation score of all the zones in the node is greater than the
wmark_high of compaction which then triggers the proactive compaction
that operates on the individual zones of the node. But proactive
compaction runs on the zone only w
Lee Jones 於 2021年1月13日 週三 下午8:21寫道:
>
> On Thu, 17 Dec 2020, cy_huang wrote:
>
> > From: ChiYuan Huang
> >
> > This adds support Richtek RT4831 core. It includes four channel WLED driver
> > and Display Bias Voltage outputs.
> >
> > Signed-off-by: ChiYuan Huang
> > ---
> > since v5
> > - Rename
This patch moves the physical cpu tracking from the vcpu
to the vmcb in svm_switch_vmcb. If either vmcb01 or vmcb02
change physical cpus from one vmrun to the next the vmcb's
previous cpu is preserved for comparison with the current
cpu and the vmcb is marked dirty if different. This prevents
the p
This patch moves the asid_generation from the vcpu to the vmcb
in order to track the ASID generation that was active the last
time the vmcb was run. If sd->asid_generation changes between
two runs, the old ASID is invalid and must be changed.
Suggested-by: Paolo Bonzini
Signed-off-by: Cathy Avery
On 24-12-20, 17:12, Kishon Vijay Abraham I wrote:
> cmn_refclk_ lines in Torrent SERDES is used for connecting external
> reference clock. cmn_refclk_ can also be configured to output the
> reference clock. In order to drive the refclk out from the SERDES
> (Cadence Torrent), PHY_EN_REFCLK should b
Hi Adam,
On 12/01/21 18:00, Adam Ford wrote:
> On Tue, Jan 12, 2021 at 10:45 AM Luca Ceresoli wrote:
>>
>> Hi Adam,
>>
>> On 11/01/21 17:40, Adam Ford wrote:
>>> On Sat, Jan 9, 2021 at 12:02 PM Luca Ceresoli wrote:
Hi Adam,
On 09/01/21 04:00, Adam Ford wrote:
> On Fri, Ja
In the cases where vmcbs change processors from one vmrun to another updated
information in the vmcb from a prior run can potentially be lost. By tracking
the physical cpu and asid_generation per vmcb instead of svm->vcpu the following
scenario illustrated by Paolo can be avoided.
---
On 12-01-21, 09:38, Zou Wei wrote:
> Fix the following sparse warning:
>
> drivers/phy/mediatek/phy-mtk-mipi-dsi.c:237:24: warning: symbol
> 'mtk_mipi_tx_driver' was not declared. Should it be static?
Applied, thanks
--
~Vinod
Patch fixes the following errors:
ld: drivers/usb/cdns3/cdnsp-pci.o: in function `cdnsp_pci_remove':
cdnsp-pci.c:(.text+0x80): undefined reference to `cdns_remove'
ld: drivers/usb/cdns3/cdnsp-pci.o: in function `cdnsp_pci_probe':
cdnsp-pci.c:(.text+0x34c): undefined reference to `cdns_init'
Issue
On 06-01-21, 21:58, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Changes that require mentioning:
> 1. interrupt-names
>Name "wakeup" was changed to the "wake". It matches example and what
>Linux driver looks for in the first place
> 2. brcm,ipp and brcm,ioc
>Both were described as
On 13/01/21 21:28, Lai Jiangshan wrote:
> On Tue, Jan 12, 2021 at 10:51 PM Peter Zijlstra wrote:
>> @@ -4972,9 +4977,11 @@ static void rebind_workers(struct worker
>> * of all workers first and then clear UNBOUND. As we're called
>> * from CPU_ONLINE, the following shouldn't fai
On 13-01-21, 11:59, Mauro Carvalho Chehab wrote:
> Changeset ba2bf1f090eb ("dt-bindings: phy: Add Cadence Sierra PHY bindings in
> YAML format")
> renamed: Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt
> to: Documentation/devicetree/bindings/phy/phy-cadence-sierra.yaml.
>
> Update
On Tue 12-01-21 10:12:03, Suren Baghdasaryan wrote:
> On Mon, Jan 11, 2021 at 11:46 PM Michal Hocko wrote:
> >
> > On Mon 11-01-21 09:06:22, Suren Baghdasaryan wrote:
> > > process_madvise currently requires ptrace attach capability.
> > > PTRACE_MODE_ATTACH gives one process complete control over
* Randy Dunlap [210112 16:23]:
> Hi--
>
> On 1/12/21 8:11 AM, Liam R. Howlett wrote:
> > Avoid allocating a new VMA when it is not necessary. Expand or contract
> > the existing VMA instead. This avoids unnecessary tree manipulations
> > and allocations.
> >
> > Once the VMA is known, use it d
On 12/01/21 17:53, Sean Christopherson wrote:
On Tue, Jan 12, 2021, Paolo Bonzini wrote:
On 12/01/21 00:01, Sean Christopherson wrote:
Perhaps cpuid_query_maxphyaddr() should just look at the low 5 bits of
CPUID.8008H:EAX?
The low 6 bits I guess---yes, that would make sense and it would h
On Tue 12-01-21 09:51:24, Suren Baghdasaryan wrote:
> On Tue, Jan 12, 2021 at 9:45 AM Oleg Nesterov wrote:
> >
> > On 01/12, Michal Hocko wrote:
> > >
> > > On Mon 11-01-21 09:06:22, Suren Baghdasaryan wrote:
> > >
> > > > What we want is the ability for one process to influence another process
>
Hey Marc,
On Wednesday 13 Jan 2021 at 11:33:13 (+), Marc Zyngier wrote:
> > +#undef KVM_HYP_CPU_FTR_REG
> > +#define KVM_HYP_CPU_FTR_REG(id, name) \
> > + { .sys_id = id, .dst = (struct arm64_ftr_reg *)&kvm_nvhe_sym(name) },
> > +static const struct __ftr_reg_copy_entry {
> > + u32
Clear-up any confusion surrounding the Fixes: tag with regards to the
need to Cc: the stable mailing list when submitting stable patch
candidates.
Cc: Greg Kroah-Hartman
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Signed-off-by: Lee Jones
---
Documentation/process/submitting-patches.rst
On Wed, 2021-01-13 at 07:53 -0600, Rob Herring wrote:
> On Tue, Jan 12, 2021 at 08:10:14AM +0200, Matti Vaittinen wrote:
> > On Mon, 2021-01-11 at 13:09 -0600, Rob Herring wrote:
> > > On Fri, Jan 08, 2021 at 03:36:38PM +0200, Matti Vaittinen wrote:
> > > > Add binding documentation for regulators
On Wed, Jan 13, 2021 at 07:11:22PM +0800, Dongliang Mu wrote:
> The missing check of ir->buf_in[i+1] can lead to an shift-out-of-bound
> in mceusb_handle_command or mceusb_dev_printdata. This patch adds a
> check to limit its value lower than 16. The concrete report of UBSAN is
> as follows.
>
> U
13.01.2021 13:27, Greg Kroah-Hartman пишет:
> On Wed, Jan 13, 2021 at 12:01:51PM +0300, Dmitry Osipenko wrote:
>> 13.01.2021 04:20, Peter Chen пишет:
>>> On 21-01-12 09:56:37, Dmitry Osipenko wrote:
29.12.2020 17:26, Dmitry Osipenko пишет:
> 29.12.2020 08:16, Peter Chen пишет:
>> On 20
13.01.2021 04:22, Furquan Shaikh пишет:
> On Tue, Jan 12, 2021 at 5:09 AM Greg Kroah-Hartman
> wrote:
>>
>> On Tue, Jan 12, 2021 at 01:45:25PM +0100, Rafael J. Wysocki wrote:
>>> On Tue, Jan 12, 2021 at 10:55 AM Dmitry Osipenko wrote:
02.12.2020 00:30, Furquan Shaikh пишет:
> When t
On Tue, Jan 12, 2021 at 10:51:29PM -0600, Samuel Holland wrote:
> The register writes during driver removal occur after the device is
> already put back in reset, so they never had any effect.
>
> Signed-off-by: Samuel Holland
> ---
> drivers/media/rc/sunxi-cir.c | 10 --
> 1 file change
This driver is mandatory for the nitrogen8m mini board
when booting from the sdcard slot.
Signed-off-by: Adrien Grassein
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 3ca9d03d5cb3..bd6ac11ad6
Tested with a basic Build Root configuration booting from sdcard.
Signed-off-by: Adrien Grassein
---
arch/arm64/boot/dts/freescale/Makefile| 1 +
.../dts/freescale/imx8mm-nitrogen8mm_rev2.dts | 364 ++
2 files changed, 365 insertions(+)
create mode 100644 arch/arm64/bo
The Nitrogen8M Mini is an ARM based single board computer (SBC).
Signed-off-by: Adrien Grassein
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml
b/Documentation/devicetree/bindings/arm/fsl.yaml
Hello,
This patch set aims is to add the support of the Nitrogen8M Mini SBC
from Boundary Devices.
Thanks,
Update in v2:
- Rewrite the dts (Remove the unused wlan and audio);
- Remove useless definition;
- Take in account review.
Adrien Grassein (3):
dt-bindings: arm: imx: add imx8mm ni
On Wednesday 13 Jan 2021 at 14:23:03 (+), Quentin Perret wrote:
> Good point, that would be nice indeed. Can I use that from outside an
> __init function?
Just gave it a go, and the answer to this appears to be yes,
surprisingly -- I was expecting a compile-time warning similar to what
we get
On Wed, Jan 13, 2021 at 2:37 PM Alexander Lobakin wrote:
>
> Instead of calling kmem_cache_alloc() every time when building a NAPI
> skb, (re)use skbuff_heads from napi_alloc_cache.skb_cache. Previously
> this cache was only used for bulk-freeing skbuff_heads consumed via
> napi_consume_skb() or _
On Tue, Jan 12, 2021 at 10:51:31PM -0600, Samuel Holland wrote:
> In preparation for adding suspend/resume hooks, factor out the hardware
> initialization from the driver probe/remove functions.
>
> The timeout programmed during init is taken from the `struct rc_dev` so
> it is maintained across a
Hi Adam,
On 13/01/21 13:31, Adam Ford wrote:
> On Tue, Jan 12, 2021 at 9:16 PM Rob Herring wrote:
>>
>> On Wed, Jan 06, 2021 at 11:38:59AM -0600, Adam Ford wrote:
>>> There are two registers which can set the load capacitance for
>>> XTAL1 and XTAL2. These are optional registers when using an
>>>
Hi Peter,
Can you replace the previous version with this one.
The v1 still has problem with undefined reference when CONFIG_PCI or
CONFIG_ACPI are disabled.
V2 fixes this issue.
Thanks,
Regards,
Pawel Laszczak
>From: Pawel Laszczak
>Sent: Wednesday, January 13, 2021 3:14 PM
>To: peter.c...
Hi Adam,
On 09/01/21 03:48, Adam Ford wrote:
> On Fri, Jan 8, 2021 at 4:49 PM Luca Ceresoli wrote:
>>
>> Hi Adam,
>>
>> On 06/01/21 18:38, Adam Ford wrote:
>>> There are two registers which can set the load capacitance for
>>> XTAL1 and XTAL2. These are optional registers when using an
>>> extern
On Wed, Jan 13, 2021 at 08:05:11PM +0800, Zhangfei Gao wrote:
> > > + /* Device-tree can set the stall property */
> > > + if (!pdev->dev.of_node &&
> > > + device_add_properties(&pdev->dev, properties))
> > Does this mean "dma-can-stall" *can* be set via DT, and if it is, this
> > quirk is not
On Tue, Jan 12, 2021 at 11:11 PM Jason Wang wrote:
>
>
> On 2021/1/13 上午7:47, Willem de Bruijn wrote:
> > On Tue, Jan 12, 2021 at 3:29 PM Yuri Benditovich
> > wrote:
> >> On Tue, Jan 12, 2021 at 9:49 PM Yuri Benditovich
> >> wrote:
> >>> On Tue, Jan 12, 2021 at 9:41 PM Yuri Benditovich
> >>> wr
The arm and riscv have same logic to check and reserve
the memory of initrd, let's provide a common function
to reduce duplicated code.
Signed-off-by: Kefeng Wang
---
PS:
- Other architecture may use this function too, eg, csky,
could guoren check it? thanks.
arch/arm/mm/init.c | 43 +---
Counting text lines in a record simply involves counting the number
of newline characters (+1). However, it is searching the full data
block for newline characters, even though the text data can be (and
often is) a subset of that area. Since the extra area in the data
block was never initialized, t
On Tue, Jan 12, 2021 at 9:29 PM Heikki Krogerus
wrote:
>
> On Wed, Jan 06, 2021 at 12:39:25AM +0800, Kyle Tso wrote:
> > This patch provides the implementation of Collision Avoidance introduced
> > in PD3.0. The start of each Atomic Message Sequence (AMS) initiated by
> > the port will be denied i
In general, device drivers should not be enabled by default.
Fixes: 657bc1d10bfc23ac ("r8153_ecm: avoid to be prior to r8152 driver")
Signed-off-by: Geert Uytterhoeven
---
drivers/net/usb/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/usb/Kconfig b/drivers/net/usb/Kconfig
On Mon, Jan 11, 2021 at 01:01:50PM -0800, Mike Kravetz wrote:
> + if (hpage_spool(page)) {
Could this be named hpage_subpool(), please?
On Tue 12-01-21 11:30:11, Johannes Weiner wrote:
> When a value is written to a cgroup's memory.high control file, the
> write() context first tries to reclaim the cgroup to size before
> putting the limit in place for the workload. Concurrent charges from
> the workload can keep such a write() loo
On Wed, Jan 13, 2021 at 2:11 PM Badhri Jagan Sridharan
wrote:
>
> Hi Kyle,
>
> Do you want to handle the FAST_ROLE_SWAP case as well ?
>
I forgot this part
Thanks for catching this.
I will fix it.
> You would have to fix up in two places:
>
> #1
> - if (port->state == S
+++ Frank van der Linden [07/01/21 19:30 +]:
5fdc7db644 ("module: setup load info before module_sig_check()")
moved the ELF setup, so that it was done before the signature
check. This made the module name available to signature error
messages.
However, the checks for ELF correctness in setup
On Tue, Jan 12, 2021 at 2:46 PM Vincent Guittot
wrote:
> On Tue, 12 Jan 2021 at 12:25, Guillaume Tucker
> wrote:
> >
> > Some details can be found here:
> >
> > https://kernelci.org/test/case/id/5ffb978de38e717501c94cd8/
> >
> > The bisection was run with CONFIG_RANDOMIZE_BASE=y enabled, but
>
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
This patch-set clears all of the W=1 warnings currently residing
in drivers/video.
Lee Jones (31):
video: fbdev: core: fbmon: Add missing descrip
Also fix a formatting issue
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/core/fbmon.c:617: warning: Function parameter or member
'specs' not described in 'fb_create_modedb'
drivers/video/fbdev/core/fbmon.c:1103: warning: bad line:
Cc: James Simmons
Cc: Egbert Eich
Cc
If used, 'dac_type' is overwritten in the '#ifdef CONFIG_ATARI' clause.
It's also not used after the last assignment, so we'll rid that too.
Cc: Bartlomiej Zolnierkiewicz
Cc: Vaibhav Gupta
Cc: Alex Kern
Cc: "Eddie C. Dost"
Cc: Anthony Tong
Cc: dri-de...@lists.freedesktop.org
Cc: linux-fb...@
Fixes the following W=1 kernel build warning(s):
drivers/video/fbdev/riva/fbdev.c:485: warning: Function parameter or member
'data8' not described in 'rivafb_load_cursor_image'
drivers/video/fbdev/riva/fbdev.c:485: warning: Excess function parameter
'data' description in 'rivafb_load_cursor_im
Fixes the following W=1 kernel build warning(s):
drivers/video/of_display_timing.c:58: warning: Function parameter or member
'dt' not described in 'of_parse_display_timing'
Cc: Steffen Trumtrar
Cc: Sascha Hauer
Cc: dri-de...@lists.freedesktop.org
Cc: linux-fb...@vger.kernel.org
Signed-off-by:
401 - 500 of 1327 matches
Mail list logo