From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org,
arnd@arndb.de, olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 1/3] Broadcom devicetree changes for 5.13
Date: Wed, 31 Mar 2021 14:48:13 -0700 [thread overview]
Message-ID: <c71b8949-b709-cb5b-b5a4-87cebf8cd8df@gmail.com> (raw)
In-Reply-To: <498a63cbc96cd52210260e6d0229ad74@milecki.pl>
On 3/31/21 2:36 PM, Rafał Miłecki wrote:
> On 2021-03-30 20:40, Florian Fainelli wrote:
>> The following changes since commit
>> fe07bfda2fb9cdef8a4d4008a409bb02f35f1bd8:
>>
>> Linux 5.12-rc1 (2021-02-28 16:05:19 -0800)
>>
>> are available in the Git repository at:
>>
>> https://github.com/Broadcom/stblinux.git
>> tags/arm-soc/for-5.13/devicetree
>>
>> for you to fetch changes up to dcb56d61d5a8acca0a357cc603397bc0272ce4cb:
>>
>> ARM: dts: BCM5301X: Set Linksys EA9500 power LED (2021-03-29
>> 11:43:45 -0700)
>
> This one seems a bit confusing.
>
> Command:
> git log arm-soc/for-5.13/devicetree
> shows me only 2 of mentioned commits
>
> Web UI:
> https://github.com/Broadcom/stblinux/releases/tag/arm-soc%2Ffor-5.13%2Fdevicetree
>
> references dcb56d6 but opening it shows page with a warning:
> "This commit does not belong to any branch on this repository, and may
> belong to a fork outside of the repository."
>
> My guess if you didn't push your local devicetree/next branch.
I did and then overwrote it, it should show up correctly now.
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-31 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 18:40 [GIT PULL 1/3] Broadcom devicetree changes for 5.13 Florian Fainelli
2021-03-30 18:40 ` [GIT PULL 2/3] Broadcom devicetree-arm64 " Florian Fainelli
2021-04-01 20:15 ` Arnd Bergmann
2021-03-30 18:40 ` [GIT PULL 3/3] Broadcom drivers " Florian Fainelli
2021-04-01 19:24 ` Arnd Bergmann
2021-03-31 21:36 ` [GIT PULL 1/3] Broadcom devicetree " Rafał Miłecki
2021-03-31 21:48 ` Florian Fainelli [this message]
2021-03-31 22:06 ` Rafał Miłecki
2021-03-31 22:08 ` Florian Fainelli
2021-04-01 20:15 ` Arnd Bergmann
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=c71b8949-b709-cb5b-b5a4-87cebf8cd8df@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--cc=soc@kernel.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