Le 03/02/2023 à 03:45, Nicholas Piggin a écrit :
> On Fri Feb 3, 2023 at 12:02 PM AEST, Benjamin Gray wrote:
>> On Fri, 2023-02-03 at 00:46 +0100, Erhard F. wrote:
>>> Happened during boot:
>>>
>>> [...]
>>> Creating 6 MTD partitions on "flash@0":
>>> 0x-0x0400 : "PNOR"
>>>
Le 07/02/2023 à 02:56, Benjamin Gray a écrit :
> patch_instruction() is designed for patching instructions in otherwise
> readonly memory. Other consumers also sometimes need to patch readonly
> memory, so have abused patch_instruction() for arbitrary data patches.
>
> This is a problem on
Correct spelling problems for Documentation/powerpc/ as reported
by codespell.
Signed-off-by: Randy Dunlap
Cc: Michael Ellerman
Cc: linuxppc-dev@lists.ozlabs.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/powerpc/kasan.txt |2 +-
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
fixes-test
branch HEAD: 2ea31e2e62bbc4d11c411eeb36f1b02841dbcab1 powerpc/64s/interrupt:
Fix interrupt exit race with security mitigation switch
elapsed time: 724m
configs tested: 2
configs skipped: 119
The
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
next-test
branch HEAD: 18e3525c5e7c6634f88857242a2e1997d5f065e8 integrity/powerpc:
Support loading keys from PLPKS
elapsed time: 722m
configs tested: 68
configs skipped: 2
The following configs have been built
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
next
branch HEAD: b505063910c134778202dfad9332dfcecb76bab3 powerpc/iommu: fix
memory leak with using debugfs_lookup()
elapsed time: 723m
configs tested: 2
configs skipped: 119
The following configs have been built
On Monday 23 January 2023 21:09:22 Pali Rohár wrote:
> On Monday 23 January 2023 14:32:36 Christophe Leroy wrote:
> > Le 22/01/2023 à 12:16, Pali Rohár a écrit :
> > > Hello! Do you have any comments for this patch series?
> >
> >
> > I think patches 1 and 2 could be a single patch.
>
> Well,
On Monday 26 December 2022 12:45:13 Pali Rohár wrote:
> Due to CPLD firmware bugs, set CPLD syscon-reboot priority level to 64
> (between rstcr and watchdog) to ensure that rstcr's global-utilities reset
> method which is preferred stay as default one, and to ensure that CPLD
> syscon-reboot is
> On 8 Feb 2023, at 11:23 pm, Christophe Leroy
> wrote:
>
>
>
> Le 08/02/2023 à 04:21, Rohan McLure a écrit :
>> KCSAN instruments calls to atomic builtins, and will in turn call these
>> builtins itself. As such, architectures supporting KCSAN must have
>> compiler support for these
On 08/02/2023 18:33, Andy Shevchenko wrote:
> From: Linus Walleij
>
> The file s3c64xx.c is including despite using no
> symbols from the file, however it needs it to implicitly bring in
> of_have_populated_dt() so include explicitly instead.
>
> Signed-off-by: Linus Walleij
> Signed-off-by:
On Wed, Feb 08, 2023 at 06:39:12PM +0100, Krzysztof Kozlowski wrote:
> On 08/02/2023 18:33, Andy Shevchenko wrote:
...
> It's not s3c24xx anymore, so subject prefix:
> ARM: s3c64xx:
Fixed locally, thanks.
--
With Best Regards,
Andy Shevchenko
On 08/02/2023 18:33, Andy Shevchenko wrote:
> From: Linus Walleij
>
> The file s3c64xx.c is including despite using no
> symbols from the file, however it needs it to implicitly bring in
> of_have_populated_dt() so include explicitly instead.
>
> Signed-off-by: Linus Walleij
> Signed-off-by:
There is a few things done:
- include only the headers we are direct user of
- when pointer is in use, provide a forward declaration
- add missing headers
- group generic headers and subsystem headers
- sort each group alphabetically
Signed-off-by: Andy Shevchenko
---
Do not imply that some of the generic headers may be always included.
Instead, include explicitly what we are direct user of.
While at it, split out the GPIO group of headers.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpio-reg.c | 12 ++--
1 file changed, 10 insertions(+), 2
There is no struct device_node pointers anywhere in the header,
drop unused forward declaration.
Signed-off-by: Andy Shevchenko
---
include/linux/gpio/driver.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
index
Do not imply that some of the generic headers may be always included.
Instead, include explicitly what we are direct user of.
While at it, drop unused linux/gpio.h and split out the GPIO group of
headers.
Signed-off-by: Andy Shevchenko
Reviewed-by: Geert Uytterhoeven
---
From: Arnd Bergmann
Almost all gpio drivers include linux/gpio/driver.h, and other
files should not rely on includes from this header.
Remove the indirect include from here and include the correct
headers directly from where they are used.
Reviewed-by: Andy Shevchenko
Signed-off-by: Arnd
From: Arnd Bergmann
gpio_set_debounce() only has a single user, which is trivially
converted to gpiod_set_debounce().
Signed-off-by: Arnd Bergmann
Reviewed-by: Linus Walleij
Reviewed-by: Andy Shevchenko
Signed-off-by: Andy Shevchenko
---
Documentation/driver-api/gpio/legacy.rst
For better maintenance group the forward declarations together.
Signed-off-by: Andy Shevchenko
---
include/linux/gpio/consumer.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/gpio/consumer.h b/include/linux/gpio/consumer.h
index a7eb8aa1e54c..5432e5d5fbfb
From: Arnd Bergmann
The arm and sh versions of this file are identical to the generic
versions and can just be removed.
The drivers that actually use the sh3 specific version also include
cpu/gpio.h directly, with the exception of magicpanelr2, which is
easily fixed. This leaves coldfire as the
The struct fwnode_handle pointer is used in both branches of ifdeffery,
no need to have a copy of the same in each of them, just make it global.
Signed-off-by: Andy Shevchenko
---
include/linux/gpio/consumer.h | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git
From: Linus Walleij
The test driver uses the gpiod consumer API so include the right
header. This may cause a problem with
struct of_device_id being implcitly pulled in by the legacy
header so include
explicitly as well.
While at it, drop explicit moduleparam.h (it's included with module.h)
These are some older patches Arnd did last year, rebased to
linux-next-20230208. On top there are Andy's patches regarding
similar topic. The series starts with Linus Walleij's patches.
The main goal is to remove some of the legacy bits of the gpiolib
interfaces, where the corner cases are easily
From: Linus Walleij
The file s3c64xx.c is including despite using no
symbols from the file, however it needs it to implicitly bring in
of_have_populated_dt() so include explicitly instead.
Signed-off-by: Linus Walleij
Signed-off-by: Andy Shevchenko
---
arch/arm/mach-s3c/s3c64xx.c | 2 +-
1
From: Arnd Bergmann
This is a rarely used feature that has nothing to do with the
client-side of_gpio.h.
Split it out with a separate header file and Kconfig option
so it can be removed on its own timeline aside from removing
the of_gpio consumer interfaces.
Reviewed-by: Andy Shevchenko
Do not imply that some of the generic headers may be always included.
Instead, include explicitly what we are direct user of.
While at it, split out the GPIO group of headers.
Signed-off-by: Andy Shevchenko
---
drivers/gpio/gpio-regmap.c | 12 +---
1 file changed, 9 insertions(+), 3
From: Arnd Bergmann
There are only a handful of users of gpio_export() and
related functions.
As these are just wrappers around the modern gpiod_export()
helper, remove the wrappers and open-code the gpio_to_desc
in all callers to shrink the legacy API.
Reviewed-by: Andy Shevchenko
From: Arnd Bergmann
Now that coldfire is the only user of a custom asm/gpio.h, it seems
better to remove this as well, and have the same interface everywhere.
For the gpio_get_value()/gpio_set_value()/gpio_to_irq(), gpio_cansleep()
functions, the custom version is only a micro-optimization to
From: Arnd Bergmann
The asm-generic/gpio.h file is now always included when
using gpiolib, so just move its contents into linux/gpio.h
with a few minor simplifications.
Signed-off-by: Arnd Bergmann
Reviewed-by: Linus Walleij
Reviewed-by: Andy Shevchenko
Signed-off-by: Andy Shevchenko
---
From: Linus Walleij
The legacy header was an all-inclusive header used
by drivers and consumers alike. After eliminating the last users
of the driver defines, we can drop the inclusion of the
header.
Signed-off-by: Linus Walleij
Signed-off-by: Andy Shevchenko
---
include/asm-generic/gpio.h
From: Linus Walleij
This is a GPIO driver so include and not
the legacy header. Switch a single call to the
legacy API and use as well.
Signed-off-by: Linus Walleij
Signed-off-by: Andy Shevchenko
---
arch/arm/plat-orion/gpio.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
On Tue, Feb 07, 2023 at 04:20:21PM +, Frank Li wrote:
> > Subject: Re: [External] : RE: [EXT] [PATCH v2 1/1] PCI: layerscape: Add EP
> > mode support for ls1028a
> >
> > { .compatible = "fsl,ls1046a-pcie-ep", .data = _ep_drvdata },
> > + { .compatible = "fsl,ls1028a-pcie-ep",
On Fri, 3 Feb 2023 10:42:30 +0100
Thomas Huth wrote:
> All kvm_arch_vm_ioctl() implementations now only deal with "int"
> types as return values, so we can change the return type of these
> functions to use "int" instead of "long".
>
> Signed-off-by: Thomas Huth
Acked-by: Claudio Imbrenda
On Wed, Feb 08, 2023 at 03:12:06PM +0100, David Hildenbrand wrote:
> On 07.02.23 01:32, Mark Brown wrote:
> > Today's -next (and at least back to Friday, older logs are unclear - I
> > only noticed -next issues today) fails to NFS boot on an AT91SAM9G20-EK
> > (an old ARMv5 platform) with
Michael Ellerman writes:
> Nathan Lynch via B4 Submission Endpoint
> writes:
>> From: Nathan Lynch
>>
>> Users of rtas_token() supply a string argument that can't be validated
>> at build time. A typo or misspelling has to be caught by inspection or
>> by observing wrong behavior at runtime.
>>
On Wed, Feb 8, 2023 at 3:51 PM Andy Shevchenko
wrote:
> On Wed, Feb 08, 2023 at 12:55:06AM +0200, Andy Shevchenko wrote:
> > On Tue, Feb 07, 2023 at 03:55:23PM +0100, Linus Walleij wrote:
> > > On Tue, Feb 7, 2023 at 3:29 PM Andy Shevchenko
> > > wrote:
> > >
> > > > From: Arnd Bergmann
> > > >
On Wed, Feb 08, 2023 at 12:55:06AM +0200, Andy Shevchenko wrote:
> On Tue, Feb 07, 2023 at 03:55:23PM +0100, Linus Walleij wrote:
> > On Tue, Feb 7, 2023 at 3:29 PM Andy Shevchenko
> > wrote:
> >
> > > From: Arnd Bergmann
> > >
> > > Almost all gpio drivers include linux/gpio/driver.h, and
Michael Ellerman writes:
> Nathan Lynch via B4 Submission Endpoint
> writes:
>> diff --git a/arch/powerpc/include/asm/rtas-work-area.h
>> b/arch/powerpc/include/asm/rtas-work-area.h
>> new file mode 100644
>> index ..76ccb039cc37
>> --- /dev/null
>> +++
On 07.02.23 01:32, Mark Brown wrote:
On Fri, Jan 13, 2023 at 06:10:04PM +0100, David Hildenbrand wrote:
Let's support __HAVE_ARCH_PTE_SWP_EXCLUSIVE by stealing one bit from the
offset. This reduces the maximum swap space per file to 64 GiB (was 128
GiB).
While at it drop the PTE_TYPE_FAULT
On Wed, Feb 08, 2023 at 08:09:00PM +0800, Yin, Fengwei wrote:
>
>
> On 2/8/2023 7:23 PM, Alexandre Ghiti wrote:
> > Hi Matthew,
> >
> > On 2/7/23 21:27, Matthew Wilcox wrote:
> >> On Thu, Feb 02, 2023 at 09:14:23PM +, Matthew Wilcox wrote:
> >>> For those of you not subscribed, linux-mm is
Michael Ellerman writes:
> Nathan Lynch via B4 Submission Endpoint
> writes:
>> From: Nathan Lynch
>>
>> The core RTAS support code and its clients perform two types of lookup
>> for RTAS firmware function information.
>>
> ...
>> diff --git a/arch/powerpc/include/asm/rtas.h
>>
Michael Ellerman writes:
> Nathan Lynch via B4 Submission Endpoint
> writes:
>> From: Nathan Lynch
>>
>> Some code that runs early in boot calls RTAS functions that can return
>> -2 or 990x statuses, which mean the caller should retry. An example is
>> pSeries_cmo_feature_init(), which invokes
On 2/8/2023 7:23 PM, Alexandre Ghiti wrote:
> Hi Matthew,
>
> On 2/7/23 21:27, Matthew Wilcox wrote:
>> On Thu, Feb 02, 2023 at 09:14:23PM +, Matthew Wilcox wrote:
>>> For those of you not subscribed, linux-mm is currently discussing
>>> how best to handle page faults on large folios. I
Hi Andy,
Thanks for your patch!
On Tue, Feb 7, 2023 at 3:29 PM Andy Shevchenko
wrote:
> Do not imply that some of the generic headers may be always included.
> Instead, include explicitly what we are direct user of.
That applies only to the addition of #include ...
Please also describe the
On 07. 02. 23 20:19, Uwe Kleine-König wrote:
Hello,
while checking in which cases hda_tegra_remove() can return a non-zero value, I
found that actually cannot happen. This series makes the involved functions
return void to make this obvious.
This is a preparation for making
On Tue, 07 Feb 2023 20:19:04 +0100,
Uwe Kleine-König wrote:
>
> Hello,
>
> while checking in which cases hda_tegra_remove() can return a non-zero value,
> I
> found that actually cannot happen. This series makes the involved functions
> return void to make this obvious.
>
> This is a
Le 08/02/2023 à 04:22, Rohan McLure a écrit :
> Enable HAVE_ARCH_KCSAN on all powerpc platforms, permitting use of the
> kernel concurrency sanitiser through the CONFIG_KCSAN_* kconfig options.
> KCSAN requires compiler builtins __atomic_* 64-bit values, and so only
> report support on PPC64.
Le 08/02/2023 à 04:21, Rohan McLure a écrit :
> KCSAN instruments calls to atomic builtins, and will in turn call these
> builtins itself. As such, architectures supporting KCSAN must have
> compiler support for these atomic primitives.
>
> Since 32-bit systems are unlikely to have 64-bit
On 08/02/2023 12.51, Steven Price wrote:
On 08/02/2023 08:49, Cornelia Huck wrote:
On Wed, Feb 08 2023, Gavin Shan wrote:
On 2/7/23 9:09 PM, Thomas Huth wrote:
Oh, drat, I thought I had checked all return statements ... this must have
fallen through the cracks, sorry!
Anyway, this is
Nathan Lynch via B4 Submission Endpoint
writes:
> From: Nathan Lynch
>
> Users of rtas_token() supply a string argument that can't be validated
> at build time. A typo or misspelling has to be caught by inspection or
> by observing wrong behavior at runtime.
>
> Since the core RTAS code now has
On 08/02/2023 08:49, Cornelia Huck wrote:
> On Wed, Feb 08 2023, Gavin Shan wrote:
>
>> On 2/7/23 9:09 PM, Thomas Huth wrote:
>>> Oh, drat, I thought I had checked all return statements ... this must have
>>> fallen through the cracks, sorry!
>>>
>>> Anyway, this is already a problem now: The
Nathan Lynch via B4 Submission Endpoint
writes:
> diff --git a/arch/powerpc/include/asm/rtas-work-area.h
> b/arch/powerpc/include/asm/rtas-work-area.h
> new file mode 100644
> index ..76ccb039cc37
> --- /dev/null
> +++ b/arch/powerpc/include/asm/rtas-work-area.h
> @@ -0,0 +1,45 @@
>
Nathan Lynch via B4 Submission Endpoint
writes:
> From: Nathan Lynch
>
> The core RTAS support code and its clients perform two types of lookup
> for RTAS firmware function information.
>
...
> diff --git a/arch/powerpc/include/asm/rtas.h b/arch/powerpc/include/asm/rtas.h
> index
On Tue, Feb 07, 2023 at 08:19:07PM +0100, Uwe Kleine-König wrote:
> The function returns 0 unconditionally. Make it return void instead and
> simplify all callers accordingly.
>
> Signed-off-by: Uwe Kleine-König
> ---
> include/sound/core.h | 2 +-
> sound/core/init.c | 6 ++
>
Hi Matthew,
On 2/7/23 21:27, Matthew Wilcox wrote:
On Thu, Feb 02, 2023 at 09:14:23PM +, Matthew Wilcox wrote:
For those of you not subscribed, linux-mm is currently discussing
how best to handle page faults on large folios. I simply made it work
when adding large folio support. Now Yin
Nathan Lynch via B4 Submission Endpoint
writes:
> From: Nathan Lynch
>
> Some code that runs early in boot calls RTAS functions that can return
> -2 or 990x statuses, which mean the caller should retry. An example is
> pSeries_cmo_feature_init(), which invokes ibm,get-system-parameter but
>
On Wed, 8 Feb 2023 at 04:23, Rohan McLure wrote:
>
> Enable HAVE_ARCH_KCSAN on all powerpc platforms, permitting use of the
> kernel concurrency sanitiser through the CONFIG_KCSAN_* kconfig options.
> KCSAN requires compiler builtins __atomic_* 64-bit values, and so only
> report support on
Hello,
On Wed, Feb 08, 2023 at 05:33:48PM +0900, Takashi Sakamoto wrote:
> On Tue, Feb 07, 2023 at 08:19:04PM +0100, Uwe Kleine-König wrote:
> > Hello,
> >
> > while checking in which cases hda_tegra_remove() can return a non-zero
> > value, I
> > found that actually cannot happen. This series
On Wed, Feb 08 2023, Gavin Shan wrote:
> On 2/7/23 9:09 PM, Thomas Huth wrote:
>> Oh, drat, I thought I had checked all return statements ... this must have
>> fallen through the cracks, sorry!
>>
>> Anyway, this is already a problem now: The function is called from
>> kvm_arch_vm_ioctl()
Hi,
On Tue, Feb 07, 2023 at 08:19:04PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> while checking in which cases hda_tegra_remove() can return a non-zero value,
> I
> found that actually cannot happen. This series makes the involved functions
> return void to make this obvious.
>
> This is a
60 matches
Mail list logo
