From: Max Krummenacher <max.krummenacher@toradex.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"shawnguo@kernel.org" <shawnguo@kernel.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
Date: Tue, 19 Apr 2022 08:15:27 +0000 [thread overview]
Message-ID: <758f780b2176f9bc06f09a693a1605194ef22735.camel@toradex.com> (raw)
In-Reply-To: <20220419065027.1046eb04@canb.auug.org.au>
Am Dienstag, dem 19.04.2022 um 06:50 +1000 schrieb Stephen Rothwell:
> Hi all,
>
> In commit
>
> a5b99c8fcd1b ("ARM: dts: imx6dl-colibri: Fix I2C pinmuxing")
>
> Fixes tag
>
> Fixes: 56f0df6b6b58 ("ARM: dts: imx*(colibri|apalis): add missing
>
> has these problem(s):
>
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over more than one line. Also, keep all
> the commit message tags together at the end of the commit message.
>
Sorry about that. I've seen you already fixed it. Thanks a lot, appreciated.
Regards
Max
next prev parent reply other threads:[~2022-04-19 8:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 20:50 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2022-04-19 8:15 ` Max Krummenacher [this message]
-- 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-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=758f780b2176f9bc06f09a693a1605194ef22735.camel@toradex.com \
--to=max.krummenacher@toradex.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).