public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner Pinctrl changes for 3.16
Date: Mon, 12 May 2014 17:25:20 +0200	[thread overview]
Message-ID: <20140512152520.GD17154@lukather> (raw)
In-Reply-To: <CACRpkdae=i8C49AMJCrRe0a=4d8Y+FhkiEOv=EJ_NfakYqRvzg@mail.gmail.com>

On Mon, May 12, 2014 at 11:22:27AM +0200, Linus Walleij wrote:
> On Fri, May 9, 2014 at 7:31 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> 
> > Only pinctrl/next is not going to be rebased, right?
> 
> pinctrl/devel actually.
> 
> for-next is a mixdown branch that is rebased all the time
> so don't use that.

Ok.

> But notify me first if you're going to be pulling in that branch!
> (Handshake.)

Yes, this is exactly what I'm doing :)

> Also: why do you need it? Just as a dependence to dts files
> does *not* count as a reason to cross merge these trees,
> as the device tree files are meant to even be moved out of
> the kernel at some point... but you may have better reasons?

It's not about DT, it's about the patch to select the pinctrl drivers
in the machine's Kconfig options.

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140512/0f2f8d12/attachment.sig>

  reply	other threads:[~2014-05-12 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 22:52 [GIT PULL] Allwinner Pinctrl changes for 3.16 Maxime Ripard
2014-05-09  6:48 ` Linus Walleij
2014-05-09 17:31   ` Maxime Ripard
2014-05-12  9:22     ` Linus Walleij
2014-05-12 15:25       ` Maxime Ripard [this message]
2014-05-13  9:37         ` Linus Walleij
2014-05-13 14:49           ` Maxime Ripard

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=20140512152520.GD17154@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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