On Fri, Sep 09, 2022 at 05:55:14AM +,
Christophe Leroy wrote:
>
>
> Le 09/09/2022 à 01:25, isaku.yamah...@intel.com a écrit :
> > [Vous ne recevez pas souvent de courriers de isaku.yamah...@intel.com.
> > Découvrez pourquoi ceci est important à
> > https://aka.ms/LearnAboutSenderIdentific
randconfig-a005
i386 randconfig-a006
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
riscvrandconfig-r042-20220909
hexagon randconfig-r041-20220909
hexagon
randconfig-r045-20220908
x86_64randconfig-a003
riscvrandconfig-r042-20220909
hexagon randconfig-r041-20220909
hexagon randconfig-r045-20220909
s390 randconfig-r044-20220909
x86_64randconfig-k001
clang tested configs:
riscvrandconfig-r042-20220909
hexagon randconfig-r041-20220909
hexagon randconfig-r045-20220909
s390 randconfig-r044-20220909
i386 randconfig-a002
i386 randconfig-a006
The pull request you sent on Fri, 09 Sep 2022 22:36:24 +1000:
> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
> tags/powerpc-6.0-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2fc1171d34deff70bf3a8338adab8ce46138aae3
Thank you!
--
Deet-doot-do
Hi,
Here's a preview of what I'm planning to discuss at the LPC toolchains
microconference. Feel free to start the discussion early :-)
This is a proposal for some new minor GCC/Clang features which would
help objtool greatly.
Background
--
Objtool is a kernel-specific tool which reve
Since commit e641eb03ab2b0 ("powerpc: Fix up the kdump base cap to
128M") memory for kdump kernel has been reserved at an offset of
128MB. This held up well for a long time before running into boot
failure on LPARs having a lot of cores. Commit 7c5ed82b800d8
("powerpc: Set crashkernel offset to mid
Le 09/09/2022 à 18:02, Suren Baghdasaryan a écrit :
> On Fri, Sep 9, 2022 at 8:19 AM Laurent Dufour wrote:
>>
>> Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
>>> call_rcu() can take a long time when callback offloading is enabled.
>>> Its use in the vm_area_free can cause regressions in the
Le 09/09/2022 à 02:51, Suren Baghdasaryan a écrit :
> On Tue, Sep 6, 2022 at 8:35 AM Laurent Dufour wrote:
>>
>> Le 01/09/2022 à 19:34, Suren Baghdasaryan a écrit :
>>> vma_adjust modifies a VMA and possibly its neighbors. Mark them as locked
>>> before making the modifications.
>>>
>>> Signed-off
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> call_rcu() can take a long time when callback offloading is enabled.
> Its use in the vm_area_free can cause regressions in the exit path when
> multiple VMAs are being freed. To minimize that impact, place VMAs into
> a list and free them in gr
Hi Vinod/Kishon,
On 9/2/22 5:37 PM, Sean Anderson wrote:
> This adds support for the Lynx 10G SerDes found on the QorIQ T-series
> and Layerscape series. Due to limited time and hardware, only support
> for the LS1046ARDB is added in this initial series. There is a sketch
> for LS1088ARDB support,
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Introduce find_and_lock_anon_vma function to lookup and lock an anonymous
> VMA during page fault handling. When VMA is not found, can't be locked
> or changes after being locked, the function returns NULL. The lookup is
> performed under RCU pr
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Add a new CONFIG_PER_VMA_LOCK_STATS config option to dump extra
> statistics about handling page fault under VMA lock.
>
Why not making this a default when per VMA lock are enabled?
> Signed-off-by: Suren Baghdasaryan
> ---
> include/linux/
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Due to the possibility of do_swap_page dropping mmap_lock, abort fault
> handling under VMA lock and retry holding mmap_lock. This can be handled
> more gracefully in the future.
>
> Signed-off-by: Suren Baghdasaryan
Reviewed-by: Laurent Dufo
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Add a new flag to distinguish page faults handled under protection of
> per-vma lock.
>
> Signed-off-by: Suren Baghdasaryan
FWIW,
Reviewed-by: Laurent Dufour
> ---
> include/linux/mm.h | 3 ++-
> include/linux/mm_types.h | 1 +
> 2
Setting DEC to maximum at the start of the timer interrupt is not
necessary and can be avoided for performance when MSR[EE] is not
enabled during the handler as explained in commit 0faf20a1ad16
("powerpc/64s/interrupt: Don't enable MSR[EE] in irq handlers unless
perf is in use"), where this change
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Pagefault handlers might need to fire MMU notifications while a new
> notifier is being registered. Modify mm_take_all_locks to mark all VMAs
> as locked and prevent this race with fault handlers that would hold VMA
> locks.
>
> Signed-off-by:
Hi Leonardo,
(restoring the list to the cc, hope that's ok)
Leonardo Brás writes:
> On Wed, 2022-09-07 at 17:01 -0500, Nathan Lynch wrote:
>> At the time this was submitted by Leonardo, I confirmed -- or thought
>> I had confirmed -- with PowerVM partition firmware development that
>> the follow
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Assert there are no holders of VMA lock for reading when it is about to be
> destroyed.
>
> Signed-off-by: Suren Baghdasaryan
> ---
> include/linux/mm.h | 8
> kernel/fork.c | 2 ++
> 2 files changed, 10 insertions(+)
>
> diff
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> While unmapping VMAs, adjacent VMAs might be able to grow into the area
> being unmapped. In such cases mark adjacent VMAs as locked to prevent
> this growth.
>
> Signed-off-by: Suren Baghdasaryan
> ---
> mm/mmap.c | 8 ++--
> 1 file chan
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> Mark VMAs as locked before isolating them and clear their tree node so
> that isolated VMAs are easily identifiable. In the later patches page
> fault handlers will try locking the found VMA and will check whether
> the VMA was isolated. Locking
Le 09/09/2022 à 01:57, Suren Baghdasaryan a écrit :
> On Tue, Sep 6, 2022 at 7:38 AM Laurent Dufour wrote:
>>
>> Le 01/09/2022 à 19:34, Suren Baghdasaryan a écrit :
>>> Protect VMAs from concurrent page fault handler while performing
>>> copy_page_range for VMAs having VM_WIPEONFORK flag set.
>>
>
Christophe Leroy writes:
> Le 09/09/2022 à 07:50, Michael Ellerman a écrit :
>> Hi Christophe,
>>
>> Thanks for trying to clean up this tangled mess.
>>
>> Christophe Leroy writes:
>>> The only 64-bit Book3E CPUs we support is the e500mc.
>>
>> AFAIK the e500mc is 32-bit?
>
> Yes it seems.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull another powerpc fix for 6.0:
The following changes since commit 6cf07810e9ef8535d60160d13bf0fd05f2af38e7:
powerpc/papr_scm: Ensure rc is always initialized in papr_scm_pmu_register()
(2022-09-02 18:55:11 +1000)
are availa
On Wed, 31 Aug 2022 08:47:06 +0800, Jilin Yuan wrote:
> Delete the redundant word 'set'.
>
>
Applied to powerpc/next.
[1/1] powerpc/xive: fix repeated words in comments
https://git.kernel.org/powerpc/c/9b135eef0787813ad073aaeb9ff80ab57bc63e69
cheers
On Wed, 31 Aug 2022 08:49:14 +0800, Jilin Yuan wrote:
> Delete the redundant word 'the'.
>
>
Applied to powerpc/next.
[1/1] powerpc/vas: fix repeated words in comments
https://git.kernel.org/powerpc/c/0d4bb5e45aa698f2f357b1424b842bebe13b1c8b
cheers
On Sat, 18 Jun 2022 12:10:42 +0800, Liang He wrote:
> In xx_init_xx(), of_find_node_by_type() will return a node pointer
> with refcount incremented. We should use of_node_put() when it is
> not used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc: embedded6xx: Fix refcount leak bugs
On Wed, 31 Aug 2022 08:51:09 +0800, Jilin Yuan wrote:
> Delete the redundant word 'the'.
>
>
Applied to powerpc/next.
[1/1] powerpc/mobility: fix repeated words in comments
https://git.kernel.org/powerpc/c/4c73cadcdc64b53248bca85baa8a19e7384701ec
cheers
On Mon, 4 Jul 2022 22:52:33 +0800, Liang He wrote:
> In fsl_setup_msi_irqs(), we should use of_node_put() for the
> refernece 'np' returned by of_parse_phandle() which increases
> the refcount.
>
>
Applied to powerpc/next.
[1/1] powerpc: sysdev: fsl_msi: Add missing of_node_put() for of_parse_p
On Fri, 17 Jun 2022 18:50:11 +0800, Liang He wrote:
> In gpio_halt_probe(), of_find_matching_node() will return a node
> pointer with refcount incremented. We should use of_node_put() in
> fail path or when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc:85xx: Add missing of_
On Mon, 20 Jun 2022 21:25:53 +0800, Liang He wrote:
> In these driver init functions, there are two kinds of errors:
>
> (1) missing of_put_node() for of_find_compatible_node()'s returned
> pointer (refcount incremented) in fail path or when it is not
> used anymore.
> (2) missing of_put_
On Mon, 20 Jun 2022 21:02:21 +0800, Liang He wrote:
> We need add corresponding of_node_put() to keep refcount balance
> in sysdev.
>
>
Applied to powerpc/next.
[1/1] powerpc/sysdev: Fix refcount leak bugs
https://git.kernel.org/powerpc/c/3d31adc47edb6d0cef122a41fba1b639db5d1c37
cheers
On Fri, 1 Jul 2022 22:49:48 +0800, Liang He wrote:
> There are several bugs as following:
>
> (1) In cbe_get_be_node(), we should hold the reference returned by
> of_find_xxx and of_get_xxx OF APIs and use it to call of_node_put
> (2) In cbe_fill_regs_map(), we should same as above
> (3) In cb
On Tue, 21 Jun 2022 19:17:01 +0800, Liang He wrote:
> In pseries_cpuhp_cache_use_count() and pseries_cpuhp_detach_nodes(),
> we need carefully hold the reference returned by
> of_find_next_cache_node() and use it to call of_node_put() to keep
> refcount balance.
>
>
Applied to powerpc/next.
[1/
On Mon, 20 Jun 2022 23:05:18 +0800, Liang He wrote:
> In smp_core99_setup(), we need to add of_node_put() to keep refcount
> balance.
>
>
Applied to powerpc/next.
[1/1] powerpc/powermac: Fix refcount leak bug
https://git.kernel.org/powerpc/c/a3a4c10aef88a80ba1b230a7bf63ea381cc5116e
cheer
On Sun, 19 Jun 2022 15:40:16 +0800, Liang He wrote:
> In ibmebus_match_path(), we should use of_node_put() to keep
> refcount balance.
>
>
Applied to powerpc/next.
[1/1] powerpc: pseries: Fix refcount bug in ibmebus
https://git.kernel.org/powerpc/c/1c754b49c002a965004b6a96d158f7ce554eb977
On Sat, 16 Jul 2022 15:43:44 +0800, Liang He wrote:
> During the iteration of for_each_child_of_node(), we need to call
> of_node_put() for the old references stored in to 'ch_def' and 'ch_a'
> as their refcounters have been increased in last iteration.
>
>
Applied to powerpc/next.
[1/1] powerp
On Sat, 16 Jul 2022 15:31:11 +0800, Liang He wrote:
> We should call of_node_put() for the reference 'gparent' escaped
> out of the for_each_child_of_node() as it has increased the refcount.
>
>
Applied to powerpc/next.
[1/1] powerpc/powermac/pfunc_base: Fix refcount leak bug in
macio_gpio_ini
On Sat, 16 Jul 2022 15:07:58 +0800, Liang He wrote:
> We should call of_node_put() for the reference 'parent' returned by
> of_get_parent() which has increased the refcount.
>
>
Applied to powerpc/next.
[1/1] powerpc/powermac/low_i2c: Fix refcount leak bug in kw_i2c_probe()
https://git.ke
On Fri, 1 Jul 2022 21:17:50 +0800, Liang He wrote:
> In pci_add_device_node_info(), we should use of_node_put() for the
> reference 'parent' returned by of_get_parent() to keep refcount
> balance.
>
>
Applied to powerpc/next.
[1/1] powerpc: kernel: pci_dn: Add missing of_node_put() for of_get_x
On Sat, 16 Jul 2022 14:54:12 +0800, Liang He wrote:
> In probe_one_macio(), we should call of_node_put() for the refernece
> 'node' escaped out of the for_each_node_by_name() which has increased
> its refcount. While the 'node' will finally escaped into a global
> reference, we should still call of
On Sun, 19 Jun 2022 15:08:11 +0800, Liang He wrote:
> In find_legacy_serial_ports(), of_find_node_by_path() will return
> a node pointer with refcount incremented. We should use of_node_put()
> when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc: kernel: Fix refcount bug in
On Thu, 16 Jun 2022 22:40:07 +0800, Liang He wrote:
> In media5200_init_irq(), of_find_compatible_node() will return a
> node pointer with refcount incremented. We should use of_node_put()
> in fail path or when it is not used anymore.
>
> Don't worry about 'fpga_np==NULL' as of_node_put() can cor
On Sat, 18 Jun 2022 15:13:53 +0800, Liang He wrote:
> In update_events_in_group(), of_find_node_by_phandle() will return
> a node pointer with refcount incremented. We should use of_node_put()
> in fail path or when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc: perf: Fix r
On Fri, 17 Jun 2022 20:40:45 +0800, Liang He wrote:
> In maple_get_boot_time(), of_find_compatible_node() will return
> a node pointer with refcount incremented. We should use of_node_put()
> in fail path or when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc: maple: Fix ref
On Sat, 2 Jul 2022 10:29:36 +0800, Liang He wrote:
> In pcibios_alloc_controller(), 'phb' is allocated and escaped into
> global 'hose_list'. So we should call of_node_get() when a new reference
> created into 'phb->dn'. And when phb is freed, we should call
> of_node_put() on it.
>
> NOTE: This f
On Wed, 20 Jul 2022 20:45:57 +0800, Liang He wrote:
> In fsl_pci_assign_primary(), we should remove the of_node_put()
> when breaking out of the for_each_matching_node() as the 'np'
> is escaped out by global 'fsl_pci_primary'.
>
>
Applied to powerpc/next.
[1/1] powerpc/fsl_pci: Remove of_node_
On Mon, 20 Jun 2022 14:59:04 +0800, Liang He wrote:
> In ls_uarts_init(), we need to add a of_node_put() to keep refcount
> balance.
>
>
Applied to powerpc/next.
[1/1] powerpc/embedded6xx/ls_uart: Add missing of_node_put()
https://git.kernel.org/powerpc/c/cd772e659da0ad67f19f022f65449e14e
On Sun, 19 Jun 2022 15:23:35 +0800, Liang He wrote:
> We should use of_node_put() for of_find_node_by_path() and
> of_find_node_by_phandle() to keep refcount balance.
>
>
Applied to powerpc/next.
[1/1] powerpc/cell: Fix refcount leak bugs
https://git.kernel.org/powerpc/c/d9e1c6104d87d4027
On Sat, 18 Jun 2022 10:49:30 +0800, Liang He wrote:
> In init_ioports(), of_find_node_by_name() will return a node pointer
> with refcount incremented. We should use of_node_put() when it is not
> used anymore.
>
>
Applied to powerpc/next.
[1/1] powerpc: 8xx: Fix refcount leak bug in tqm8xx_set
On Fri, 1 Jul 2022 22:01:19 +0800, Liang He wrote:
> for_each_node_by_type() will automatically increase and decrease
> the refcount during the iteration. However, there is a reference
> escaped into global 'fsl_pci_primary' and we need to handle it.
>
>
Applied to powerpc/next.
[1/1] powerpc:
On Tue, 21 Jun 2022 16:09:32 +0800, Liang He wrote:
> In mpc832x_spi_init(), we should hold the reference returned by
> of_find_compatible_node() and use it to call of_node_put() for
> refcount balance.
>
>
Applied to powerpc/next.
[1/1] powerpc/83xx: Hold the reference returned by of_find_comp
On Tue, 21 Jun 2022 16:03:49 +0800, Liang He wrote:
> In mpc5121_clk_provide_migration_support(), we need to hold the
> reference returned by of_find_compatible_node() and use it to call
> of_node_put for refcount balance.
>
>
Applied to powerpc/next.
[1/1] powerpc/512x: Hold the reference retu
On Fri, 1 Jul 2022 21:31:26 +0800, Liang He wrote:
> In ppc47x_init_irq(), we need to call of_node_put() when there is
> a break during the iteration of for_each_node_with_property() which
> will automatically increase and decrease the refcount.
>
>
Applied to powerpc/next.
[1/1] powerpc: 44x:
On Wed, 22 Jun 2022 14:16:52 +0800, Liang He wrote:
> We need a of_node_get() for of_find_compatible_node() to keep refcount
> balance.
>
>
Applied to powerpc/next.
[1/1] macintosh: Add missing of_node_get() in do_attach()
https://git.kernel.org/powerpc/c/d208d8c2cde513b94ae3b8b9766365607
On Thu, 16 Jun 2022 21:29:22 +0800, Liang He wrote:
> In ksi8560_setup_arch(), of_find_compatible_node() will return a
> node pointer with refcount incremented. We should use of_node_put()
> when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] arch: powerpc: platforms: 85xx: Fix refc
On Wed, 15 Jun 2022 22:37:03 +0800, Liang He wrote:
> In mpc5121_clk_init(), of_find_compatible_node() will return a
> node pointer with refcount incremented. We should use of_node_put()
> when it is not used anymore.
>
>
Applied to powerpc/next.
[1/1] arch: powerpc: platforms: 512x: Add missin
On Sat, 27 Aug 2022 16:39:46 +1000, Russell Currey wrote:
> find_i2c_driver() contained the last usage of strlcpy() in arch/powerpc.
> The return value was used to check if strlen(src) >= n, for which
> strscpy() returns -E2BIG.
>
>
Applied to powerpc/next.
[1/1] powerpc/pasemi: Use strscpy ins
On Fri, 2 Sep 2022 18:53:12 +1000, Nicholas Piggin wrote:
> pseries provides stolen time accounting when VIRT_CPU_ACCOUNTING_NATIVE
> is selected, but not when VIRT_CPU_ACCOUNTING_GEN is. We like GEN
> because it's less code in arch/powerpc, allows full nohz, and distros
> have moved to it, so this
On Wed, 31 Aug 2022 08:20:15 -0700, Nathan Chancellor wrote:
> When building with a recent version of clang, there are a couple of
> errors around the call to module_init():
>
> arch/powerpc/math-emu/math_efp.c:927:1: error: type specifier missing,
> defaults to 'int'; ISO C99 and later do not
On Thu, 1 Sep 2022 12:02:15 +1000, Michael Ellerman wrote:
> Systems using the hash MMU with a 4K page size don't support 4PB address
> space, so skip the test because the bug it tests for can't be triggered.
>
>
Applied to powerpc/next.
[1/1] selftests/powerpc: Skip 4PB test on 4K PAGE_SIZE sy
On Thu, 1 Sep 2022 11:42:53 +1000, Michael Ellerman wrote:
> My commit to add PAPR_SCM to pseries_defconfig failed to add the
> required dependencies, meaning the driver doesn't get built.
>
> Add the required LIBNVDIMM=m.
>
>
Applied to powerpc/next.
[1/1] powerpc/configs: Properly enable PAP
On Wed, 31 Aug 2022 11:32:07 +0200, Christophe Leroy wrote:
> A comment about the reservation of gigantic pages was left in MMU_init()
> after commit 79cc38ded1e1 ("powerpc/mm/hugetlb: Add support for
> reserving gigantic huge pages via kernel command line")
>
> Remove it.
>
>
> [...]
Applied t
On Fri, 2 Sep 2022 17:25:24 +0200, Christophe Leroy wrote:
> With recent binutils, the following warning appears:
>
> VDSO32L arch/powerpc/kernel/vdso/vdso32.so.dbg
> /opt/gcc-12.2.0-nolibc/powerpc64-linux/bin/../lib/gcc/powerpc64-linux/12.2.0/../../../../powerpc64-linux/bin/ld:
> warning: arch
On Fri, 2 Sep 2022 18:00:08 +0200, Christophe Leroy wrote:
> From: Nathan Chancellor
>
> When building with a recent version of clang, there are a couple of
> errors around the call to module_init():
>
> arch/powerpc/math-emu/math_efp.c:927:1: error: type specifier missing,
> defaults to 'int
On Wed, 7 Sep 2022 08:12:54 +0200, Christophe Leroy wrote:
> When building with W=1 you get:
>
> arch/powerpc/math-emu/fre.c:6:5: error: no previous prototype for 'fre'
> [-Werror=missing-prototypes]
> arch/powerpc/math-emu/fsqrt.c:11:1: error: no previous prototype for
> 'fsqrt' [-W
On Fri, Sep 9, 2022, at 1:19 PM, Christophe Leroy wrote:
> Le 09/09/2022 à 13:09, Arnd Bergmann a écrit :
>> On Fri, Sep 9, 2022, at 11:03 AM, Lukas Bulwahn wrote:
>>
>> I don't see a single powerpc machine that creates a
>> name="pata_platform" platform_device. I suspect this was
>> only needed
Le 09/09/2022 à 13:09, Arnd Bergmann a écrit :
> On Fri, Sep 9, 2022, at 11:03 AM, Lukas Bulwahn wrote:
>> Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
>> PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
>> that all architectures simply select this config
On Fri, Sep 9, 2022, at 11:03 AM, Lukas Bulwahn wrote:
> Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
> PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
> that all architectures simply select this config when the architecture
> supports using the PATA_PLATF
On Fri, Sep 9, 2022 at 1:09 PM Arnd Bergmann wrote:
>
> On Fri, Sep 9, 2022, at 11:03 AM, Lukas Bulwahn wrote:
> > Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
> > PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
> > that all architectures simply select th
On Wed, 7 Sep 2022 16:50:38 +1000, Michael Ellerman wrote:
> As reported[1] by Nathan, the recently added plpks driver will crash if
> it's built into the kernel and booted on a non-pseries machine, eg
> powernv:
>
> kernel BUG at arch/powerpc/kernel/syscall.c:39!
> Oops: Exception in kernel m
Le 01/09/2022 à 19:35, Suren Baghdasaryan a écrit :
> free_pgtables and unmap_page_range functions can be called with mmap_lock
> held for write (e.g. in mmap_region), held for read (e.g in
> madvise_pageout) or not held at all (e.g in madvise_remove might
> drop mmap_lock before calling vfs_falloc
> > init/Kconfig | 8
> > 1 file changed, 8 deletions(-)
> >
> > diff --git a/init/Kconfig b/init/Kconfig
> > index 9e3fd79b089c..d7429e0b8cae 100644
> > --- a/init/Kconfig
> > +++ b/init/Kconfig
> > @@ -1818,14 +1818,6 @@ config DEBUG_RSEQ
> >
> > If unsure, say N.
> >
> > -con
On Fri, Sep 9, 2022 at 11:04 AM Lukas Bulwahn wrote:
>
> Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
> PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
> that all architectures simply select this config when the architecture
> supports using the PATA_PLAT
On Fri, Sep 9, 2022 at 10:55 AM Lukas Bulwahn wrote:
>
> Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
> PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
> that all architectures simply select this config when the architecture
> supports using the PATA_PLAT
On Fri, Sep 02, 2022 at 07:30:55AM +, cgel@gmail.com wrote:
> From: ye xingchen
>
> Return the value set_msg_len() directly instead of storing it in another
> redundant variable.
>
> Reported-by: Zeal Robot
> Signed-off-by: ye xingchen
> ---
> drivers/crypto/nx/nx-aes-ccm.c | 5 +
+ linuxppc-dev
Le 08/09/2022 à 12:43, Lukas Bulwahn a écrit :
> Commit 6a108a14fa35 ("kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT")
> introduces CONFIG_EXPERT to carry the previous intent of CONFIG_EMBEDDED
> and just gives that intent a much better name. That has been clearly a good
> and lo
Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
that all architectures simply select this config when the architecture
supports using the PATA_PLATFORM driver.
This is properly implemented already for all archi
Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
that all architectures simply select this config when the architecture
supports using the PATA_PLATFORM driver.
This is properly implemented already for all archi
Commit cc18e0fea790 ("LIBATA: Add HAVE_PATA_PLATFORM to select
PATA_PLATFORM driver") introduces config HAVE_PATA_PLATFORM, and expects
that all architectures simply select this config when the architecture
supports using the PATA_PLATFORM driver.
This is properly implemented already for all archi
80 matches
Mail list logo
