Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <Takahiro.Kuwano@infineon.com>
To: <Ronan.Dalton@alliedtelesis.co.nz>
Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>,
	<pratyush@kernel.org>, <linux-kernel@vger.kernel.org>,
	<vigneshr@ti.com>, <linux-mtd@lists.infradead.org>,
	<mwalle@kernel.org>, <Aryan.Srivastava@alliedtelesis.co.nz>,
	<Chris.Packham@alliedtelesis.co.nz>
Subject: RE: [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support"
Date: Thu, 2 Jul 2026 02:41:05 +0000	[thread overview]
Message-ID: <99731a393e5649e692afe57f59d5926b@infineon.com> (raw)
In-Reply-To: <8baaf8a603f7f351b4f7acb7a2df4cb60be9f083.camel@alliedtelesis.co.nz>

Hi Ronan,
 
> Hi Takahiro,
> 
> On Wed, 2026-07-01 at 09:49 +0000, Takahiro.Kuwano@infineon.com wrote:
> >
> > I didn't mean any kernel features, but we can dump tmpfs contents
> > from/to FRAM chip (exposed as NVMEM device) by 'dd'. Doesn't it meet
> > your system's requirement?
> 
> Do you mean something like creating a tmpfs and then say, using `tar`
> and copying the data to nvmem with dd and restoring this data at boot?

Yes, I meant something like that (sorry, my comment was still not clear).
Hope that's worth considering.

Thanks,
Takahiro

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

  reply	other threads:[~2026-07-02  2:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  2:21 [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Ronan Dalton
2026-06-26  2:21 ` [PATCH v2 2/3] mtd: spi-nor: fujitsu: Convert to new flash_info format Ronan Dalton
2026-06-26  2:21 ` [PATCH v2 3/3] mtd: spi-nor: fujitsu: Add support for MB85RS4MTY chip Ronan Dalton
2026-07-01  8:05   ` Michael Walle
2026-07-01 23:48     ` Ronan Dalton
2026-06-30  7:47 ` [PATCH v2 1/3] Revert "mtd: spi-nor: remove Fujitsu MB85RS1MT support" Takahiro.Kuwano
2026-06-30 21:05   ` Chris Packham
2026-07-01  1:10     ` Takahiro.Kuwano
2026-07-01  2:08       ` Ronan Dalton
2026-07-01  8:12         ` Michael Walle
2026-07-01 23:42           ` Ronan Dalton
2026-07-01  9:49         ` Takahiro.Kuwano
2026-07-02  1:21           ` Ronan Dalton
2026-07-02  2:41             ` Takahiro.Kuwano [this message]
2026-07-02  3:06               ` Chris Packham

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=99731a393e5649e692afe57f59d5926b@infineon.com \
    --to=takahiro.kuwano@infineon.com \
    --cc=Aryan.Srivastava@alliedtelesis.co.nz \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=Ronan.Dalton@alliedtelesis.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox