From: Stefan Wahren <stefan.wahren@i2se.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 1/4] bcm2835-defconfig-next-2018-11-27
Date: Wed, 9 Jan 2019 19:38:31 +0100 (CET) [thread overview]
Message-ID: <1330816632.286127.1547059111664@email.ionos.de> (raw)
In-Reply-To: <da219894-4bba-21a3-94dc-da7ff7e63896@gmail.com>
Hi Florian,
> Florian Fainelli <f.fainelli@gmail.com> hat am 28. November 2018 um 22:48 geschrieben:
>
>
>
>
> On 11/27/18 1:12 PM, Eric Anholt wrote:
> > Hi Florian,
> >
> > Hopefully I'm not too late this time around. Stefan's been doing a
> > great job maintaining the bcm2835 branches, and was waiting for me to
> > send the PRs.
> >
> > The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
> >
> > Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
> >
> > are available in the Git repository at:
> >
> > git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-11-27
> >
> > for you to fetch changes up to 24632d6b78a1929b14f32cab762a0859db7086f2:
> >
> > ARM: bcm2835_defconfig: Enable BCM2835 MMAL-based V4L2 camera driver (2018-11-15 19:07:36 +0100)
> >
> > ----------------------------------------------------------------
> > This pull request enables the V4L2 camera driver on the Pi1 defconfig.
> >
> > ----------------------------------------------------------------
>
> Merged into defconfig/next, thanks Eric.
looks like this patch didn't reached Olof for 4.21/5.0.
Should i resend for the next version?
Stefan
next prev parent reply other threads:[~2019-01-09 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 21:12 [GIT PULL 1/4] bcm2835-defconfig-next-2018-11-27 Eric Anholt
2018-11-27 21:12 ` [GIT PULL 2/4] bcm2835-soc-next-2018-11-27 Eric Anholt
2018-11-28 21:48 ` Florian Fainelli
2018-11-27 21:13 ` [GIT PULL 3/4] bcm2835-drivers-next-2018-11-27 Eric Anholt
2018-11-28 21:48 ` Florian Fainelli
2018-11-27 21:13 ` [GIT PULL 4/4] bcm2835-dt-next-2018-11-27 Eric Anholt
2018-11-28 21:49 ` Florian Fainelli
2018-11-28 21:48 ` [GIT PULL 1/4] bcm2835-defconfig-next-2018-11-27 Florian Fainelli
2019-01-09 18:38 ` Stefan Wahren [this message]
2019-01-14 18:36 ` 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=1330816632.286127.1547059111664@email.ionos.de \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=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 \
/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;
as well as URLs for NNTP newsgroup(s).