From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
Shawn Guo <shawn.guo@freescale.com>,
Sascha Hauer <kernel@pengutronix.de>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, Steven Miao <realmz6@gmail.com>,
adi-buildroot-devel@lists.sourceforge.net,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80)
Date: Thu, 17 Apr 2014 13:07:44 +0200 [thread overview]
Message-ID: <201404171307.44214.marex@denx.de> (raw)
In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com>
On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote:
> Hi all,
>
> We are introducing a new SPI-NOR library/framework for MTD, to support
> various types of SPI-NOR flash controllers which require (or benefit from)
> intimate knowledge of the flash interface, rather than just the relatively
> dumb SPI interface. This library borrows much of the m25p80 driver for its
> abstraction and moves this code into a spi-nor module.
>
> This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which
> should be added to the defconfigs. I'm not sure what is the best process
> for doing this. Should each $ARCH maintainer just take their respective
> patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet?
> Or should maintainers plan on merging the relevant SPI-NOR code into their
> trees during the development cycle? Or some third option?
Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't
need the adjustment to defconfigs at all I think.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mips@linux-mips.org, Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-sh@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Steven Miao <realmz6@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
adi-buildroot-devel@lists.sourceforge.net,
linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
Olof Johansson <olof@lixom.net>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80)
Date: Thu, 17 Apr 2014 13:07:44 +0200 [thread overview]
Message-ID: <201404171307.44214.marex@denx.de> (raw)
In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com>
On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote:
> Hi all,
>
> We are introducing a new SPI-NOR library/framework for MTD, to support
> various types of SPI-NOR flash controllers which require (or benefit from)
> intimate knowledge of the flash interface, rather than just the relatively
> dumb SPI interface. This library borrows much of the m25p80 driver for its
> abstraction and moves this code into a spi-nor module.
>
> This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which
> should be added to the defconfigs. I'm not sure what is the best process
> for doing this. Should each $ARCH maintainer just take their respective
> patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet?
> Or should maintainers plan on merging the relevant SPI-NOR code into their
> trees during the development cycle? Or some third option?
Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't
need the adjustment to defconfigs at all I think.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80)
Date: Thu, 17 Apr 2014 11:07:44 +0000 [thread overview]
Message-ID: <201404171307.44214.marex@denx.de> (raw)
In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com>
On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote:
> Hi all,
>
> We are introducing a new SPI-NOR library/framework for MTD, to support
> various types of SPI-NOR flash controllers which require (or benefit from)
> intimate knowledge of the flash interface, rather than just the relatively
> dumb SPI interface. This library borrows much of the m25p80 driver for its
> abstraction and moves this code into a spi-nor module.
>
> This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which
> should be added to the defconfigs. I'm not sure what is the best process
> for doing this. Should each $ARCH maintainer just take their respective
> patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet?
> Or should maintainers plan on merging the relevant SPI-NOR code into their
> trees during the development cycle? Or some third option?
Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't
need the adjustment to defconfigs at all I think.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mips@linux-mips.org, Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-sh@vger.kernel.org, Steven Miao <realmz6@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
adi-buildroot-devel@lists.sourceforge.net,
linux-tegra@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
Olof Johansson <olof@lixom.net>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80)
Date: Thu, 17 Apr 2014 13:07:44 +0200 [thread overview]
Message-ID: <201404171307.44214.marex@denx.de> (raw)
In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com>
On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote:
> Hi all,
>
> We are introducing a new SPI-NOR library/framework for MTD, to support
> various types of SPI-NOR flash controllers which require (or benefit from)
> intimate knowledge of the flash interface, rather than just the relatively
> dumb SPI interface. This library borrows much of the m25p80 driver for its
> abstraction and moves this code into a spi-nor module.
>
> This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which
> should be added to the defconfigs. I'm not sure what is the best process
> for doing this. Should each $ARCH maintainer just take their respective
> patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet?
> Or should maintainers plan on merging the relevant SPI-NOR code into their
> trees during the development cycle? Or some third option?
Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't
need the adjustment to defconfigs at all I think.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80)
Date: Thu, 17 Apr 2014 13:07:44 +0200 [thread overview]
Message-ID: <201404171307.44214.marex@denx.de> (raw)
In-Reply-To: <1397719309-2022-1-git-send-email-computersforpeace@gmail.com>
On Thursday, April 17, 2014 at 09:21:44 AM, Brian Norris wrote:
> Hi all,
>
> We are introducing a new SPI-NOR library/framework for MTD, to support
> various types of SPI-NOR flash controllers which require (or benefit from)
> intimate knowledge of the flash interface, rather than just the relatively
> dumb SPI interface. This library borrows much of the m25p80 driver for its
> abstraction and moves this code into a spi-nor module.
>
> This means CONFIG_M25P80 now has a dependency on CONFIG_MTD_SPI_NOR, which
> should be added to the defconfigs. I'm not sure what is the best process
> for doing this. Should each $ARCH maintainer just take their respective
> patch, even if the MTD_SPI_NOR Kconfig symbol is not defined for them yet?
> Or should maintainers plan on merging the relevant SPI-NOR code into their
> trees during the development cycle? Or some third option?
Shouldn't the M25P80 driver just "select" the SPI NOR framework? Then you won't
need the adjustment to defconfigs at all I think.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-17 11:23 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 7:21 [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` [PATCH 1/5] ARM: defconfigs: add MTD_SPI_NOR (new dependency " Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 11:08 ` Marek Vasut
2014-04-17 11:08 ` Marek Vasut
2014-04-17 11:08 ` Marek Vasut
2014-04-21 2:32 ` Huang Shijie
2014-04-21 2:32 ` Huang Shijie
2014-04-21 2:32 ` Huang Shijie
2014-04-25 16:39 ` Stephen Warren
2014-04-25 16:39 ` Stephen Warren
2014-04-25 16:39 ` Stephen Warren
2014-04-29 17:22 ` Ezequiel Garcia
2014-04-29 17:22 ` Ezequiel Garcia
2014-04-29 17:22 ` Ezequiel Garcia
2014-04-29 17:48 ` Jason Cooper
2014-04-29 17:48 ` Jason Cooper
2014-04-29 17:48 ` Jason Cooper
2014-04-29 18:28 ` Ezequiel Garcia
2014-04-29 18:28 ` Ezequiel Garcia
2014-04-29 18:28 ` Ezequiel Garcia
2014-04-29 18:55 ` Jason Cooper
2014-04-29 18:55 ` Jason Cooper
2014-04-29 18:55 ` Jason Cooper
2014-04-29 19:06 ` Brian Norris
2014-04-29 19:06 ` Brian Norris
2014-04-29 19:06 ` Brian Norris
2014-04-29 19:22 ` Ezequiel Garcia
2014-04-29 19:22 ` Ezequiel Garcia
2014-04-29 19:22 ` Ezequiel Garcia
2014-05-01 6:04 ` Brian Norris
2014-05-01 6:04 ` Brian Norris
2014-05-01 6:04 ` Brian Norris
2014-04-29 19:42 ` Stephen Warren
2014-04-29 19:42 ` Stephen Warren
2014-04-29 19:42 ` Stephen Warren
2014-05-01 6:07 ` Brian Norris
2014-05-01 6:07 ` Brian Norris
2014-05-01 6:07 ` Brian Norris
2014-05-01 16:48 ` Stephen Warren
2014-05-01 16:48 ` Stephen Warren
2014-05-01 16:48 ` Stephen Warren
2014-04-30 5:39 ` Huang Shijie
2014-04-30 5:39 ` Huang Shijie
2014-04-30 5:39 ` Huang Shijie
2014-04-30 11:45 ` Jason Cooper
2014-04-30 11:45 ` Jason Cooper
2014-04-30 11:45 ` Jason Cooper
2014-05-01 6:08 ` Brian Norris
2014-05-01 6:08 ` Brian Norris
2014-05-01 6:08 ` Brian Norris
2014-05-03 22:51 ` Olof Johansson
2014-05-03 22:51 ` Olof Johansson
2014-05-03 22:51 ` Olof Johansson
2014-05-04 17:42 ` Jason Cooper
2014-05-04 17:42 ` Jason Cooper
2014-05-04 17:42 ` Jason Cooper
2014-05-04 18:53 ` Olof Johansson
2014-05-04 18:53 ` Olof Johansson
2014-05-04 18:53 ` Olof Johansson
2014-05-06 17:05 ` Brian Norris
2014-05-06 17:05 ` Brian Norris
2014-05-06 17:05 ` Brian Norris
2014-04-17 7:21 ` [PATCH 2/5] blackfin: " Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` [PATCH 3/5] mips: " Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-19 0:24 ` Florian Fainelli
2014-04-19 0:24 ` Florian Fainelli
2014-04-19 0:49 ` Brian Norris
2014-04-19 0:49 ` Brian Norris
2014-04-17 7:21 ` [PATCH 4/5] powerpc: " Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` [PATCH 5/5] sh: defconfig: " Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 7:21 ` Brian Norris
2014-04-17 10:53 ` [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency " Thierry Reding
2014-04-17 10:53 ` Thierry Reding
2014-04-17 10:53 ` Thierry Reding
2014-04-17 10:53 ` Thierry Reding
2014-04-17 10:53 ` Thierry Reding
2014-04-18 6:30 ` Brian Norris
2014-04-18 6:30 ` Brian Norris
2014-04-18 6:30 ` Brian Norris
2014-04-18 6:30 ` Brian Norris
2014-04-18 6:30 ` Brian Norris
2014-04-21 14:52 ` Marek Vasut
2014-04-21 14:52 ` Marek Vasut
2014-04-21 14:52 ` Marek Vasut
2014-04-21 14:52 ` Marek Vasut
2014-04-21 14:52 ` Marek Vasut
2014-04-17 11:07 ` Marek Vasut [this message]
2014-04-17 11:07 ` Marek Vasut
2014-04-17 11:07 ` Marek Vasut
2014-04-17 11:07 ` Marek Vasut
2014-04-17 11:07 ` Marek Vasut
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=201404171307.44214.marex@denx.de \
--to=marex@denx.de \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=computersforpeace@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=realmz6@gmail.com \
--cc=shawn.guo@freescale.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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.