From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org
Subject: Re: sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib/iommu-co
Date: Sat, 18 Apr 2015 18:38:44 +0000 [thread overview]
Message-ID: <20150418183844.GA21225@oracle.com> (raw)
In-Reply-To: <5532A249.30703@roeck-us.net>
On (04/18/15 11:28), Guenter Roeck wrote:
>
> Some merge gone wrong, maybe ? I tried to revert f1600e549b94
> and apply http://patchwork.ozlabs.org/patch/459803/ instead.
That patch is a part-2 of a 3-part patch set. In order, this should
have been v10: applied as:
http://patchwork.ozlabs.org/patch/459804/
http://patchwork.ozlabs.org/patch/459803/
http://patchwork.ozlabs.org/patch/459802/
The mail thread for the 3-part patch set was here
http://www.spinics.net/lists/sparclinux/msg13785.html
I noticed that the existing dates on the iommu commits were also odd:
commit 671d773297969bebb1732e1cdc1ec03aa53c6be2
Author: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Thu Mar 12 20:02:37 2015 -0400
commit f1600e549b948a32ad7672e069b2915314637ae3
Author: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Thu Mar 12 20:02:36 2015 -0400
commit 10b88a4b17d31a7409494b179dcb76e7ab2fcaea
Author: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Thu Mar 12 20:02:35 2015 -0400
We have had many discussions of this patch set since March 12,
and the correct version should have been v10, dated something
after Apr 9, and acked by Benjamin Herrenschmidt.
next prev parent reply other threads:[~2015-04-18 18:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 5:47 sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib/iommu-common Guenter Roeck
2015-04-18 10:59 ` sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib/iommu-co Sowmini Varadhan
2015-04-18 12:05 ` Sowmini Varadhan
2015-04-18 18:28 ` Guenter Roeck
2015-04-18 18:38 ` Sowmini Varadhan [this message]
2015-04-18 19:27 ` David Miller
2015-04-18 19:40 ` David Miller
2015-04-18 19:44 ` Sowmini Varadhan
2015-04-18 19:55 ` Sowmini Varadhan
2015-04-18 21:41 ` David Miller
2015-04-19 4:13 ` Guenter Roeck
2015-04-19 4:23 ` Guenter Roeck
2015-04-19 10:51 ` Sowmini Varadhan
2015-04-19 18:09 ` David Miller
2015-04-18 19:25 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-04-19 18:36 Fwd: Re: sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib/iom Sowmini Varadhan
2015-04-20 3:01 ` Fwd: Re: sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib Michael Ellerman
2015-04-20 5:17 ` Guenter Roeck
2015-04-20 16:25 ` sparc64: Build failure due to commit f1600e549b94 (sparc: Make sparc64 use scalable lib/iommu-co David Miller
2015-04-20 16:44 ` Guenter Roeck
2015-04-20 16:50 ` David Miller
2015-04-21 1:54 ` Michael Ellerman
2015-04-21 2:32 ` Guenter Roeck
2015-04-21 3:25 ` Michael Ellerman
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=20150418183844.GA21225@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sparclinux@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).