public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: <broonie@kernel.org>
Cc: Md Sadre Alam <quic_mdalam@quicinc.com>,  <andersson@kernel.org>,
	<konradybcio@kernel.org>,  <richard@nod.at>,  <vigneshr@ti.com>,
	<manivannan.sadhasivam@linaro.org>,
	 <linux-arm-msm@vger.kernel.org>, <linux-spi@vger.kernel.org>,
	 <linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
	 Tudor Ambarus <Tudor.Ambarus@linaro.org>,
	 Frieder Schrempf <frieder.schrempf@kontron.de>,
	 Michael Walle <michael@walle.cc>,
	Pratyush Yadav <pratyush@kernel.org>,
	 <quic_srichara@quicinc.com>, <quic_varada@quicinc.com>
Subject: Re: [GIT PULL] mtd: topic branch for spi with Qcom changes
Date: Mon, 06 Jan 2025 14:49:18 +0100	[thread overview]
Message-ID: <87bjwkoxwh.fsf@bootlin.com> (raw)
In-Reply-To: <87jzbp9hnt.fsf@bootlin.com> (Miquel Raynal's message of "Tue, 24 Dec 2024 17:20:38 +0100")

Hi Mark,

On 24/12/2024 at 17:20:38 +01, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> Hello Mark,
>
> I'm merging the Qcom series, in case you need a topic branch to apply
> the spi bits (binding and driver), here it is.

There is a breakage on x86 with this series, I'm applying another patch
from Md Sadre Alam on top, so I'd suggest to not merge this branch and
wait for the next cycle to take the spi bits if you're happy with them.

Link: https://lore.kernel.org/linux-mtd/20250106131558.2219136-1-quic_mdalam@quicinc.com/T/#u

Thanks,
Miquèl

  reply	other threads:[~2025-01-06 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-24 16:20 [GIT PULL] mtd: topic branch for spi with Qcom changes Miquel Raynal
2025-01-06 13:49 ` Miquel Raynal [this message]
2025-01-06 15:36   ` Mark Brown
2025-02-17  5:55     ` Md Sadre Alam
2025-02-18 14:54       ` Mark Brown
2025-02-20 11:33         ` Md Sadre Alam

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=87bjwkoxwh.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=Tudor.Ambarus@linaro.org \
    --cc=andersson@kernel.org \
    --cc=broonie@kernel.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=michael@walle.cc \
    --cc=pratyush@kernel.org \
    --cc=quic_mdalam@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --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