All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 imx-mxs tree
Date: Wed, 14 Sep 2022 11:48:49 +0800	[thread overview]
Message-ID: <20220914034849.GI1728671@dragon> (raw)
In-Reply-To: <CAJ+vNU2naFP=X1B3HwPCRez7Phft3OGA0sM6TMZUXJ78S5s6Aw@mail.gmail.com>

On Tue, Sep 13, 2022 at 10:08:16AM -0700, Tim Harvey wrote:
> On Tue, Sep 13, 2022 at 3:16 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > In commit
> >
> >   c1f84a75babe ("arm64: dts: imx8mp-venice-gw74xx: fix port/phy validation")
> >
> > Fixes tag
> >
> >   Fixes: 7899eb6cb15d ("arm64: dts: imx: Add i.MX8M Plus Gateworks gw7400
> >
> > has these problem(s):
> >
> >   - Subject has leading but no trailing parentheses
> >   - Subject has leading but no trailing quotes
> >
> > Please do not split Fixes tags over more than one line.
> >
> 
> Stephen,
> 
> Sorry, that was my fault with my editor's word-wrap getting in the
> way. I will be more careful in the future.
> 
> Is there anything that I can and should do at this point to result this one?

I fixed it up.

Shawn

  reply	other threads:[~2022-09-14  3:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 10:15 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2022-09-13 17:08 ` Tim Harvey
2022-09-14  3:48   ` Shawn Guo [this message]
2022-09-14 15:11     ` Tim Harvey
  -- 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-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-06-06 21:46 Stephen Rothwell
2019-06-07  0:24 ` Shawn Guo
2019-06-11  8:36   ` Peng Fan
2019-06-12 10:51     ` Shawn Guo
2019-06-12 12:15       ` Peng Fan
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=20220914034849.GI1728671@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tharvey@gateworks.com \
    /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.