public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rhyland Klein <rklein@nvidia.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Chris Ball <chris@printf.net>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: tegra: Optimize write_w path for tegra114 and later
Date: Thu, 12 Feb 2015 11:17:19 -0500	[thread overview]
Message-ID: <54DCD20F.7070909@nvidia.com> (raw)
In-Reply-To: <CAAVeFuKVWGExO2y9cb=icvGmNZWTnYve2w2N25t_ybmSo9MPYg@mail.gmail.com>

On 2/11/2015 10:50 PM, Alexandre Courbot wrote:
> On Thu, Feb 12, 2015 at 2:55 AM, Rhyland Klein <rklein@nvidia.com> wrote:
>> Setup a different set of sdhci_ops for tegra114 and later so that
>> the write_w callback is only used on tegra114. This allows us to
>> remove the NVQUIRK_SHADOW_XFER_MODE_REG and simply the logic
>> in tegra_sdhci_writew.
>>
>> This was suggested by Alexandre Courbot.
> 
> There's a tag for that. ;)
> 
> Suggested-by: Alexandre Courbot <acourbot@nvidia.com>
> 
>>
>> Signed-off-by: Rhyland Klein <rklein@nvidia.com>
> 
> Acked-by: Alexandre Courbot <acourbot@nvidia.com>
> 
> Thanks for keeping up with this!
> 

Ahh I figured there had to be one but I wasn't sure. Ulf, I can repost
this if you want unless you want to just update the commit msg (assuming
there are no other complaints).

-rhyland

-- 
nvpublic

  reply	other threads:[~2015-02-12 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 17:55 [PATCH] mmc: tegra: Optimize write_w path for tegra114 and later Rhyland Klein
2015-02-12  3:50 ` Alexandre Courbot
2015-02-12 16:17   ` Rhyland Klein [this message]
2015-03-05 14:59 ` Ulf Hansson

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=54DCD20F.7070909@nvidia.com \
    --to=rklein@nvidia.com \
    --cc=chris@printf.net \
    --cc=gnurou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    --cc=ulf.hansson@linaro.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