From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: fix vdsomunge not to depend on glibc specific byteswap.h
Date: Thu, 15 Oct 2015 12:23:05 -0500 [thread overview]
Message-ID: <561FE0F9.8010201@mentor.com> (raw)
In-Reply-To: <585048FA-B498-4F84-AC09-642D95D7E8D9@goldelico.com>
On 10/15/2015 12:16 PM, H. Nikolaus Schaller wrote:
> Does this mean it is ok now in V3 in all cases? I have switched my patch editor
> tool from indirect git imap-send to git send-email (which appears to be more
> compatible).
v3 applied without issue, so yes, in that respect it is fine.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Will Deacon <will.deacon@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <marek@goldelico.com>
Subject: Re: [PATCH v2] ARM: fix vdsomunge not to depend on glibc specific byteswap.h
Date: Thu, 15 Oct 2015 12:23:05 -0500 [thread overview]
Message-ID: <561FE0F9.8010201@mentor.com> (raw)
In-Reply-To: <585048FA-B498-4F84-AC09-642D95D7E8D9@goldelico.com>
On 10/15/2015 12:16 PM, H. Nikolaus Schaller wrote:
> Does this mean it is ok now in V3 in all cases? I have switched my patch editor
> tool from indirect git imap-send to git send-email (which appears to be more
> compatible).
v3 applied without issue, so yes, in that respect it is fine.
next prev parent reply other threads:[~2015-10-15 17:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1443628457.git.hns@goldelico.com>
2015-09-30 15:56 ` [PATCH] ARM: fix vdsomunge depends on glibc specific byteswap.h H. Nikolaus Schaller
2015-09-30 15:56 ` H. Nikolaus Schaller
2015-09-30 16:02 ` Ard Biesheuvel
2015-09-30 16:02 ` Ard Biesheuvel
2015-09-30 16:13 ` H. Nikolaus Schaller
2015-09-30 16:13 ` H. Nikolaus Schaller
2015-09-30 16:17 ` Ard Biesheuvel
2015-09-30 16:17 ` Ard Biesheuvel
2015-09-30 17:25 ` H. Nikolaus Schaller
2015-09-30 17:25 ` H. Nikolaus Schaller
2015-09-30 17:37 ` Nathan Lynch
2015-09-30 17:37 ` Nathan Lynch
2015-09-30 17:47 ` H. Nikolaus Schaller
2015-09-30 17:47 ` H. Nikolaus Schaller
2015-09-30 18:17 ` Nathan Lynch
2015-09-30 18:17 ` Nathan Lynch
2015-09-30 19:08 ` H. Nikolaus Schaller
2015-09-30 19:08 ` H. Nikolaus Schaller
[not found] ` <cover.1443791320.git.hns@goldelico.com>
2015-10-02 13:10 ` [PATCH] ARM: fix vdsomunge not to depend " H. Nikolaus Schaller
2015-10-03 8:20 ` H. Nikolaus Schaller
2015-10-03 20:46 ` [PATCH v2] " H. Nikolaus Schaller
2015-10-03 20:46 ` H. Nikolaus Schaller
2015-10-14 12:47 ` H. Nikolaus Schaller
2015-10-14 12:47 ` H. Nikolaus Schaller
2015-10-14 14:16 ` Nathan Lynch
2015-10-14 14:16 ` Nathan Lynch
2015-10-15 5:52 ` H. Nikolaus Schaller
2015-10-15 5:52 ` H. Nikolaus Schaller
2015-10-15 16:37 ` Russell King - ARM Linux
2015-10-15 16:37 ` Russell King - ARM Linux
2015-10-15 16:52 ` H. Nikolaus Schaller
2015-10-15 16:52 ` H. Nikolaus Schaller
2015-10-15 17:07 ` Nathan Lynch
2015-10-15 17:07 ` Nathan Lynch
2015-10-15 17:16 ` H. Nikolaus Schaller
2015-10-15 17:16 ` H. Nikolaus Schaller
2015-10-15 17:23 ` Nathan Lynch [this message]
2015-10-15 17:23 ` Nathan Lynch
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=561FE0F9.8010201@mentor.com \
--to=nathan_lynch@mentor.com \
--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 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.