From: Tony Lindgren <tony@atomide.com>
To: 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>,
Adam Ford <aford173@gmail.com>
Subject: Re: linux-next: Fixes tag needs some work in the omap-fixes tree
Date: Tue, 10 Sep 2019 07:32:04 -0700 [thread overview]
Message-ID: <20190910143204.GR52127@atomide.com> (raw)
In-Reply-To: <20190911000818.6539fd35@canb.auug.org.au>
Hi,
* Stephen Rothwell <sfr@canb.auug.org.au> [190910 14:25]:
> Hi all,
>
> In commit
>
> a932b77b4d19 ("ARM: dts: logicpd-som-lv: Fix i2c2 and i2c3 Pin mux")
>
> Fixes tag
>
> Fixes: 5fe3c0fa0d54 ("ARM: dts: Add pinmuxing for i2c2 and i2c3
>
> 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 (and also just
> keep them with all the other tags).
Oops sorry I missed that again, will try to be more careful
the next time. I really should have some automated checks
in place for that..
Regards,
Tony
next prev parent reply other threads:[~2019-09-10 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:08 linux-next: Fixes tag needs some work in the omap-fixes tree Stephen Rothwell
2019-09-10 14:32 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-12 21:02 Stephen Rothwell
2022-04-13 6:21 ` H. Nikolaus Schaller
2022-04-14 8:46 ` Tony Lindgren
2020-11-10 21:16 Stephen Rothwell
2020-11-11 7:21 ` Tony Lindgren
2019-12-17 20:13 Stephen Rothwell
2019-12-17 23:23 ` Tony Lindgren
2019-01-23 5:32 Stephen Rothwell
2019-01-23 21:14 ` Tony Lindgren
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=20190910143204.GR52127@atomide.com \
--to=tony@atomide.com \
--cc=aford173@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).