All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Gross <agross@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: arm@kernel.org, Olof Johansson <olof@lixom.net>,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] qcom SoC changes for 4.3-rc2
Date: Fri, 28 Aug 2015 12:19:04 -0500	[thread overview]
Message-ID: <20150828171903.GA7886@qualcomm.com> (raw)
In-Reply-To: <20150828001603.GO13472@usrtlx11787.corpusers.net>

On Thu, Aug 27, 2015 at 05:16:03PM -0700, Bjorn Andersson wrote:
> On Thu 27 Aug 14:28 PDT 2015, Andy Gross wrote:
> 
> > The following changes since commit 72af1ff60d08a57e223b9753f9c52396fb4c3897:
> > 
> >   Merge tag 'qcom-soc-for-4.3' into for-soc-new (2015-08-27 12:14:29 -0500)
> > 
> > are available in the git repository at:
> > 
> > 
> >   git://codeaurora.org/quic/kernel/agross-msm.git tags/qcom-soc-for-4.3-rc2
> > 
> > for you to fetch changes up to 3427446d72e21f6992534a3b68055f1b4c722546:
> > 
> >   soc: qcom: smd: Use correct remote processor ID (2015-08-27 12:15:58 -0500)
> > 
> > ----------------------------------------------------------------
> > Qualcomm ARM Based SoC Updates for 4.3-rc2
> > 
> > * Fix errant private access in SMEM
> > * Fix use of correct remote processor ID in SMD transactions
> > 
> 
> I was hoping to see my fBLOCKREADINTR fix [1] here as well, as the issue
> it's fixing it a never ending stall if we're trying to send data with a
> full tx fifo - i.e. a rather bad result...
> 
> But I'm fine with you queuing it for -rc3 too...
> 
> [1] https://lkml.org/lkml/2015/8/24/756
> 
> Regards,
> Bjorn

Ack, sorry.  I'll resend it after bumping the subject

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

WARNING: multiple messages have this Message-ID (diff)
From: agross@codeaurora.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] qcom SoC changes for 4.3-rc2
Date: Fri, 28 Aug 2015 12:19:04 -0500	[thread overview]
Message-ID: <20150828171903.GA7886@qualcomm.com> (raw)
In-Reply-To: <20150828001603.GO13472@usrtlx11787.corpusers.net>

On Thu, Aug 27, 2015 at 05:16:03PM -0700, Bjorn Andersson wrote:
> On Thu 27 Aug 14:28 PDT 2015, Andy Gross wrote:
> 
> > The following changes since commit 72af1ff60d08a57e223b9753f9c52396fb4c3897:
> > 
> >   Merge tag 'qcom-soc-for-4.3' into for-soc-new (2015-08-27 12:14:29 -0500)
> > 
> > are available in the git repository at:
> > 
> > 
> >   git://codeaurora.org/quic/kernel/agross-msm.git tags/qcom-soc-for-4.3-rc2
> > 
> > for you to fetch changes up to 3427446d72e21f6992534a3b68055f1b4c722546:
> > 
> >   soc: qcom: smd: Use correct remote processor ID (2015-08-27 12:15:58 -0500)
> > 
> > ----------------------------------------------------------------
> > Qualcomm ARM Based SoC Updates for 4.3-rc2
> > 
> > * Fix errant private access in SMEM
> > * Fix use of correct remote processor ID in SMD transactions
> > 
> 
> I was hoping to see my fBLOCKREADINTR fix [1] here as well, as the issue
> it's fixing it a never ending stall if we're trying to send data with a
> full tx fifo - i.e. a rather bad result...
> 
> But I'm fine with you queuing it for -rc3 too...
> 
> [1] https://lkml.org/lkml/2015/8/24/756
> 
> Regards,
> Bjorn

Ack, sorry.  I'll resend it after bumping the subject

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-08-28 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 21:28 [GIT PULL] qcom SoC changes for 4.3-rc2 Andy Gross
2015-08-27 21:28 ` Andy Gross
2015-08-28  0:16 ` Bjorn Andersson
2015-08-28  0:16   ` Bjorn Andersson
2015-08-28 17:19   ` Andy Gross [this message]
2015-08-28 17:19     ` Andy Gross

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=20150828171903.GA7886@qualcomm.com \
    --to=agross@codeaurora.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olof@lixom.net \
    /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.