All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Samuel Holland <samuel@sholland.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mtd: rawnand: hynix: Add support for H27UCG8T2FTR-BC MLC NAND
Date: Fri, 30 Dec 2022 13:46:46 +0100	[thread overview]
Message-ID: <20221230134646.2e07bcc6@xps-13> (raw)
In-Reply-To: <20221230134507.719edeae@xps-13>

Hi again,

miquel.raynal@bootlin.com wrote on Fri, 30 Dec 2022 13:45:07 +0100:

> Hi Samuel,
> 
> samuel@sholland.org wrote on Thu, 29 Dec 2022 13:09:03 -0600:
> 
> > H27UCG8T2FTR-BC is similar to the already-supported H27UCG8T2ETR-BC, but
> > reports a different ID.
> 
> Can you provide a datasheet for this part? I am surprised by the page
> size. In general anyway, it's best to provide a link when adding
> support for a new component.
> 
> Also, for your two series, no need to resend this time, but please use
> git-format-patch and git-send-email to create your series, so that all
> the patches are answers of the cover letter. It helps keeping all
> patches and answers in the series packed together.

You can ignore this, I did momentarily change the display inadvertently
on my side, your series are perfectly fine.

Sorry for the noise.
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: Samuel Holland <samuel@sholland.org>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mtd: rawnand: hynix: Add support for H27UCG8T2FTR-BC MLC NAND
Date: Fri, 30 Dec 2022 13:46:46 +0100	[thread overview]
Message-ID: <20221230134646.2e07bcc6@xps-13> (raw)
In-Reply-To: <20221230134507.719edeae@xps-13>

Hi again,

miquel.raynal@bootlin.com wrote on Fri, 30 Dec 2022 13:45:07 +0100:

> Hi Samuel,
> 
> samuel@sholland.org wrote on Thu, 29 Dec 2022 13:09:03 -0600:
> 
> > H27UCG8T2FTR-BC is similar to the already-supported H27UCG8T2ETR-BC, but
> > reports a different ID.
> 
> Can you provide a datasheet for this part? I am surprised by the page
> size. In general anyway, it's best to provide a link when adding
> support for a new component.
> 
> Also, for your two series, no need to resend this time, but please use
> git-format-patch and git-send-email to create your series, so that all
> the patches are answers of the cover letter. It helps keeping all
> patches and answers in the series packed together.

You can ignore this, I did momentarily change the display inadvertently
on my side, your series are perfectly fine.

Sorry for the noise.
Miquèl

  reply	other threads:[~2022-12-30 12:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 19:09 [PATCH 0/3] mtd: rawnand: Add H27UCG8T2FTR-BC MLC NAND Samuel Holland
2022-12-29 19:09 ` Samuel Holland
2022-12-29 19:09 ` [PATCH 1/3] mtd: rawnand: hynix: Add support for " Samuel Holland
2022-12-29 19:09   ` Samuel Holland
2022-12-30 12:45   ` Miquel Raynal
2022-12-30 12:45     ` Miquel Raynal
2022-12-30 12:46     ` Miquel Raynal [this message]
2022-12-30 12:46       ` Miquel Raynal
2022-12-30 16:08     ` Samuel Holland
2022-12-30 16:08       ` Samuel Holland
2023-01-02 10:06       ` Miquel Raynal
2023-01-02 10:06         ` Miquel Raynal
2023-01-02 15:50         ` Samuel Holland
2023-01-02 15:50           ` Samuel Holland
2023-01-02 16:59           ` Miquel Raynal
2023-01-02 16:59             ` Miquel Raynal
2022-12-29 19:09 ` [RFC PATCH 2/3] mtd: rawnand: Support non-power-of-two chip sizes Samuel Holland
2022-12-29 19:09   ` Samuel Holland
2022-12-29 19:09 ` [RFC PATCH 3/3] mtd: rawnand: hynix: Expose the full H27UCG8T2FTR-BC chip size Samuel Holland
2022-12-29 19:09   ` Samuel Holland

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=20221230134646.2e07bcc6@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=samuel@sholland.org \
    --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 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.