From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andy Gross <agross@kernel.org>,
Kuogee Hsieh <khsieh@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the qcom tree
Date: Tue, 21 Sep 2021 16:31:38 -0700 [thread overview]
Message-ID: <YUprWiZNgPt2YEUl@ripper> (raw)
In-Reply-To: <20210922090235.2a626af6@canb.auug.org.au>
On Tue 21 Sep 16:02 PDT 2021, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 21 Sep 2021 08:24:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > In commit
> >
> > 33c4296d99ef ("arm64: dts: qcom: sc7280: fix display port phy reg property")
>
> This is now commit 1a5968e5b7de.
>
> > Fixes tag
> >
> > Fixes: 9886e8fd8438 ("arm64: dts: qcom: sc7280: Add USB related nodes")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: bb9efa59c665 ("arm64: dts: qcom: sc7280: Add USB related nodes")
>
> Surely if you are going to rebase the tree anyway, you can fix this up
> :-(
>
Yes of course!
I had made a git merge snafu earlier in the branch, fixed the fixes and
then fixed the snafu, which broke the fixes...
I should have double checked this before pushing out the rebased branch,
but it looks okay to me (and checkpatch) now.
Thanks,
Bjorn
next prev parent reply other threads:[~2021-09-21 23:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 22:24 linux-next: Fixes tag needs some work in the qcom tree Stephen Rothwell
2021-09-21 23:02 ` Stephen Rothwell
2021-09-21 23:31 ` Bjorn Andersson [this message]
2021-09-22 0:15 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-02-07 7:05 Stephen Rothwell
2023-07-23 22:53 Stephen Rothwell
2023-05-29 21:49 Stephen Rothwell
2023-05-30 14:56 ` Bjorn Andersson
2023-05-31 13:25 ` Linus Walleij
2023-03-14 21:15 Stephen Rothwell
2023-03-13 21:37 Stephen Rothwell
2023-02-09 4:04 Stephen Rothwell
2023-02-09 10:02 ` Bartosz Golaszewski
2023-02-05 21:09 Stephen Rothwell
2023-01-19 6:04 Stephen Rothwell
2022-10-03 20:13 Stephen Rothwell
2022-09-14 7:23 Stephen Rothwell
2022-04-13 21:40 Stephen Rothwell
2022-04-14 15:03 ` Konrad Dybcio
2022-03-09 12:10 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
2021-11-22 21:08 Stephen Rothwell
2021-07-20 7:25 Stephen Rothwell
2021-01-21 7:41 Stephen Rothwell
2021-01-21 8:50 ` Robert Foss
2020-02-12 7:18 Stephen Rothwell
2019-02-07 13:47 Stephen Rothwell
2019-02-07 17:06 ` Doug Anderson
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=YUprWiZNgPt2YEUl@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=khsieh@codeaurora.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 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.