From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: "hch@lst.de" <hch@lst.de>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
arcml <linux-snps-arc@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>arcml
<linux-snps-arc@lists.infradead.org>
Subject: Re: + arc-convert-to-dma_map_ops.patch added to -mm tree
Date: Thu, 17 Dec 2015 10:58:55 +0530 [thread overview]
Message-ID: <56724817.7090003@synopsys.com> (raw)
In-Reply-To: <20151124075047.GA29572@lst.de>
On Tuesday 24 November 2015 01:20 PM, hch@lst.de wrote:
> Hi Vineet,
>
> the original version went through the buildbot, which succeeded. It seems
> like the official buildbot does not support arc, and might benefit from
> helping to set up an arc environment. However in the meantime Guenther
> send me output from his buildbot and I sent a fix for arc.
>
Hi Andrew, Christoph
The dma mapping conversion build error fixlet (below) exists as a separate patch
which will break bisectability. Will it be possible to squash it into the orig commit.
Thx,
-Vineet
commit 7f33b4a409493b81c24741dbad6700aae99d8ed0
Author: Christoph Hellwig <hch@lst.de>
Date: Fri Dec 11 15:59:33 2015 +1100
arc: dma mapping fixes
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reported-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
next prev parent reply other threads:[~2015-12-17 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <564b9e3a.DaXj5xWV8Mzu1fPX%akpm@linux-foundation.org>
2015-11-24 4:21 ` + arc-convert-to-dma_map_ops.patch added to -mm tree Vineet Gupta
2015-11-24 7:50 ` hch
2015-11-24 9:46 ` Vineet Gupta
2015-11-24 11:01 ` Michael Ellerman
2015-11-24 11:39 ` Vineet Gupta
2015-11-26 7:04 ` Michael Ellerman
2015-12-17 5:28 ` Vineet Gupta [this message]
2015-12-17 5:43 ` Andrew Morton
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=56724817.7090003@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-snps-arc@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).