From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>
Subject: [GIT PULL 0/3] BCM2835 pull requests for 4.8
Date: Sun, 3 Jul 2016 17:45:33 -0700 [thread overview]
Message-ID: <1467593136-29524-1-git-send-email-eric@anholt.net> (raw)
It looks like we didn't get an updated defconfig patch while I was
gone, so I'm sending my pull requests for Pi3 and ethernet in the DT
now (the same stuff that's been in -next the whole time). I think
it's still worth it to have Pi3 present in 4.8, even if we don't have
the defconfig in place yet.
WARNING: multiple messages have this Message-ID (diff)
From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/3] BCM2835 pull requests for 4.8
Date: Sun, 3 Jul 2016 17:45:33 -0700 [thread overview]
Message-ID: <1467593136-29524-1-git-send-email-eric@anholt.net> (raw)
It looks like we didn't get an updated defconfig patch while I was
gone, so I'm sending my pull requests for Pi3 and ethernet in the DT
now (the same stuff that's been in -next the whole time). I think
it's still worth it to have Pi3 present in 4.8, even if we don't have
the defconfig in place yet.
next reply other threads:[~2016-07-04 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 0:45 Eric Anholt [this message]
2016-07-04 0:45 ` [GIT PULL 0/3] BCM2835 pull requests for 4.8 Eric Anholt
2016-07-04 0:45 ` [GIT PULL 1/3] bcm2835-dt-next-2016-07-03 Eric Anholt
2016-07-04 0:45 ` Eric Anholt
2016-07-06 3:46 ` Florian Fainelli
2016-07-06 3:46 ` Florian Fainelli
2016-07-04 0:45 ` [GIT PULL 2/3] bcm2835-dt-64-next-2016-07-03 Eric Anholt
2016-07-04 0:45 ` Eric Anholt
2016-07-06 3:48 ` Florian Fainelli
2016-07-06 3:48 ` Florian Fainelli
2016-07-04 0:45 ` [GIT PULL 3/3] bcm2835-arm64-next-2016-07-03 Eric Anholt
2016-07-04 0:45 ` Eric Anholt
2016-07-05 18:03 ` Jason Cooper
2016-07-05 18:03 ` Jason Cooper
2016-07-06 3:50 ` Florian Fainelli
2016-07-06 3:50 ` Florian Fainelli
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=1467593136-29524-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.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.