Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: Andy Gross <agross@codeaurora.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 5/5] regulator: Regulator driver for the Qualcomm RPM
Date: Sat, 15 Aug 2015 07:05:20 -0700	[thread overview]
Message-ID: <20150815140520.GA10748@sirena.org.uk> (raw)
In-Reply-To: <20150815045950.GL13472@usrtlx11787.corpusers.net>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Fri, Aug 14, 2015 at 09:59:50PM -0700, Bjorn Andersson wrote:
> On Fri 14 Aug 19:14 PDT 2015, Mark Brown wrote:

> > Please submit any patches you think should be included in the upstream
> > kernel using the process documented in SubmittingPatches.

> I'm sorry, I thought I did and Andy's comment was to inform you that the
> other 4 patches in this series have been merged.

> Do you want me to resend this single patch on its own? Or is there
> anything else you would like me to do with it?

Yes, you need to send patches to me if you want me to consider applying
them.  Sending me content free pings mostly just adds to the mail
volume, I can't apply a content free ping and given that it's a reply to
something with my Reviewed-by on it's not even something I replied to.

If I gave a Reviewed-by for the patch it's presumably because there are
some dependencies that prevented me just applying it and I was expecting
it to go in with the rest of the series, are there any actual
dependencies here or have the dependencies reached Linus' tree?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-08-15 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  3:20 [PATCH v3 0/5] Qualcomm Shared Memory & RPM drivers Bjorn Andersson
2015-07-28  3:20 ` [PATCH v3 1/5] soc: qcom: Add device tree binding for Shared Memory Device Bjorn Andersson
2015-07-29 19:01   ` Andy Gross
2015-07-28  3:20 ` [PATCH v3 2/5] soc: qcom: Add Shared Memory Driver Bjorn Andersson
2015-07-29 19:03   ` Andy Gross
2015-07-28  3:20 ` [PATCH v3 3/5] devicetree: soc: Add Qualcomm SMD based RPM DT binding Bjorn Andersson
2015-07-29 19:37   ` Andy Gross
2015-07-28  3:20 ` [PATCH v3 4/5] soc: qcom: Driver for the Qualcomm RPM over SMD Bjorn Andersson
2015-07-29 18:54   ` Andy Gross
2015-07-28  3:20 ` [PATCH v3 5/5] regulator: Regulator driver for the Qualcomm RPM Bjorn Andersson
2015-08-14 16:58   ` Andy Gross
2015-08-14 21:41     ` Tim Bird
2015-08-15  2:14     ` Mark Brown
2015-08-15  4:59       ` Bjorn Andersson
2015-08-15 14:05         ` Mark Brown [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=20150815140520.GA10748@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=agross@codeaurora.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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