From: "Andreas Färber" <afaerber@suse.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Tarek Dakhran <t.dakhran@samsung.com>,
Kevin Hilman <khilman@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
"OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Ben Dooks <ben-linux@fluff.org>,
Kumar Gala <galak@codeaurora.org>,
"ARM/SAMSUNG ARM A..." <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: exynos5410: Fill in CPU clock-frequency
Date: Tue, 15 Jul 2014 14:57:14 +0200 [thread overview]
Message-ID: <53C5252A.2040301@suse.de> (raw)
In-Reply-To: <53B7175B.1030109@samsung.com>
Hi Kukjin,
Am 04.07.2014 23:06, schrieb Kukjin Kim:
> BTW Andreas, I can't use 'Färber' in my git tree so which one is right
> or more preferred? Farber, Faerber, Ferber? Sorry.
Hm, git-am should in theory just work fine for this patch with UTF-8 on
Linux. As for Reviewed-by / Tested-by, some people had success with
copy&paste, otherwise Faerber as in the email please.
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-07-15 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 19:49 [PATCH] ARM: dts: exynos5410: Fill in CPU clock-frequency Andreas Färber
2014-06-23 7:53 ` Tarek Dakhran
2014-07-04 11:32 ` Andreas Färber
2014-07-04 21:06 ` Kukjin Kim
2014-07-15 12:57 ` Andreas Färber [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=53C5252A.2040301@suse.de \
--to=afaerber@suse.de \
--cc=ben-linux@fluff.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene.kim@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=t.dakhran@samsung.com \
/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).