All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: "Maxime Ripard" <mripard@kernel.org>,
	"Pratyush Yadav" <pratyush@kernel.org>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Russell King" <linux@armlinux.org.uk>,
	"Joel Stanley" <joel@jms.id.au>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Dinh Nguyen" <dinguyen@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"WANG Xuerui" <kernel@xen0n.name>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, imx@lists.linux.dev,
	linux-omap@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-tegra@vger.kernel.org, openbmc@lists.ozlabs.org,
	linuxppc-dev@lists.ozlabs.org, linux-mips@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: Re: [PATCH 4/9] mtd: devices: add AT24 eeprom support
Date: Wed, 17 Jul 2024 10:19:48 +0200	[thread overview]
Message-ID: <20240717101948.2e99f472@xps-13> (raw)
In-Reply-To: <20240709103841.7x7n4hdtqrunyoc3@pengutronix.de>

Hi Marco,

> > > > Overall I think the idea of getting rid of these misc/ drivers is goes
> > > > into the right direction, but registering directly into NVMEM makes
> > > > more sense IMO.    
> > > 
> > > So you propose to have two places for the partition handling (one for
> > > MTD and one for NVMEM) instead of one and moving the code into NVMEM
> > > directly?  
> > 
> > Why two places for the partitions handling? Just one, in NVMEM. Also  
> 
> Without checking the details I think that converting the MTD
> partitioning code into NVMEM partitioning code is a bigger task. As you
> said below there are many legacy code paths you need to consider so they
> still work afterwards as well.
> 
> > usually EEPROMs don't require very advanced partitioning schemes,
> > unlike flashes (which are the most common MTD devices today).  
> 
> As said in my cover letter EEPROMs can become quite large and MTD
> supports partitioning storage devices which is very handy for large
> EEPROMs as well.

Did you had a look at nvmem-layouts ? In particular the fixed-layout.

Is there anything you would like to achieve already that is not
possible with nvmem but is with mtd?

Thanks,
Miquèl

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 4/9] mtd: devices: add AT24 eeprom support
Date: Wed, 17 Jul 2024 08:20:18 -0000	[thread overview]
Message-ID: <20240717101948.2e99f472@xps-13> (raw)
In-Reply-To: <20240709103841.7x7n4hdtqrunyoc3@pengutronix.de>

Hi Marco,

> > > > Overall I think the idea of getting rid of these misc/ drivers is goes
> > > > into the right direction, but registering directly into NVMEM makes
> > > > more sense IMO.    
> > > 
> > > So you propose to have two places for the partition handling (one for
> > > MTD and one for NVMEM) instead of one and moving the code into NVMEM
> > > directly?  
> > 
> > Why two places for the partitions handling? Just one, in NVMEM. Also  
> 
> Without checking the details I think that converting the MTD
> partitioning code into NVMEM partitioning code is a bigger task. As you
> said below there are many legacy code paths you need to consider so they
> still work afterwards as well.
> 
> > usually EEPROMs don't require very advanced partitioning schemes,
> > unlike flashes (which are the most common MTD devices today).  
> 
> As said in my cover letter EEPROMs can become quite large and MTD
> supports partitioning storage devices which is very handy for large
> EEPROMs as well.

Did you had a look at nvmem-layouts ? In particular the fixed-layout.

Is there anything you would like to achieve already that is not
possible with nvmem but is with mtd?

Thanks,
Miqu?l

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: "Maxime Ripard" <mripard@kernel.org>,
	"Pratyush Yadav" <pratyush@kernel.org>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Russell King" <linux@armlinux.org.uk>,
	"Joel Stanley" <joel@jms.id.au>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Dinh Nguyen" <dinguyen@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"WANG Xuerui" <kernel@xen0n.name>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, imx@lists.linux.dev,
	linux-omap@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-tegra@vger.kernel.org, openbmc@lists.ozlabs.org,
	linuxppc-dev@lists.ozlabs.org, linux-mips@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: Re: [PATCH 4/9] mtd: devices: add AT24 eeprom support
Date: Wed, 17 Jul 2024 10:19:48 +0200	[thread overview]
Message-ID: <20240717101948.2e99f472@xps-13> (raw)
In-Reply-To: <20240709103841.7x7n4hdtqrunyoc3@pengutronix.de>

Hi Marco,

> > > > Overall I think the idea of getting rid of these misc/ drivers is goes
> > > > into the right direction, but registering directly into NVMEM makes
> > > > more sense IMO.    
> > > 
> > > So you propose to have two places for the partition handling (one for
> > > MTD and one for NVMEM) instead of one and moving the code into NVMEM
> > > directly?  
> > 
> > Why two places for the partitions handling? Just one, in NVMEM. Also  
> 
> Without checking the details I think that converting the MTD
> partitioning code into NVMEM partitioning code is a bigger task. As you
> said below there are many legacy code paths you need to consider so they
> still work afterwards as well.
> 
> > usually EEPROMs don't require very advanced partitioning schemes,
> > unlike flashes (which are the most common MTD devices today).  
> 
> As said in my cover letter EEPROMs can become quite large and MTD
> supports partitioning storage devices which is very handy for large
> EEPROMs as well.

