From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: linux-kbuild@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kbuild: arm: Do not define "comma" twice
Date: Thu, 02 Oct 2014 15:11:05 +0200 [thread overview]
Message-ID: <542D4EE9.4010003@suse.cz> (raw)
In-Reply-To: <1408704737-16973-1-git-send-email-yamada.m@jp.panasonic.com>
On 2014-08-22 12:52, Masahiro Yamada wrote:
> The definition of "comma" exists in scripts/Kbuild.include.
> We should not double it.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: linux-arm-kernel@lists.infradead.org
I do not see the patch in linux-next, so I applied it to the kbuild tree.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: mmarek@suse.cz (Michal Marek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kbuild: arm: Do not define "comma" twice
Date: Thu, 02 Oct 2014 15:11:05 +0200 [thread overview]
Message-ID: <542D4EE9.4010003@suse.cz> (raw)
In-Reply-To: <1408704737-16973-1-git-send-email-yamada.m@jp.panasonic.com>
On 2014-08-22 12:52, Masahiro Yamada wrote:
> The definition of "comma" exists in scripts/Kbuild.include.
> We should not double it.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: linux-arm-kernel at lists.infradead.org
I do not see the patch in linux-next, so I applied it to the kbuild tree.
Michal
next prev parent reply other threads:[~2014-10-02 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 10:52 [PATCH] kbuild: arm: Do not define "comma" twice Masahiro Yamada
2014-08-22 10:52 ` Masahiro Yamada
2014-10-02 13:11 ` Michal Marek [this message]
2014-10-02 13:11 ` Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2015-01-13 6:53 Masahiro Yamada
2015-01-13 8:03 ` Sascha Hauer
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=542D4EE9.4010003@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.m@jp.panasonic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.