public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jarrett Schultz <jaschultzms@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mark Gross <markgross@kernel.org>,
	Maximilian Luz <luzmaximilian@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,
	Felipe Balbi <balbi@kernel.org>,
	Jarrett Schultz <jaschultz@microsoft.com>
Subject: Re: [PATCH v5 0/4] platform: surface: Introduce Surface XBL Driver
Date: Wed, 13 Apr 2022 13:28:40 -0500	[thread overview]
Message-ID: <YlcWWPqGzc4Zk9R+@robh.at.kernel.org> (raw)
In-Reply-To: <d648629e-2339-449f-f63c-41af85ba35b5@redhat.com>

On Mon, Apr 11, 2022 at 02:13:42PM +0200, Hans de Goede wrote:
> Hi Jarrett,
> 
> On 1/1/70 01:00, Jarrett Schultz wrote:
> > After v4, there were some suggestions to change the driver again to use
> > nvmem that would include some other changes to the sm8150 dtsi. While
> > the suggestions make sense, this driver was supposed to remain simple
> > for the introduction in order to get it into the tree and I think that
> > it would be best to implement those and any other suggestions in a future
> > patch. Hopefully this patch is now in a state where it can be accepted.
> > Thanks to all who have helped and been patient along the way, this was
> > my first patch :)
> I appreciate your efforts to get this upstream, but this is not
> how upstream development typically works. We usually iterate a patch
> until all stakeholders are happy and then merge it.
> 
> So unless Rob changes its mind and gives his Reviewed-by for the
> devicetree bits from this v5, then this cannot be merged as is.

This is dependent on the QCom folks. We can't really define the child 
without first defining the parent binding.

Rob

      reply	other threads:[~2022-04-13 18:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 21:07 [PATCH v5 0/4] platform: surface: Introduce Surface XBL Driver Jarrett Schultz
2022-04-05 21:07 ` [PATCH v5 1/4] dt-bindings: platform: microsoft: Document surface xbl Jarrett Schultz
2022-04-13 18:27   ` Rob Herring
2022-04-18 22:53     ` [EXTERNAL] " Jarrett Schultz
2022-04-21 14:47       ` Jarrett Schultz
2022-04-05 21:07 ` [PATCH v5 2/4] platform: surface: Add " Jarrett Schultz
2022-04-05 21:07 ` [PATCH v5 3/4] arm64: dts: qcom: sm8150: Add imem section Jarrett Schultz
2022-04-05 21:07 ` [PATCH v5 4/4] arm64: dts: qcom: surface-duo: Add surface xbl Jarrett Schultz
2022-04-11 12:13 ` [PATCH v5 0/4] platform: surface: Introduce Surface XBL Driver Hans de Goede
2022-04-13 18:28   ` Rob Herring [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=YlcWWPqGzc4Zk9R+@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=balbi@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=jaschultz@microsoft.com \
    --cc=jaschultzms@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.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