Did you had a look at nvmem-layouts ? In particular the fixed-layout.

Is there anything you would like to achieve already that is not
possible with nvmem but is with mtd?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	imx@lists.linux.dev, "Tony Lindgren" <tony@atomide.com>,
	"Nicolas Ferre" <nicolas.ferre@microchip.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
	"WANG Xuerui" <kernel@xen0n.name>,
	"Fabio Estevam" <festevam@gmail.com>,
	linux-aspeed@lists.ozlabs.org,
	"Richard Weinberger" <richard@nod.at>,
	"Gregory Clement" <gregory.clement@bootlin.com>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Russell King" <linux@armlinux.org.uk>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	"Joel Stanley" <joel@jms.id.au>,
	"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	openbmc@lists.ozlabs.org, "Sascha Hauer" <s.hauer@pengutronix.de>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	loongarch@lists.linux.dev, linux-tegra@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	linux-mips@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linuxppc-dev@lists.ozlabs.org,
	"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	"Dinh Nguyen" <dinguyen@kernel.org>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Pratyush Yadav" <pratyush@kernel.org>
Subject: Re: [PATCH 4/9] mtd: devices: add AT24 eeprom support
Date: Wed, 17 Jul 2024 10:19:48 +0200	[thread overview]
Message-ID: <20240717101948.2e99f472@xps-13> (raw)
In-Reply-To: <20240709103841.7x7n4hdtqrunyoc3@pengutronix.de>

Hi Marco,

> > > > Overall I think the idea of getting rid of these misc/ drivers is goes
> > > > into the right direction, but registering directly into NVMEM makes
> > > > more sense IMO.    
> > > 
> > > So you propose to have two places for the partition handling (one for
> > > MTD and one for NVMEM) instead of one and moving the code into NVMEM
> > > directly?  
> > 
> > Why two places for the partitions handling? Just one, in NVMEM. Also  
> 
> Without checking the details I think that converting the MTD
> partitioning code into NVMEM partitioning code is a bigger task. As you
> said below there are many legacy code paths you need to consider so they
> still work afterwards as well.
> 
> > usually EEPROMs don't require very advanced partitioning schemes,
> > unlike flashes (which are the most common MTD devices today).  
> 
> As said in my cover letter EEPROMs can become quite large and MTD
> supports partitioning storage devices which is very handy for large
> EEPROMs as well.

Did you had a look at nvmem-layouts ? In particular the fixed-layout.

Is there anything you would like to achieve already that is not
possible with nvmem but is with mtd?

Thanks,
Miquèl

  reply	other threads:[~2024-07-17  8:20 UTC|newest]

