All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Andy Gross <andy.gross@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, arm@kernel.org,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: [GIT PULL] Qualcomm SoC Updates for v4.11
Date: Sun, 29 Jan 2017 16:26:44 -0800	[thread overview]
Message-ID: <20170130002644.GP3133@localhost> (raw)
In-Reply-To: <1485240752-8339-1-git-send-email-andy.gross@linaro.org>

On Tue, Jan 24, 2017 at 12:52:32AM -0600, Andy Gross wrote:
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
> 
>   Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-soc-for-4.11
> 
> for you to fetch changes up to aabde95fc543a9ca68df06b9c7ea8e699702d7ad:
> 
>   firmware: qcom: scm: Fix interrupted SCM calls (2017-01-23 10:01:49 -0600)
> 
> ----------------------------------------------------------------
> Qualcomm ARM Based SoC Updates for v4.11
> 
> * Add SMCC quirk support
> * Add Qualcomm SCM quirk to fix interrupted calls

Hi,

I replied on one of the patches. Not sure doing this through quirks is the
right way right now -- unless we expect a lot more quirks over time, and/or if
this is an "enhancement" that other vendors are also likely to pick up.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Qualcomm SoC Updates for v4.11
Date: Sun, 29 Jan 2017 16:26:44 -0800	[thread overview]
Message-ID: <20170130002644.GP3133@localhost> (raw)
In-Reply-To: <1485240752-8339-1-git-send-email-andy.gross@linaro.org>

On Tue, Jan 24, 2017 at 12:52:32AM -0600, Andy Gross wrote:
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
> 
>   Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-soc-for-4.11
> 
> for you to fetch changes up to aabde95fc543a9ca68df06b9c7ea8e699702d7ad:
> 
>   firmware: qcom: scm: Fix interrupted SCM calls (2017-01-23 10:01:49 -0600)
> 
> ----------------------------------------------------------------
> Qualcomm ARM Based SoC Updates for v4.11
> 
> * Add SMCC quirk support
> * Add Qualcomm SCM quirk to fix interrupted calls

Hi,

I replied on one of the patches. Not sure doing this through quirks is the
right way right now -- unless we expect a lot more quirks over time, and/or if
this is an "enhancement" that other vendors are also likely to pick up.


-Olof

  reply	other threads:[~2017-01-30  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24  6:52 [GIT PULL] Qualcomm SoC Updates for v4.11 Andy Gross
2017-01-24  6:52 ` Andy Gross
2017-01-30  0:26 ` Olof Johansson [this message]
2017-01-30  0:26   ` Olof Johansson
2017-01-31  7:11   ` Andy Gross
2017-01-31  7:11     ` Andy Gross
2017-01-31 17:44     ` Olof Johansson
2017-01-31 17:44       ` Olof Johansson

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=20170130002644.GP3133@localhost \
    --to=olof@lixom.net \
    --cc=andy.gross@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@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 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.