From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: arm-soc: Xilinx Zynq dt changes for v3.14
Date: Fri, 13 Dec 2013 14:25:17 +0100 [thread overview]
Message-ID: <52AB0ABD.1050307@monstr.eu> (raw)
In-Reply-To: <20131213112659.GD4360@n2100.arm.linux.org.uk>
Hi Russell,
On 12/13/2013 12:26 PM, Russell King - ARM Linux wrote:
> 1. Address it to arm at kernel.org; there's no need to copy arm-soc people
> individually. The whole point of arm at kernel.org is that it reaches
> the current arm-soc maintainers, whoever they may be at the time that
> you send your email without you needing to know who they are.
>
> 2. Include in the subject line not "arm-soc:" but [GIT PULL] to mark it as
> a pull request message.
Thanks, I will keep this in my mind for future. I am just doing what I have done
before and this is the first complain I have got.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131213/faae07da/attachment.sig>
next prev parent reply other threads:[~2013-12-13 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 8:33 arm-soc: Xilinx Zynq dt changes for v3.14 Michal Simek
2013-12-13 11:26 ` Russell King - ARM Linux
2013-12-13 13:25 ` Michal Simek [this message]
2013-12-17 20:27 ` Olof Johansson
2013-12-18 9:06 ` Michal Simek
2013-12-20 16:34 ` Kevin Hilman
2013-12-22 19:37 ` Olof Johansson
2013-12-27 4:43 ` Sören Brinkmann
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=52AB0ABD.1050307@monstr.eu \
--to=monstr@monstr.eu \
--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).