From: Eric Anholt <eric@anholt.net>
To: Martin Sperl <martin@sperl.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] bcm2835 DT changes for 4.6
Date: Wed, 10 Feb 2016 10:51:55 -0800 [thread overview]
Message-ID: <87d1s42yb8.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <DDFB1D8B-805B-488F-9582-796EBCEF287B@sperl.org>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Martin Sperl <martin@sperl.org> writes:
>> On 09.02.2016, at 01:32, Eric Anholt <eric@anholt.net> wrote:
>>
>> Hi Florian. Here's the first set of patches for bcm2835 for 4.6.
>> We've got more DT patches that are going to happen for new boards,
>> too, but they're still getting polished.
>>
>> The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
>>
>> Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
>>
>> are available in the git repository at:
>>
>> git@github.com:anholt/linux.git tags/bcm2835-dt-next-2016-02-04
>>
>> for you to fetch changes up to 5ec6f2cd8ec4bcd38ba199ea8711a5ec906d85e7:
>>
>> ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT. (2016-02-02 20:02:45 -0800)
>>
>> ----------------------------------------------------------------
>> This pull request covers mostly DT changes that didn't make it into
>> 4.5 because required header files went through other trees.
>>
>> ----------------------------------------------------------------
>> Alexander Aring (1):
>> ARM: bcm2835: Add the Raspberry Pi power domain driver to the DT.
>>
>> Lubomir Rintel (1):
>> ARM: bcm2835: dt: Add Raspberry Pi Model A
>>
>> Martin Sperl (2):
>> ARM: bcm2835: add the auxiliary spi1 and spi2 to the device tree
>> ARM: bcm2835: follow dt uart node-naming convention
>
> Do you want me to resend a rebased version of:
> ARM: bcm2835: add bcm2835-aux-uart support to default DT
>
> The corresponding driver has been added to tty/tty-next.
It hadn't landed last time I checked. A rebased version that you've
tested would be great!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-02-10 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 0:32 Eric Anholt
2016-02-10 16:39 ` Martin Sperl
2016-02-10 18:51 ` Eric Anholt [this message]
2016-02-12 3:46 ` Florian Fainelli
2016-02-13 0:53 ` Eric Anholt
2016-02-13 4:00 ` Florian Fainelli
2016-02-18 2:57 ` Eric Anholt
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=87d1s42yb8.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=martin@sperl.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
all inboxes | Powered by JetHome®