Skip to contentSkip to conversation

MAINTAINERS: update Krzysztof Kozlowski's email

PATCH In review Krzysztof Kozlowski 2 participants 5 messages Mar 21, 2022 – Mar 22, 2022 Stable branch

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: update Krzysztof Kozlowski's email

From: Krzysztof Kozlowski <[email protected]>

commit 5125091d757a251a128ec38d2397c9d160394eac upstream.

Use Krzysztof Kozlowski's @kernel.org account in maintainer entries.

---
 .mailmap    |  1 +
 MAINTAINERS | 28 ++++++++++++++--------------
 2 files changed, 15 insertions(+), 14 deletions(-)
.mailmap +1 -0
index 90e614d2bf7e..243fb1c728b3 100644
@@ -196,6 +196,7 @@ Konstantin Khlebnikov <[email protected]> <[email protected]>
 Koushik <[email protected]>
 Krzysztof Kozlowski <[email protected]> <[email protected]>
 Krzysztof Kozlowski <[email protected]> <[email protected]>
+Krzysztof Kozlowski <[email protected]> <[email protected]>
 Kuninori Morimoto <[email protected]>
 Leonardo Bras <[email protected]> <[email protected]>
 Leonid I Ananiev <[email protected]>
MAINTAINERS +14 -14
index c8103e57a70b..10ad85379afa 100644
@@ -2494,7 +2494,7 @@ F:	sound/soc/rockchip/
 N:	rockchip
 
 ARM/SAMSUNG S3C, S5P AND EXYNOS ARM ARCHITECTURES
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected] (moderated for non-subscribers)
 L:	[email protected]
 S:	Maintained
