From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the thunderbolt-fixes tree
Date: Fri, 14 Jun 2019 14:28:02 +0300 [thread overview]
Message-ID: <20190614112802.GE2640@lahna.fi.intel.com> (raw)
In-Reply-To: <20190614211933.25c1b792@canb.auug.org.au>
On Fri, Jun 14, 2019 at 09:19:33PM +1000, Stephen Rothwell wrote:
> Hi Mika,
Hi,
> In commit
>
> e00367a43c56 ("thunderbolt: Implement CIO reset correctly for Titan Ridge")
>
> Fixes tag
>
> Fixes: 4630d6ae6e3 ("thunderbolt: Start firmware on Titan Ridge Apple systems")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Did you mean
>
> Fixes: c4630d6ae6e3 ("thunderbolt: Start firmware on Titan Ridge Apple systems")
Indeed that's the correct one. I've fixed it up now. Thanks!
prev parent reply other threads:[~2019-06-14 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 11:19 linux-next: Fixes tag needs some work in the thunderbolt-fixes tree Stephen Rothwell
2019-06-14 11:28 ` Mika Westerberg [this message]
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=20190614112802.GE2640@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--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