mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
	"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: pull request for some small fixes
Date: Tue, 7 Jan 2014 14:51:22 +0200	[thread overview]
Message-ID: <20140107125122.GC26588@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20140106054322.26907.37296@quantum>

On Mon, Jan 06, 2014 at 06:43:22AM +0100, Mike Turquette wrote:
> Quoting Peter De Schrijver (2013-12-23 08:27:05)
> > The following changes since commit 62ce7cd62f534023224912dc9b909963f26a38da:
> > 
> >   clk: tegra: fix __clk_lookup() return value checks (2013-11-28 15:09:22 +0200)
> > 
> > are available in the git repository at:
> >   git://nv-tegra.nvidia.com/user/pdeschrijver/linux.git clk-tegra-next-1
> 
> Hi Peter,
> 
> Do you intend for this to go as fixes for 3.13-rc8? The fixes are based

Yes.

> off of a commit from my clk-next branch.
> 
Do you want me to rebase them on 3.13-rc7?

Cheers,

Peter.

  parent reply	other threads:[~2014-01-07 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 16:27 Peter De Schrijver
     [not found] ` <20140106054322.26907.37296@quantum>
2014-01-07 12:51   ` Peter De Schrijver [this message]
     [not found]     ` <20140108162757.27803.23767@quantum>
2014-01-09 12:53       ` Peter De Schrijver

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=20140107125122.GC26588@tbergstrom-lnx.Nvidia.com \
    --to=pdeschrijver@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@linaro.org \
    --cc=pawel.moll@arm.com \
    --cc=pgaikwad@nvidia.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    /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

all inboxes | Powered by JetHome®