All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: richard@nod.at, vigneshr@ti.com, miquel.raynal@bootlin.com,
	linux-spi@vger.kernel.org, Yicong Yang <yangyicong@hisilicon.com>,
	tudor.ambarus@microchip.com, linux-mtd@lists.infradead.org
Cc: linuxarm@openeuler.org, john.garry@huawei.com, prime.zeng@huawei.com
Subject: Re: (subset) [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table
Date: Wed, 27 Jan 2021 17:15:30 +0000	[thread overview]
Message-ID: <161176773014.34911.1124682946060569750.b4-ty@kernel.org> (raw)
In-Reply-To: <1611740450-47975-1-git-send-email-yangyicong@hisilicon.com>

On Wed, 27 Jan 2021 17:40:48 +0800, Yicong Yang wrote:
> Add check of 4-byte address mode support when parsing SFDP 4bait. Some
> flash will provide a 4bait table and the spi-nor core will convert the
> address mode to 4-byte without checking whether it's actually supported
> or not by the controller. For example, the 16M s25fs128s1 provides the
> 4bait and will be convert to 4-byte address mode, which makes it unusable
> on hisi-sfc-v3xx on hip08 platform.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[2/2] spi: hisi-sfc-v3xx: add address mode check
      commit: 6d2386e36440165da782dbc5c0de40f31665e108

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: richard@nod.at, vigneshr@ti.com, miquel.raynal@bootlin.com,
	linux-spi@vger.kernel.org, Yicong Yang <yangyicong@hisilicon.com>,
	tudor.ambarus@microchip.com, linux-mtd@lists.infradead.org
Cc: john.garry@huawei.com, linuxarm@openeuler.org, prime.zeng@huawei.com
Subject: Re: (subset) [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table
Date: Wed, 27 Jan 2021 17:15:30 +0000	[thread overview]
Message-ID: <161176773014.34911.1124682946060569750.b4-ty@kernel.org> (raw)
In-Reply-To: <1611740450-47975-1-git-send-email-yangyicong@hisilicon.com>

On Wed, 27 Jan 2021 17:40:48 +0800, Yicong Yang wrote:
> Add check of 4-byte address mode support when parsing SFDP 4bait. Some
> flash will provide a 4bait table and the spi-nor core will convert the
> address mode to 4-byte without checking whether it's actually supported
> or not by the controller. For example, the 16M s25fs128s1 provides the
> 4bait and will be convert to 4-byte address mode, which makes it unusable
> on hisi-sfc-v3xx on hip08 platform.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[2/2] spi: hisi-sfc-v3xx: add address mode check
      commit: 6d2386e36440165da782dbc5c0de40f31665e108

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

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

  parent reply	other threads:[~2021-01-27 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  9:40 [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table Yicong Yang
2021-01-27  9:40 ` Yicong Yang
2021-01-27  9:40 ` [PATCH 1/2] mtd: spi-nor: check 4-byte address support when parsing 4bait Yicong Yang
2021-01-27  9:40   ` Yicong Yang
2021-01-29 11:16   ` Pratyush Yadav
2021-02-01 12:55     ` Yicong Yang
2021-02-01 12:55       ` Yicong Yang
2021-01-27  9:40 ` [PATCH 2/2] spi: hisi-sfc-v3xx: add address mode check Yicong Yang
2021-01-27  9:40   ` Yicong Yang
2021-01-27 17:15 ` Mark Brown [this message]
2021-01-27 17:15   ` (subset) [PATCH 0/2] Add check of 4-byte when parsing SFDP 4bait table Mark Brown

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=161176773014.34911.1124682946060569750.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=john.garry@huawei.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=prime.zeng@huawei.com \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@microchip.com \
    --cc=vigneshr@ti.com \
    --cc=yangyicong@hisilicon.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.