Thread overview: 131+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 13:53 [PATCH 0/9] AT24 EEPROM MTD Support Marco Felsch
2024-07-01 14:15 ` Marco Felsch
2024-07-01 13:53 ` Marco Felsch
2024-07-01 13:53 ` Marco Felsch
2024-07-01 13:53 ` [PATCH 1/9] mtd: core: add nvmem_write support Marco Felsch
2024-07-01 14:14   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53 ` [PATCH 2/9] mtd: add mtd_is_master helper Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 16:14   ` Sergei Shtylyov
2024-07-01 16:14     ` Sergei Shtylyov
2024-07-01 16:14     ` Sergei Shtylyov
2024-07-01 16:14     ` Sergei Shtylyov
2024-07-02  8:22     ` Marco Felsch
2024-07-02  8:39       ` Marco Felsch
2024-07-02  8:22       ` Marco Felsch
2024-07-02  8:22       ` Marco Felsch
2024-07-02  8:22       ` Marco Felsch
2024-07-01 13:53 ` [PATCH 3/9] mtd: add support to handle EEPROM devices Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53 ` [PATCH 4/9] mtd: devices: add AT24 eeprom support Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 16:14   ` Tudor Ambarus
2024-07-01 16:14     ` Tudor Ambarus
2024-07-01 16:14     ` Tudor Ambarus
2024-07-01 16:14     ` Tudor Ambarus
2024-07-02 13:41     ` Pratyush Yadav
2024-07-02 13:42       ` Pratyush Yadav
2024-07-02 13:41       ` Pratyush Yadav
2024-07-02 13:41       ` Pratyush Yadav
2024-07-02 13:56       ` Maxime Ripard
2024-07-02 13:56         ` Maxime Ripard
2024-07-02 13:56         ` Maxime Ripard
2024-07-02 13:56         ` Maxime Ripard
2024-07-02 14:15         ` Pratyush Yadav
2024-07-02 14:15           ` Pratyush Yadav
2024-07-02 14:15           ` Pratyush Yadav
2024-07-02 14:15           ` Pratyush Yadav
2024-07-02 14:34           ` Maxime Ripard
2024-07-02 14:34             ` Maxime Ripard
2024-07-02 14:34             ` Maxime Ripard
2024-07-02 14:34             ` Maxime Ripard
2024-07-08  6:44             ` Miquel Raynal
2024-07-08  7:05               ` Miquel Raynal
2024-07-08  6:44               ` Miquel Raynal
2024-07-08  6:44               ` Miquel Raynal
2024-07-09  9:22               ` Marco Felsch
2024-07-09  9:24                 ` Marco Felsch
2024-07-09  9:22                 ` Marco Felsch
2024-07-09  9:22                 ` Marco Felsch
2024-07-09  9:43                 ` Miquel Raynal
2024-07-09  9:43                   ` Miquel Raynal
2024-07-09  9:43                   ` Miquel Raynal
2024-07-09  9:43                   ` Miquel Raynal
2024-07-09 10:38                   ` Marco Felsch
2024-07-09 10:39                     ` Marco Felsch
2024-07-09 10:38                     ` Marco Felsch
2024-07-09 10:38                     ` Marco Felsch
2024-07-17  8:19                     ` Miquel Raynal [this message]
2024-07-17  8:20                       ` Miquel Raynal
2024-07-17  8:19                       ` Miquel Raynal
2024-07-17  8:19                       ` Miquel Raynal
2024-07-18  9:17                       ` Marco Felsch
2024-07-18  9:20                         ` Marco Felsch
2024-07-18  9:17                         ` Marco Felsch
2024-07-18  9:17                         ` Marco Felsch
2024-08-23 15:37                         ` Miquel Raynal
2024-08-23 15:37                           ` Miquel Raynal
2024-08-23 15:37                           ` Miquel Raynal
2024-07-01 13:53 ` [PATCH 5/9] ARM: defconfig: convert to MTD_EEPROM_AT24 Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-10 12:48   ` Arnd Bergmann
2024-07-10 12:56     ` Arnd Bergmann
2024-07-10 12:48     ` Arnd Bergmann
2024-07-10 12:48     ` Arnd Bergmann
2024-07-10 12:59     ` Bartosz Golaszewski
2024-07-10 13:00       ` Bartosz Golaszewski
2024-07-10 12:59       ` Bartosz Golaszewski
2024-07-10 12:59       ` Bartosz Golaszewski
2024-07-10 12:59       ` Bartosz Golaszewski
2024-07-10 14:06       ` Arnd Bergmann
2024-07-10 14:06         ` Arnd Bergmann
2024-07-10 14:06         ` Arnd Bergmann
2024-07-10 14:06         ` Arnd Bergmann
2024-07-01 13:53 ` [PATCH 6/9] powerpc: " Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53 ` [PATCH 7/9] MIPS: configs: " Marco Felsch
2024-07-01 14:14   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53 ` [PATCH 8/9] LoongArch: " Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53 ` [PATCH 9/9] eeprom: at24: remove deprecated Kconfig symbol Marco Felsch
2024-07-01 14:15   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-01 13:53   ` Marco Felsch
2024-07-02  8:57   ` Bartosz Golaszewski
2024-07-02  8:57     ` Bartosz Golaszewski
2024-07-02  8:57     ` Bartosz Golaszewski
2024-07-02  8:57     ` Bartosz Golaszewski
2024-07-02  8:57     ` Bartosz Golaszewski
2024-07-02  9:15     ` Marco Felsch
2024-07-02  9:16       ` Marco Felsch
2024-07-02  9:15       ` Marco Felsch
2024-07-02  9:15       ` Marco Felsch
2024-07-02  9:15       ` Marco Felsch
2024-08-23 16:24 ` [PATCH 0/9] AT24 EEPROM MTD Support Andy Shevchenko
2024-08-23 16:24   ` Andy Shevchenko
2024-08-23 16:24   ` Andy Shevchenko
2024-08-23 16:24   ` Andy Shevchenko
2024-08-26  7:51   ` Marco Felsch
2024-08-26  7:51     ` Marco Felsch
2024-08-26  7:51     ` Marco Felsch
2024-08-26  7:51     ` Marco Felsch
2024-08-26 10:32     ` Andy Shevchenko
2024-08-26 10:32       ` Andy Shevchenko
2024-08-26 10:32       ` Andy Shevchenko
2024-08-26 10:32       ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240717101948.2e99f472@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=chenhuacai@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=dinguyen@kernel.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@bootlin.com \
    --cc=imx@lists.linux.dev \
    --cc=j.neuschaefer@gmx.net \
    --cc=joel@jms.id.au \
    --cc=jonathanh@nvidia.com \
    --cc=kernel@pengutronix.de \
    --cc=kernel@xen0n.name \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=m.felsch@pengutronix.de \
    --cc=magnus.damm@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=mripard@kernel.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=npiggin@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=s.hauer@pengutronix.de \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=shawnguo@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=tony@atomide.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=tudor.ambarus@linaro.org \
    --cc=vigneshr@ti.com \
    --cc=vz@mleia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.