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: Tue, 13 May 2014 16:49:39 +0200 [thread overview]
Message-ID: <20140513144939.GC29258@lukather> (raw)
In-Reply-To: <CACRpkdZUJrCdyLJdnZw64=rrbOvyHs9nVEmZ=D7ke1hF_n2_Fg@mail.gmail.com>
On Tue, May 13, 2014 at 11:37:15AM +0200, Linus Walleij wrote:
> On Mon, May 12, 2014 at 5:25 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Mon, May 12, 2014 at 11:22:27AM +0200, Linus Walleij wrote:
>
> >> 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.
>
> But ... surely you can select a non-existant symbol and wait
> for it to appear during the merge window?
>
> Or is there some problem with this?
Because it wouldn't be very easily bisectable.
After discussing this a bit more with Arnd on IRC, I'll send you an
additional patch for you to merge, that should solve the issue,
without requiring any merge on my side.
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: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140513/50aa3dee/attachment-0001.sig>
prev parent reply other threads:[~2014-05-13 14:49 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
2014-05-13 9:37 ` Linus Walleij
2014-05-13 14:49 ` Maxime Ripard [this message]
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=20140513144939.GC29258@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 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.