From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure after merge of the arm tree
Date: Mon, 24 Apr 2017 09:50:33 +0530 [thread overview]
Message-ID: <20170424042033.GC6263@localhost> (raw)
In-Reply-To: <f89b6045-8c09-f6c4-3893-84f172260926@free.fr>
On Sat, Apr 22, 2017 at 10:41:37AM +0200, Mason wrote:
> On 22/04/2017 01:43, Russell King - ARM Linux wrote:
>
> > Or I drop the offending patch (done) and we get the DMA subsystem fixed
> > first. Given how long it's been this way, I doubt there's any hurry to
> > get this change in for the next merge window.
>
> Your solution makes sense.
>
> Vinod, could you apply [PATCH v2] dmaengine: sun4i: fix invalid argument
> to your tree when you have the time?
Done now..
--
~Vinod
next prev parent reply other threads:[~2017-04-24 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170421084033.5c987e13@canb.auug.org.au>
2017-04-21 7:58 ` linux-next: build failure after merge of the arm tree Mason
2017-04-21 8:06 ` [PATCH] dmaengine: sun4i: fix invalid argument Mason
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:43 ` [PATCH v2] " Mason
2017-04-21 14:40 ` Maxime Ripard
2017-04-21 8:12 ` linux-next: build failure after merge of the arm tree Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul [this message]
2017-04-26 22:34 ` [PATCH v2] arm: bitops: Align prototypes to generic API Mason
2017-06-14 19:23 ` linux-next: build failure after merge of the arm tree Mason
2017-04-21 11:27 ` Mason
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=20170424042033.GC6263@localhost \
--to=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox