| Message ID | 20221025064623.22808-1-mika.westerberg@linux.intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | spi: intel: Add support for SFDP opcode | expand |
Hi Mark, On Tue, Oct 25, 2022 at 09:46:19AM +0300, Mika Westerberg wrote: > Hi, > > This series adds support for SFDP (Serial Flash Discoverable Parameter) > opcode to the Intel SPI driver. This allows the SPI-NOR core to query > the flash chip what it supports. > > Mika Westerberg (4): > spi: intel: Use ->replacement_op in intel_spi_hw_cycle() > spi: intel: Implement adjust_op_size() > spi: intel: Take possible chip address into account in intel_spi_read/write_reg() > spi: intel: Add support for SFDP opcode > > drivers/spi/spi-intel.c | 78 +++++++++++++++++++++-------------------- > 1 file changed, 40 insertions(+), 38 deletions(-) Any chance getting this queued for v6.2? Thanks!
On Tue, Nov 22, 2022 at 02:30:53PM +0200, Mika Westerberg wrote:
> Any chance getting this queued for v6.2? Thanks!
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review. If there have been
review comments then people may be waiting for those to be addressed.
Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.
On Tue, 25 Oct 2022 09:46:19 +0300, Mika Westerberg wrote: > This series adds support for SFDP (Serial Flash Discoverable Parameter) > opcode to the Intel SPI driver. This allows the SPI-NOR core to query > the flash chip what it supports. > > Mika Westerberg (4): > spi: intel: Use ->replacement_op in intel_spi_hw_cycle() > spi: intel: Implement adjust_op_size() > spi: intel: Take possible chip address into account in intel_spi_read/write_reg() > spi: intel: Add support for SFDP opcode > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: intel: Use ->replacement_op in intel_spi_hw_cycle() commit: f73f6bd200c399d52d7147f66b956a01c93d7606 [2/4] spi: intel: Implement adjust_op_size() commit: 8a9a784fb337cfd07f305faf5358335d4c12a788 [3/4] spi: intel: Take possible chip address into account in intel_spi_read/write_reg() commit: 43f173e7e508ede3d6f5411b9ffbb33d6d284211 [4/4] spi: intel: Add support for SFDP opcode commit: ec4a04aa6962fff3cfa63d70536537844f7446d2 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