From: Florian Fainelli <f.fainelli@gmail.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/3] bcm2835-dt-fixes-2020-03-27
Date: Wed, 1 Apr 2020 12:38:42 -0700 [thread overview]
Message-ID: <0db69929-ba6f-555f-7ed4-8a03dd398507@gmail.com> (raw)
In-Reply-To: <20200327211632.32346-1-nsaenzjulienne@suse.de>
On 3/27/2020 2:16 PM, Nicolas Saenz Julienne wrote:
> Hi Florian,
>
> The following changes since commit 55c7c0621078bd73e9d4d2a11eb36e61bc6fe998:
>
> ARM: dts: bcm283x: Fix vc4's firmware bus DMA limitations (2020-03-22 14:45:24 -0700)
>
> are available in the Git repository at:
>
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git tags/bcm2835-dt-fixes-2020-03-27
You would want to provide a public fetch URL for next pull requests, I
fetched your tree so this is fine, but in case someone processes those
messages in a semi automated way, they would not be able to pull from
your tree here.
>
> for you to fetch changes up to be08d278eb09210fefbad4c9b27d7843f1c096b2:
>
> ARM: dts: bcm283x: Add cells encoding format to firmware bus (2020-03-27 21:36:17 +0100)
>
> ----------------------------------------------------------------
> This patch is to be squashed into 55c7c0621078 ("ARM: dts: bcm283x: Fix
> vc4's firmware bus DMA limitations") as it turned out to be faulty
>
> ----------------------------------------------------------------
Merged into devicetree/fixes, thanks Nicolas, looks like the offending
commit has already been applied, though I had not gotten an email about
it, so the fixup in place is no longer an option.
> Nicolas Saenz Julienne (1):
> ARM: dts: bcm283x: Add cells encoding format to firmware bus
>
> arch/arm/boot/dts/bcm2835-rpi.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
--
Florian
next prev parent reply other threads:[~2020-04-01 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 21:16 Nicolas Saenz Julienne
2020-03-27 21:16 ` [GIT PULL 2/3] bcm2835-dt-next-2020-03-27 Nicolas Saenz Julienne
2020-04-04 21:36 ` Florian Fainelli
2020-03-27 21:16 ` [GIT PULL 3/3] bcm2835-defconfig-next-2020-03-27 Nicolas Saenz Julienne
2020-04-04 21:37 ` Florian Fainelli
2020-04-01 19:38 ` Florian Fainelli [this message]
2020-04-01 19:46 ` [GIT PULL 1/3] bcm2835-dt-fixes-2020-03-27 Nicolas Saenz Julienne
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=0db69929-ba6f-555f-7ed4-8a03dd398507@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
/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®