From: Michal Marek <mmarek@suse.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 2/9] KVM: arm: Do not indent the arguments of DECLARE_BITMAP
Date: Mon, 19 Oct 2015 14:07:19 +0200 [thread overview]
Message-ID: <5624DCF7.7000001@suse.com> (raw)
In-Reply-To: <20151019120556.GC24104@cbox>
On 2015-10-19 14:05, Christoffer Dall wrote:
> ok, I've taken the patch.
Thank you! I will remove it from my series.
Michal
next prev parent reply other threads:[~2015-10-19 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 20:16 [PATCH 0/9] scripts/tags.sh cleanup Michal Marek
2015-10-15 20:16 ` [PATCH 1/9] tags: Treat header files as C code Michal Marek
2015-10-15 20:16 ` [PATCH 2/9] KVM: arm: Do not indent the arguments of DECLARE_BITMAP Michal Marek
2015-10-18 20:34 ` Christoffer Dall
2015-10-19 11:55 ` Michal Marek
2015-10-19 12:05 ` Christoffer Dall
2015-10-19 12:07 ` Michal Marek [this message]
2015-10-15 20:16 ` [PATCH 3/9] aic7xxx: Avoid name collision with <linux/list.h> Michal Marek
2015-10-15 20:16 ` [PATCH 4/9] tags: Fix erroneous pattern match in a comment Michal Marek
2015-10-15 20:16 ` [PATCH 5/9] tags: Process Kconfig files in a single pass Michal Marek
2015-10-15 20:16 ` [PATCH 6/9] tags: Do not try to index defconfigs Michal Marek
2015-10-15 20:16 ` [PATCH 7/9] tags: Drop the _PE rule Michal Marek
2015-10-15 20:16 ` [PATCH 8/9] tags: Unify emacs and exuberant rules Michal Marek
2015-10-15 20:16 ` [PATCH 9/9] treewide: Remove newlines inside DEFINE_PER_CPU() macros Michal Marek
2015-10-21 19:27 ` Prarit Bhargava
2015-10-21 19:52 ` Michal Marek
2015-10-22 11:31 ` Prarit Bhargava
2015-10-22 12:06 ` Michal Marek
2015-10-22 12:14 ` Prarit Bhargava
2015-10-22 12:24 ` Michal Marek
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=5624DCF7.7000001@suse.com \
--to=mmarek@suse.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).