From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tony Lindgren <tony@atomide•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Heiko Schocher <hs@denx•de>,
Arthur Demchenkov <spinal.by@gmail•com>
Subject: linux-next: Fixes tag needs some work in the omap-fixes tree
Date: Wed, 23 Jan 2019 16:32:09 +1100 [thread overview]
Message-ID: <20190123163209.6187fe78@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hi Tony,
In commit
5a1826e1b175 ("ARM: dts: am335x-shc.dts: fix wrong cd pin level")
Fixes tag
Fixes: e63201f19438 ("mmc: omap_hsmmc: Delete platform data
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
In commit
0b30afcb8948 ("ARM: dts: n900: fix mmc1 card detect gpio polarity")
Fixes tag
Fixes: e63201f19438 ("mmc: omap_hsmmc: Delete platform data GPIO
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes tags across more than one line.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-01-23 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 5:32 Stephen Rothwell [this message]
2019-01-23 21:14 ` linux-next: Fixes tag needs some work in the omap-fixes tree Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2019-09-10 14:08 Stephen Rothwell
2019-09-10 14:32 ` Tony Lindgren
2019-12-17 20:13 Stephen Rothwell
2019-12-17 23:23 ` Tony Lindgren
2020-11-10 21:16 Stephen Rothwell
2020-11-11 7:21 ` Tony Lindgren
2022-04-12 21:02 Stephen Rothwell
2022-04-13 6:21 ` H. Nikolaus Schaller
2022-04-14 8:46 ` 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=20190123163209.6187fe78@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hs@denx$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=spinal.by@gmail$(echo .)com \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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