linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zhangfei.gao@linaro.org (zhangfei)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] ARM: multi_v7_defconfig: add driver support for hix5hd2
Date: Fri, 28 Nov 2014 23:21:54 +0800	[thread overview]
Message-ID: <54789312.1010804@linaro.org> (raw)
In-Reply-To: <44903559.5EVSLnOq11@wuerfel>



On 11/28/2014 11:17 PM, Arnd Bergmann wrote:
> On Friday 28 November 2014 23:15:48 zhangfei wrote:
>> On 11/28/2014 11:07 PM, Arnd Bergmann wrote:
>>> On Tuesday 25 November 2014, Zhangfei Gao wrote:
>>>> Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
>>>>
>>>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>>>
>>> Applied to next/defconfig, thanks!
>>>
>>> You mentioned earlier that you'd like me to apply this patch so I took it, but
>>> you did not send it to arm at kernel.org or ask for it to be applied in the email,
>>> so there was still a chance for it to get lost. Please try to be explict
>>> about these things as you can.
>>>
>>
>> Thanks Arnd
>>
>> Usually, should this info be listed in the git msg or reply with the
>> original patch?
>
> The best way to do this is to put it under the '---' line that separates
> the changelog part of the patch from the additional info like the diffstat.
>
> If you are sending more than one patch at once, use a [PATCH 0/x] introductory
> mail and put it in there.
>

Thanks Arnd for the kind education.

      reply	other threads:[~2014-11-28 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  7:37 [PATCH v1] ARM: multi_v7_defconfig: add driver support for hix5hd2 Zhangfei Gao
2014-11-28 15:07 ` Arnd Bergmann
2014-11-28 15:15   ` zhangfei
2014-11-28 15:17     ` Arnd Bergmann
2014-11-28 15:21       ` zhangfei [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=54789312.1010804@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --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).