From: Doug Anderson <dianders@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <andy.gross@linaro.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: linux-next: Fixes tag needs some work in the qcom tree
Date: Thu, 7 Feb 2019 09:06:19 -0800 [thread overview]
Message-ID: <CAD=FV=U07_E6O96o4KrJGPaKvE4aSGb9OT6kCy7x40Q_-kGGOA@mail.gmail.com> (raw)
In-Reply-To: <20190208004721.129a9eb7@canb.auug.org.au>
Hi,
On Thu, Feb 7, 2019 at 5:47 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Andy,
>
> In commit
>
> 761f63b2ff21 ("arm64: dts: sdm845: Add clocks and iommus to WCN3990 WLAN node")
>
> Fixes tag
>
> Fixes: be7019103469 ("dts: arm64/sdm845: Add WCN3990 WLAN module device node")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean:
>
> 022bccb840b7 ("arm64: dts: sdm845: Add WCN3990 WLAN module device node")
+Bjorn
Looks like someone reorganized and/or rebased the tree after I sent
out my fix. When I check locally I have the old commit still and the
new:
commit be7019103469e6ccb997f932d3e0dce0141a0eda
Author: Govind Singh <govinds@codeaurora.org>
AuthorDate: Mon Nov 5 18:38:37 2018 +0530
Commit: Bjorn Andersson <bjorn.andersson@linaro.org>
CommitDate: Wed Jan 16 14:13:41 2019 -0800
dts: arm64/sdm845: Add WCN3990 WLAN module device node
Add device node for the ath10k SNOC platform driver probe
and add resources required for WCN3990 on SDM845 soc.
Reviewed-by: Brian Norris <briannorris@chromium.org>
Tested-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Govind Singh <govinds@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
---
commit 022bccb840b7ff9c64a70e81ac017d4d10bb8a9c
Author: Govind Singh <govinds@codeaurora.org>
AuthorDate: Mon Nov 5 18:38:37 2018 +0530
Commit: Andy Gross <andy.gross@linaro.org>
CommitDate: Thu Jan 24 22:19:20 2019 -0600
arm64: dts: sdm845: Add WCN3990 WLAN module device node
Add device node for the ath10k SNOC platform driver probe
and add resources required for WCN3990 on SDM845 soc.
Reviewed-by: Brian Norris <briannorris@chromium.org>
Tested-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Govind Singh <govinds@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
next prev parent reply other threads:[~2019-02-07 17:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 13:47 linux-next: Fixes tag needs some work in the qcom tree Stephen Rothwell
2019-02-07 17:06 ` Doug Anderson [this message]
2020-02-12 7:18 Stephen Rothwell
2021-01-21 7:41 Stephen Rothwell
2021-01-21 8:50 ` Robert Foss
2021-07-20 7:25 Stephen Rothwell
2021-09-20 22:24 Stephen Rothwell
2021-09-21 23:02 ` Stephen Rothwell
2021-09-21 23:31 ` Bjorn Andersson
2021-09-22 0:15 ` Stephen Rothwell
2021-11-22 21:08 Stephen Rothwell
2022-02-13 10:39 Stephen Rothwell
2022-02-13 11:52 ` Robert Marko
2022-02-13 21:02 ` Stephen Rothwell
2022-02-14 4:53 ` Bjorn Andersson
2022-02-16 9:59 ` Robert Marko
2022-03-09 12:10 Stephen Rothwell
2022-04-13 21:40 Stephen Rothwell
2022-04-14 15:03 ` Konrad Dybcio
2022-09-14 7:23 Stephen Rothwell
2022-10-03 20:13 Stephen Rothwell
2023-01-19 6:04 Stephen Rothwell
2023-02-05 21:09 Stephen Rothwell
2023-02-09 4:04 Stephen Rothwell
2023-02-09 10:02 ` Bartosz Golaszewski
2023-03-13 21:37 Stephen Rothwell
2023-03-14 21:15 Stephen Rothwell
2023-05-29 21:49 Stephen Rothwell
2023-05-30 14:56 ` Bjorn Andersson
2023-05-31 13:25 ` Linus Walleij
2023-07-23 22:53 Stephen Rothwell
2024-02-07 7:05 Stephen Rothwell
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='CAD=FV=U07_E6O96o4KrJGPaKvE4aSGb9OT6kCy7x40Q_-kGGOA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).