* [GIT PULL] Pin control fixes for v6.7 minus one patch
@ 2023-11-29 15:18 Linus Walleij
2023-11-29 15:48 ` Linus Torvalds
0 siblings, 1 reply; 3+ messages in thread
From: Linus Walleij @ 2023-11-29 15:18 UTC (permalink / raw)
To: Linus Torvalds
Cc: open list:GPIO SUBSYSTEM, linux-kernel, Maria Yu, Charles Keepax
Hi Linus,
Here is an updated tag on a branch where the only change
is to drop the locking READ_ONCE() patch until we know
more about what is going on here.
Remains: driver fixes.
Some details on the fixes are in the tag.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
tags/pinctrl-v6.7-3
for you to fetch changes up to 650d240056059296168b24ba47e76bafa37c0646:
dt-bindings: pinctrl: s32g2: change a maintainer email address
(2023-11-29 16:11:52 +0100)
----------------------------------------------------------------
Some pin control fixes for the v6.7 cycle:
- Check devm_kcalloc() return value and an array bounds in the STM32
driver.
- Fix an exotic string truncation issue in the s32cc driver, found
by the kernel test robot (impressive!)
- Fix an undocumented struct member in the cy8c95x0 driver.
- Fix a symbol overlap with MIPS in the Lochnagar driver, MIPS
defines a global symbol "RST" which is a bit too generic and
collide with stuff. OK this one should be renamed too, we will
fix that as well.
- Fix erroneous branch taking in the Realtek driver.
- Fix the mail address in MAINTAINERS for the s32g2 driver.
----------------------------------------------------------------
Antonio Borneo (1):
pinctrl: stm32: fix array read out of bound
Charles Keepax (1):
pinctrl: lochnagar: Don't build on MIPS
Chen Ni (1):
pinctrl: stm32: Add check for devm_kcalloc
Chester Lin (2):
pinctrl: s32cc: Avoid possible string truncation
dt-bindings: pinctrl: s32g2: change a maintainer email address
Linus Walleij (1):
pinctrl: cy8c95x0: Fix doc warning
Tzuyi Chang (1):
pinctrl: realtek: Fix logical error when finding descriptor
.../bindings/pinctrl/nxp,s32g2-siul2-pinctrl.yaml | 2 +-
drivers/pinctrl/cirrus/Kconfig | 3 ++-
drivers/pinctrl/nxp/pinctrl-s32cc.c | 4 ++--
drivers/pinctrl/pinctrl-cy8c95x0.c | 1 +
drivers/pinctrl/realtek/pinctrl-rtd.c | 4 ++--
drivers/pinctrl/stm32/pinctrl-stm32.c | 13 ++++++++++---
6 files changed, 18 insertions(+), 9 deletions(-)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] Pin control fixes for v6.7 minus one patch
2023-11-29 15:18 [GIT PULL] Pin control fixes for v6.7 minus one patch Linus Walleij
@ 2023-11-29 15:48 ` Linus Torvalds
2023-11-29 21:43 ` Linus Walleij
0 siblings, 1 reply; 3+ messages in thread
From: Linus Torvalds @ 2023-11-29 15:48 UTC (permalink / raw)
To: Linus Walleij
Cc: open list:GPIO SUBSYSTEM, linux-kernel, Maria Yu, Charles Keepax
On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@linaro.org> wrote:
>
> Here is an updated tag on a branch where the only change
> is to drop the locking READ_ONCE() patch until we know
> more about what is going on here.
Bah. I already pulled the previous one and pushed out before reading
more emails and noticing you had so quickly re-done it.
So the READ_ONCE() workaround is there now, but I hope there will be a
future patch that explains (and fixes) whatever made the value change
from underneath that code.
Linus
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [GIT PULL] Pin control fixes for v6.7 minus one patch
2023-11-29 15:48 ` Linus Torvalds
@ 2023-11-29 21:43 ` Linus Walleij
0 siblings, 0 replies; 3+ messages in thread
From: Linus Walleij @ 2023-11-29 21:43 UTC (permalink / raw)
To: Linus Torvalds, Maria Yu
Cc: open list:GPIO SUBSYSTEM, linux-kernel, Charles Keepax
On Wed, Nov 29, 2023 at 4:48 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > Here is an updated tag on a branch where the only change
> > is to drop the locking READ_ONCE() patch until we know
> > more about what is going on here.
>
> Bah. I already pulled the previous one and pushed out before reading
> more emails and noticing you had so quickly re-done it.
>
> So the READ_ONCE() workaround is there now, but I hope there will be a
> future patch that explains (and fixes) whatever made the value change
> from underneath that code.
Fair enough, we'll look closer at it. I just hope I get some help with
that from Maria.
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-11-29 21:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-29 15:18 [GIT PULL] Pin control fixes for v6.7 minus one patch Linus Walleij
2023-11-29 15:48 ` Linus Torvalds
2023-11-29 21:43 ` Linus Walleij
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).