From: Vinod Koul <vkoul@kernel.org>
To: Justin Chen <justinpopo6@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Kishon Vijay Abraham I <kishon@ti.com>,
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 phy-next tree
Date: Mon, 7 Nov 2022 10:21:37 +0530 [thread overview]
Message-ID: <Y2iO2XbUPmewsrfH@matsya> (raw)
In-Reply-To: <CAJx26kX_fb6RMyVWQO7TntVTn9i3z2SzR0uXjUf4_zQczsmEeQ@mail.gmail.com>
On 06-11-22, 17:10, Justin Chen wrote:
> On Sun, Nov 6, 2022 at 1:12 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commits
> >
> > 5b679072af07 ("phy: usb: Fix clock imbalance for suspend/resume")
> > 219ec4e8f7b2 ("phy: usb: Use slow clock for wake enabled suspend")
> >
> > Fixes tag
> >
> > Fixes: ae532b2b7aa5 ("usb: Add "wake on" functionality for newer Synopsis XHCI controllers")
> >
> > has these problem(s):
> >
> > - Subject does not match target commit subject
Fixed now
> > Just use
> > git log -1 --format='Fixes: %h ("%s")'
> >
> Apologies, I missed the "phy:" in the beginning. Should be this.
> Fixes: ae532b2b7aa5 ("phy: usb: Add "wake on" functionality for newer
> Synopsis XHCI controllers")
Use the script above to generate this and not manually
>
> How should I fix this? Can this be fixed in place?
I have fixed it up
--
~Vinod
next prev parent reply other threads:[~2022-11-07 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 21:11 linux-next: Fixes tag needs some work in the phy-next tree Stephen Rothwell
2022-11-07 1:10 ` Justin Chen
2022-11-07 4:51 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-06 21:13 Stephen Rothwell
2022-11-07 4:50 ` Vinod Koul
2020-01-27 20:05 Stephen Rothwell
2020-01-28 4:52 ` Kishon Vijay Abraham I
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=Y2iO2XbUPmewsrfH@matsya \
--to=vkoul@kernel.org \
--cc=justinpopo6@gmail.com \
--cc=kishon@ti.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 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.