From: "@SRCHACK.ORG" <tochiro.srchack@gmail.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Add support for EN25QH32
Date: Sat, 19 May 2018 22:33:41 +0900 [thread overview]
Message-ID: <24dc78d7-9779-4169-17fd-7bbcca69cea4@gmail.com> (raw)
In-Reply-To: <20180518220809.14071539@bbrezillon>
Dear, Boris
Thanks,
Yes, I will.
On 2018/05/19 5:08, Boris Brezillon wrote:
> On Thu, 17 May 2018 11:40:27 +0900
> YuheiOKAWA <tochiro.srchack@gmail.com> wrote:
>
>> Add support for Eon en25qh32 spi nor flash.
>>
>> Sorry, very sorry.
>> I had misspelled it. chip name is en25qh32, non en25ph32.
>
> Queued to spi-nor/next after removing this sentence :-).
>
> Next time you want to add extra information that you don't want
> to appear in the commit, just put it after the "---" separator ;-).
>
> Also, you should prefix your patch with "[PATCH v2]" and add a
> changelog after the "---". Something like:
>
> "
> ---
> Changes in v2:
> - blablabla
> "
>
> Thanks,
>
> Boris
>
>>
>> Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com>
>> ---
>> drivers/mtd/spi-nor/spi-nor.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
>> index 5bfa36e..7bc556c 100644
>> --- a/drivers/mtd/spi-nor/spi-nor.c
>> +++ b/drivers/mtd/spi-nor/spi-nor.c
>> @@ -980,6 +980,7 @@ static const struct flash_info spi_nor_ids[] = {
>> { "en25q32b", INFO(0x1c3016, 0, 64 * 1024, 64, 0) },
>> { "en25p64", INFO(0x1c2017, 0, 64 * 1024, 128, 0) },
>> { "en25q64", INFO(0x1c3017, 0, 64 * 1024, 128, SECT_4K) },
>> + { "en25qh32", INFO(0x1c7016, 0, 64 * 1024, 64, 0) },
>> { "en25qh128", INFO(0x1c7018, 0, 64 * 1024, 256, 0) },
>> { "en25qh256", INFO(0x1c7019, 0, 64 * 1024, 512, 0) },
>> { "en25s64", INFO(0x1c3817, 0, 64 * 1024, 128, SECT_4K) },
>
>
--
------------------------------------------------------
@SRCHACK.ORG
tochiro.srchack@gmail.com
http://www.srchack.org/
------------------------------------------------------
prev parent reply other threads:[~2018-05-19 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 2:33 [PATCH] mtd: spi-nor: Add support for EN25QH32 YuheiOKAWA
2018-05-17 2:40 ` YuheiOKAWA
2018-05-18 20:08 ` Boris Brezillon
2018-05-19 13:33 ` @SRCHACK.ORG [this message]
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=24dc78d7-9779-4169-17fd-7bbcca69cea4@gmail.com \
--to=tochiro.srchack@gmail.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.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