From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: linux-omap@vger.kernel.org, stable@vger.kernel.org,
adam.ford@logicpd.com
Subject: Re: [PATCH] ARM:DTS:OMAP3:Fix Card Detect and Write Protect on Logic PD SOM-LV
Date: Tue, 17 Jan 2017 13:53:33 -0800 [thread overview]
Message-ID: <20170117215332.GU7403@atomide.com> (raw)
In-Reply-To: <1484681646-16124-1-git-send-email-aford173@gmail.com>
* Adam Ford <aford173@gmail.com> [170117 11:36]:
> This fixes commit ab8dd3aed011 ("ARM: DTS: Add minimal Support for
> Logic PD DM3730 SOM-LV") where the Card Detect and Write Protect
> pins were improperly configured.
OK applying into omap-for-v4.10/fixes. I corrected the following:
- Unified the subject to start with "ARM: dts: omap3: ..."
- Added a Fixes: tag
Can you please check those next time so I don't have to manually
edit patches?
Thanks,
Tony
prev parent reply other threads:[~2017-01-17 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 19:34 [PATCH] ARM:DTS:OMAP3:Fix Card Detect and Write Protect on Logic PD SOM-LV Adam Ford
2017-01-17 21:53 ` Tony Lindgren [this message]
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=20170117215332.GU7403@atomide.com \
--to=tony@atomide.com \
--cc=adam.ford@logicpd.com \
--cc=aford173@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=stable@vger.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).