linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>, 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 imx-mxs tree
Date: Tue, 11 Jun 2019 08:36:52 +0000	[thread overview]
Message-ID: <AM0PR04MB44817EB65913F29630453E1A88ED0@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190607002407.GY29853@dragon>

Hi Shawn, Stephen
> Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
> 
> On Fri, Jun 07, 2019 at 07:46:52AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> >   f6a8ff82ce68 ("clk: imx: imx8mm: correct audio_pll2_clk to
> > audio_pll2_out")
> >
> > Fixes tag
> >
> >   Fixes: ba5625c3e27 ("clk: imx: Add clock driver support for imx8mm")
> >
> > has these problem(s):
> >
> >   - SHA1 should be at least 12 digits long
> >     Can be fixed 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").
> 
> Hi Stephen,
> 
> Thanks for reporting.  I just got it fixed, will be more careful about that in the
> future.
> 
> @Peng, please check your git configuration as suggested above, thanks.

Sorry for this. Do I need to resend the patch?

Thanks,
Peng.

> 
> Shawn

  reply	other threads:[~2019-06-11  8:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 21:46 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2019-06-07  0:24 ` Shawn Guo
2019-06-11  8:36   ` Peng Fan [this message]
2019-06-12 10:51     ` Shawn Guo
2019-06-12 12:15       ` Peng Fan
  -- strict thread matches above, loose matches on Subject: below --
2023-12-06  4:47 Stephen Rothwell
2023-12-06  5:25 ` Shawn Guo
2023-11-27  4:25 Stephen Rothwell
2022-10-24  4:37 Stephen Rothwell
2022-10-24  6:50 ` Francesco Dolcini
2022-10-24  7:07 ` Marcel Ziswiler
2022-10-29  8:27   ` Shawn Guo
2022-09-13 10:15 Stephen Rothwell
2022-09-13 17:08 ` Tim Harvey
2022-09-14  3:48   ` Shawn Guo
2022-09-14 15:11     ` Tim Harvey
2022-09-05 21:37 Stephen Rothwell
2022-09-06  7:22 ` Marcel Ziswiler
2022-09-06  7:49   ` Shawn Guo
2022-06-13 21:41 Stephen Rothwell
2022-04-18 20:50 Stephen Rothwell
2022-04-19  8:15 ` Max Krummenacher
2022-01-29 23:18 Stephen Rothwell
2021-07-14 22:04 Stephen Rothwell
2021-07-15 11:03 ` Shawn Guo
2020-11-01 21:24 Stephen Rothwell
2020-11-02  0:02 ` Shawn Guo
2020-11-02  8:47   ` Oleksij Rempel
2019-01-16 20:54 Stephen Rothwell
2019-01-17  0:36 ` Shawn Guo

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=AM0PR04MB44817EB65913F29630453E1A88ED0@AM0PR04MB4481.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shawnguo@kernel.org \
    /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).