@@ -11406,7 +11406,7 @@ F:	drivers/regulator/max77802-regulator.c
 F:	include/dt-bindings/*/*max77802.h
 
 MAXIM MUIC CHARGER DRIVERS FOR EXYNOS BASED BOARDS
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Bartlomiej Zolnierkiewicz <[email protected]>
 L:	[email protected]
 S:	Supported
@@ -11415,7 +11415,7 @@ F:	drivers/power/supply/max77693_charger.c
 
 MAXIM PMIC AND MUIC DRIVERS FOR EXYNOS BASED BOARDS
 M:	Chanwoo Choi <[email protected]>
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Bartlomiej Zolnierkiewicz <[email protected]>
 L:	[email protected]
 S:	Supported
@@ -12087,7 +12087,7 @@ F:	include/linux/memblock.h
 F:	mm/memblock.c
 
 MEMORY CONTROLLER DRIVERS
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected]
 S:	Maintained
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git
@@ -13206,7 +13206,7 @@ F:	include/uapi/linux/nexthop.h
 F:	net/ipv4/nexthop.c
 
 NFC SUBSYSTEM
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected] (subscribers-only)
 L:	[email protected]
 S:	Maintained
@@ -13489,7 +13489,7 @@ F:	Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
 F:	drivers/regulator/pf8x00-regulator.c
 
 NXP PTN5150A CC LOGIC AND EXTCON DRIVER
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected]
 S:	Maintained
 F:	Documentation/devicetree/bindings/extcon/extcon-ptn5150.yaml
@@ -14851,7 +14851,7 @@ F:	drivers/pinctrl/renesas/
 
 PIN CONTROLLER - SAMSUNG
 M:	Tomasz Figa <[email protected]>
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Sylwester Nawrocki <[email protected]>
 L:	[email protected] (moderated for non-subscribers)
 L:	[email protected]
@@ -16427,7 +16427,7 @@ W:	http://www.ibm.com/developerworks/linux/linux390/
 F:	drivers/s390/scsi/zfcp_*
 
 S3C ADC BATTERY DRIVER
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected]
 S:	Odd Fixes
 F:	drivers/power/supply/s3c_adc_battery.c
@@ -16472,7 +16472,7 @@ F:	Documentation/admin-guide/LSM/SafeSetID.rst
 F:	security/safesetid/
 
 SAMSUNG AUDIO (ASoC) DRIVERS
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Sylwester Nawrocki <[email protected]>
 L:	[email protected] (moderated for non-subscribers)
 S:	Supported
@@ -16480,7 +16480,7 @@ F:	Documentation/devicetree/bindings/sound/samsung*
 F:	sound/soc/samsung/
 
 SAMSUNG EXYNOS PSEUDO RANDOM NUMBER GENERATOR (RNG) DRIVER
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 L:	[email protected]
 L:	[email protected]
 S:	Maintained
@@ -16515,7 +16515,7 @@ S:	Maintained
 F:	drivers/platform/x86/samsung-laptop.c
 
 SAMSUNG MULTIFUNCTION PMIC DEVICE DRIVERS
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Bartlomiej Zolnierkiewicz <[email protected]>
 L:	[email protected]
 L:	[email protected]
@@ -16540,7 +16540,7 @@ F:	drivers/media/platform/s3c-camif/
 F:	include/media/drv-intf/s3c_camif.h
 
 SAMSUNG S3FWRN5 NFC DRIVER
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Krzysztof Opasiak <[email protected]>
 L:	[email protected] (subscribers-only)
 S:	Maintained
@@ -16560,7 +16560,7 @@ S:	Supported
 F:	drivers/media/i2c/s5k5baf.c
 
 SAMSUNG S5P Security SubSystem (SSS) DRIVER
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Vladimir Zapolskiy <[email protected]>
 L:	[email protected]
 L:	[email protected]
@@ -16596,7 +16596,7 @@ F:	include/linux/clk/samsung.h
 F:	include/linux/platform_data/clk-s3c2410.h
 
 SAMSUNG SPI DRIVERS
-M:	Krzysztof Kozlowski <[email protected]>
+M:	Krzysztof Kozlowski <[email protected]>
 M:	Andi Shyti <[email protected]>
 L:	[email protected]
 L:	[email protected]
Signature · 1 line
2.32.0
maintainer
#1 lore raw
Quoted 6 lines · Krzysztof Kozlowski

From: Krzysztof Kozlowski <[email protected]>

commit 5125091d757a251a128ec38d2397c9d160394eac upstream.

Use Krzysztof Kozlowski's @kernel.org account in maintainer entries.

Quoted 7 lines
---
 .mailmap    |  1 +
 MAINTAINERS | 28 ++++++++++++++--------------
 2 files changed, 15 insertions(+), 14 deletions(-)

We do not normally do MAINTAINERS updates for older kernel trees as no one should be doing development against them.

Any reason why this is different?

thanks,

greg k-h

#2 lore raw
Quoted 15 lines · Greg KH
Quoted 6 lines · Krzysztof Kozlowski

From: Krzysztof Kozlowski <[email protected]>

commit 5125091d757a251a128ec38d2397c9d160394eac upstream.

Use Krzysztof Kozlowski's @kernel.org account in maintainer entries.

Quoted 7 lines
---
 .mailmap    |  1 +
 MAINTAINERS | 28 ++++++++++++++--------------
 2 files changed, 15 insertions(+), 14 deletions(-)
Quoted 5 lines

We do not normally do MAINTAINERS updates for older kernel trees as no one should be doing development against them.

Any reason why this is different?

Hi Greg,

No, it's not different, but people work on backports for stables on a stable branch. Then they send such patch from within the stable tree, because it's easier, I guess. Without the .mailmap all these backports will go to wrong email address - my @canonical.com will start bouncing in two days.

In the same time I am not sure which mailmap is being followed by your and other stable-folks tools, when notifying with backport queue ("5.16.17-rc1 review" etc.).

Plus people actually might have some questions about some my backported commit. They might respond to the email shown in git log, which will be wrong without mailmap file.

Best regards,
Krzysztof

maintainer
#3 lore raw
Quoted 30 lines · Krzysztof Kozlowski
Quoted 15 lines · Greg KH
Quoted 6 lines · Krzysztof Kozlowski

From: Krzysztof Kozlowski <[email protected]>

commit 5125091d757a251a128ec38d2397c9d160394eac upstream.

Use Krzysztof Kozlowski's @kernel.org account in maintainer entries.

Quoted 7 lines
---
 .mailmap    |  1 +
 MAINTAINERS | 28 ++++++++++++++--------------
 2 files changed, 15 insertions(+), 14 deletions(-)
Quoted 5 lines

We do not normally do MAINTAINERS updates for older kernel trees as no one should be doing development against them.

Any reason why this is different?

Hi Greg,

No, it's not different, but people work on backports for stables on a stable branch. Then they send such patch from within the stable tree, because it's easier, I guess. Without the .mailmap all these backports will go to wrong email address - my @canonical.com will start bouncing in two days.

Quoted 3 lines

In the same time I am not sure which mailmap is being followed by your and other stable-folks tools, when notifying with backport queue ("5.16.17-rc1 review" etc.).

I don't use any tools that uses the mailmap file at all. So updating it isn't going to affect the stable patch review process, sorry.

Quoted 3 lines

Plus people actually might have some questions about some my backported commit. They might respond to the email shown in git log, which will be wrong without mailmap file.

People change email addresses all the time, this isn't anything new. I really don't want to get into the habit of having to keep this file up to date with Linus's tree for 6 years, sorry.

thanks,

greg k-h

#4 lore raw
Quoted 15 lines · Greg KH
Quoted 11 lines

Hi Greg,

No, it's not different, but people work on backports for stables on a stable branch. Then they send such patch from within the stable tree, because it's easier, I guess. Without the .mailmap all these backports will go to wrong email address - my @canonical.com will start bouncing in two days.

In the same time I am not sure which mailmap is being followed by your and other stable-folks tools, when notifying with backport queue ("5.16.17-rc1 review" etc.).

I don't use any tools that uses the mailmap file at all. So updating it isn't going to affect the stable patch review process, sorry.

Quoted 8 lines
Quoted 3 lines

Plus people actually might have some questions about some my backported commit. They might respond to the email shown in git log, which will be wrong without mailmap file.

People change email addresses all the time, this isn't anything new. I really don't want to get into the habit of having to keep this file up to date with Linus's tree for 6 years, sorry.

Understood, no problem, thanks for the explanation!

Best regards,
Krzysztof