Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 5/9] ARM: defconfig: convert to MTD_EEPROM_AT24
Date: Wed, 10 Jul 2024 14:06:34 -0000	[thread overview]
Message-ID: <64662665-929e-4d95-a9ac-c8f66bd83168@app.fastmail.com> (raw)
In-Reply-To: <CAMRc=McvRLeCTTXgC_OD5z5OAxQ0pZ46dTKP8XO+T-LkXKgRfQ@mail.gmail.com>

On Wed, Jul 10, 2024, at 14:59, Bartosz Golaszewski wrote:
> On Wed, Jul 10, 2024 at 2:49?PM Arnd Bergmann <arnd@arndb.de> wrote:
>>
>> On Mon, Jul 1, 2024, at 15:53, Marco Felsch wrote:
>> > The EEPROM_AT24 Kconfig symbol is marked as deprecated. Make use of the
>> > new Kconfig symbol to select the I2C EEPROM driver support.
>> >
>> > Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
>> > ---
>> >  arch/arm/configs/aspeed_g4_defconfig   | 2 +-
>> >  arch/arm/configs/aspeed_g5_defconfig   | 2 +-
>> >  arch/arm/configs/at91_dt_defconfig     | 2 +-
>> >  arch/arm/configs/axm55xx_defconfig     | 2 +-
>> >  arch/arm/configs/davinci_all_defconfig | 2 +-
>> >  arch/arm/configs/imx_v4_v5_defconfig   | 2 +-
>> >  arch/arm/configs/imx_v6_v7_defconfig   | 2 +-
>> >  arch/arm/configs/ixp4xx_defconfig      | 2 +-
>> >  arch/arm/configs/keystone_defconfig    | 2 +-
>> >  arch/arm/configs/lpc18xx_defconfig     | 2 +-
>>
>> Applied to soc/defconfig, thanks
>
> No! Why? This is still being discussed and it's not clear it will even
> make it upstream.

Ok, dropped again, thanks for catching this.

     Arnd

  reply	other threads:[~2024-07-10 14:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 14:15 [PATCH 0/9] AT24 EEPROM MTD Support Marco Felsch
2024-07-01 14:14 ` [PATCH 1/9] mtd: core: add nvmem_write support Marco Felsch
2024-07-01 14:14 ` [PATCH 7/9] MIPS: configs: convert to MTD_EEPROM_AT24 Marco Felsch
2024-07-01 14:15 ` [PATCH 3/9] mtd: add support to handle EEPROM devices Marco Felsch
2024-07-01 14:15 ` [PATCH 9/9] eeprom: at24: remove deprecated Kconfig symbol Marco Felsch
2024-07-02  8:57   ` Bartosz Golaszewski
2024-07-02  9:16     ` Marco Felsch
2024-07-01 14:15 ` [PATCH 8/9] LoongArch: convert to MTD_EEPROM_AT24 Marco Felsch
2024-07-01 14:15 ` [PATCH 5/9] ARM: defconfig: " Marco Felsch
2024-07-10 12:56   ` Arnd Bergmann
2024-07-10 13:00     ` Bartosz Golaszewski
2024-07-10 14:06       ` Arnd Bergmann [this message]
2024-07-01 14:15 ` [PATCH 6/9] powerpc: " Marco Felsch
2024-07-01 14:15 ` [PATCH 2/9] mtd: add mtd_is_master helper Marco Felsch
2024-07-01 16:14   ` Sergei Shtylyov
2024-07-02  8:39     ` Marco Felsch
2024-07-01 14:15 ` [PATCH 4/9] mtd: devices: add AT24 eeprom support Marco Felsch
2024-07-01 16:14   ` Tudor Ambarus
2024-07-02 13:42     ` Pratyush Yadav
2024-07-02 13:56       ` Maxime Ripard
2024-07-02 14:15         ` Pratyush Yadav
2024-07-02 14:34           ` Maxime Ripard
2024-07-08  7:05             ` Miquel Raynal
2024-07-09  9:24               ` Marco Felsch
2024-07-09  9:43                 ` Miquel Raynal
2024-07-09 10:39                   ` Marco Felsch
2024-07-17  8:20                     ` Miquel Raynal
2024-07-18  9:20                       ` Marco Felsch
2024-08-23 15:37                         ` Miquel Raynal
2024-08-23 16:24 ` [PATCH 0/9] AT24 EEPROM MTD Support Andy Shevchenko
2024-08-26  7:51   ` Marco Felsch
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=64662665-929e-4d95-a9ac-c8f66bd83168@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=linux-aspeed@lists.ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox