linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Miaoqian Lin <linmq006@gmail.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 tree
Date: Thu, 14 Apr 2022 10:46:29 +0530	[thread overview]
Message-ID: <YleuLWpFl02Mqeex@matsya> (raw)
In-Reply-To: <20220414073236.1f955bff@canb.auug.org.au>

On 14-04-22, 07:32, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   8724489e5ffc ("phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe")
> 
> Fixes tag
> 
>   Fixes: 71e2f5c ("phy: ti: Add a new SERDES driver for TI's AM654x SoC")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future by setting core.abbrev to 12 (or
>     more) or (for git v2.11 or later) just making sure it is not set
>     (or set to "auto").
> 
> In commit
> 
>   19974ef56750 ("phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe")
> 
> Fixes tag
> 
>   Fixes: f7f50b2 ("phy: mapphone-mdm6600: Add runtime PM support for n_gsm on USB suspend")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future by setting core.abbrev to 12 (or
>     more) or (for git v2.11 or later) just making sure it is not set
>     (or set to "auto").

Thanks fixed that..

Btw I am sure you have a script for this, can I get that. It would be
good to run that as part of patch tests before applying


-- 
~Vinod

  reply	other threads:[~2022-04-14  5:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 21:32 linux-next: Fixes tag needs some work in the phy tree Stephen Rothwell
2022-04-14  5:16 ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-23 20:24 Stephen Rothwell
2022-01-24  4:06 ` Vinod Koul
2019-06-03 14:02 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=YleuLWpFl02Mqeex@matsya \
    --to=vkoul@kernel.org \
    --cc=kishon@ti.com \
    --cc=linmq006@gmail.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;
as well as URLs for NNTP newsgroup(s).