From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: socfpga: dts: fix spi1 interrupt
Date: Thu, 19 Mar 2015 20:21:15 +0100 [thread overview]
Message-ID: <20150319192115.GA3229@pengutronix.de> (raw)
In-Reply-To: <550B0621.3070101@jamers.net>
On Thu, Mar 19, 2015 at 05:23:45PM +0000, Mark James wrote:
> Hi Dinh,
>
> Thank you for that - I thought I would be all good with what I sent having changed the settings in Thunderbird as per Documentation/email-clients.txt, evidently not! Will do some more reading before submitting any more patches.
>
"git send-email" is your friend ;-)
It does the right thing. (As long as the original git commit is correct
of course)
Regards,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2015-03-19 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 21:35 ARM: socfpga: dts: fix spi1 interrupt Mark James
2015-03-18 8:09 ` Steffen Trumtrar
2015-03-19 14:14 ` Dinh Nguyen
2015-03-19 17:23 ` Mark James
2015-03-19 19:21 ` Steffen Trumtrar [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=20150319192115.GA3229@pengutronix.de \
--to=s.trumtrar@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).