All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Olof Johansson <olof@lixom.net>, Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	James Hughes <james.hughes@raspberrypi.org>,
	arnd@arndb.de, khilman@kernel.org,
	Yangtao Li <tiny.windzz@gmail.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	arm@kernel.org, bcm-kernel-feedback-list@broadcom.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/4] Broadcom drivers changes for 4.21
Date: Mon, 03 Dec 2018 13:58:27 -0800	[thread overview]
Message-ID: <87wooq9ssc.fsf@anholt.net> (raw)
In-Reply-To: <20181203210740.x5zxpty5x4jnb47v@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1323 bytes --]

Olof Johansson <olof@lixom.net> writes:

> On Sat, Dec 01, 2018 at 12:39:40PM -0800, Florian Fainelli wrote:
>> The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
>> 
>>   Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
>> 
>> are available in the Git repository at:
>> 
>>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.21/drivers
>> 
>> for you to fetch changes up to 1861a7f07e02292830a1ca256328d370deefea30:
>> 
>>   soc: bcm: brcmstb: Don't leak device tree node reference (2018-11-28 13:46:44 -0800)
>> 
>> ----------------------------------------------------------------
>> This pull request contains Broadcom ARM/ARM64/MIPS SoCs drivers changes
>> for 4.21, please pull the following changes:
>> 
>> - James fixes the firmware interface after a commit changed the use of
>>   VLA and broke large transfers
>> 
>> - Stefan adds a timeout check for Raspberry Pi firmware transactions and
>>   updates a bunch of SoC/firmware files to use SPDX tags
>
> Should the timeout and large transfers be merged as fixes?
>
> Picked it up in next/drivers now, we can cherry-pick the fixes if needed.

Large transfers only currently affect the Raspberry Pi fork, and we
shouldn't ever see a timeout in normal operation, so I don't think we
need them for fixes.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-03 21:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01 20:39 [GIT PULL 1/4] Broadcom devicetree changes for 4.21 Florian Fainelli
2018-12-01 20:39 ` [GIT PULL 2/4] Broadcom drivers " Florian Fainelli
2018-12-03 21:07   ` Olof Johansson
2018-12-03 21:58     ` Eric Anholt [this message]
2018-12-01 20:39 ` [GIT PULL 3/4] Broadcom maintainers " Florian Fainelli
2018-12-03 21:08   ` Olof Johansson
2018-12-01 20:39 ` [GIT PULL 4/4] Broadcom soc " Florian Fainelli
2018-12-03 21:09   ` Olof Johansson
2018-12-03 20:54 ` [GIT PULL 1/4] Broadcom devicetree " Olof Johansson

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=87wooq9ssc.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=james.hughes@raspberrypi.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=stefan.wahren@i2se.com \
    --cc=tiny.windzz@gmail.com \
    --cc=wsa+renesas@sang-engineering.com \
    /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.