linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-soc@vger.kernel.org,
	Mahesh Sivasubramanian <msivasub@codeaurora.org>,
	Lina Iyer <ilina@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Evan Green <evgreen@chromium.org>
Subject: Re: [PATCH 0/2] qcom: remove memcpy()ing from cmd-db driver
Date: Thu, 13 Sep 2018 16:30:36 -0500	[thread overview]
Message-ID: <20180913213036.GA15874@hector.attlocal.net> (raw)
In-Reply-To: <20180717202947.197922-1-swboyd@chromium.org>

On Tue, Jul 17, 2018 at 01:29:45PM -0700, Stephen Boyd wrote:
> Some changes to the cmd-db code to not do any more copying
> of memory. Instead, we'll just hand out pointers to things
> inside cmd-db. Merging the second patch will cause problems
> for any in-flight users of the cmd-db APIs that are modified
> and/or removed. Probably that patch can wait until later, or 
> I can provide the fixes for any patches in-flight that get
> wrecked when it's applied.

The Adreno folks picked up the cmd-db APIs and ran with them.  I'll
need an additional patch to fix that breakage.  You can see this in
4.19-rc1.

Thanks,

Andy

  parent reply	other threads:[~2018-09-13 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 20:29 [PATCH 0/2] qcom: remove memcpy()ing from cmd-db driver Stephen Boyd
2018-07-17 20:29 ` [PATCH 1/2] soc: qcom: cmd-db: Remove memcpy()ing from cmd_db_get_header() Stephen Boyd
2018-07-17 20:29 ` [PATCH 2/2] soc: qcom: cmd-db: Stop memcpy()ing in cmd_db_read_aux_data() Stephen Boyd
2018-09-13 21:30 ` Andy Gross [this message]
2018-09-17 18:14   ` [PATCH 0/2] qcom: remove memcpy()ing from cmd-db driver Stephen Boyd

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=20180913213036.GA15874@hector.attlocal.net \
    --to=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=ilina@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=msivasub@codeaurora.org \
    --cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).