From: Vinod Koul <vinod.koul@intel.com>
To: Mason <slash.tmp@free.fr>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
arm-soc <arm@kernel.org>, Emilio Lopez <emilio@elopez.com.ar>,
dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: 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
WARNING: multiple messages have this Message-ID (diff)
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: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 22:40 linux-next: build failure after merge of the arm tree Stephen Rothwell
2017-04-21 7:58 ` Mason
2017-04-21 7:58 ` Mason
2017-04-21 8:06 ` [PATCH] dmaengine: sun4i: fix invalid argument Mason
2017-04-21 8:06 ` Mason
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:24 ` Maxime Ripard
2017-04-21 8:43 ` [PATCH v2] " Mason
2017-04-21 8:43 ` Mason
2017-04-21 14:40 ` Maxime Ripard
2017-04-21 14:40 ` Maxime Ripard
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:12 ` Stephen Rothwell
2017-04-21 8:30 ` Mason
2017-04-21 8:30 ` Mason
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-21 23:43 ` Russell King - ARM Linux
2017-04-22 8:41 ` Mason
2017-04-22 8:41 ` Mason
2017-04-22 8:41 ` Mason
2017-04-24 4:20 ` Vinod Koul [this message]
2017-04-24 4:20 ` Vinod Koul
2017-04-26 22:34 ` [PATCH v2] arm: bitops: Align prototypes to generic API Mason
2017-04-26 22:34 ` Mason
2017-06-14 19:23 ` linux-next: build failure after merge of the arm tree Mason
2017-06-14 19:23 ` Mason
2017-04-21 11:27 ` Mason
2017-04-21 11:27 ` Mason
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 23:46 Stephen Rothwell
2024-11-13 0:25 ` Stephen Rothwell
2024-08-20 23:36 Stephen Rothwell
2024-08-21 3:27 ` liuyuntao (F)
2024-05-03 0:15 Stephen Rothwell
2024-05-03 8:18 ` Russell King (Oracle)
2024-05-03 8:23 ` Russell King (Oracle)
2024-05-03 12:08 ` Stephen Rothwell
2024-05-03 12:29 ` Russell King (Oracle)
2022-08-31 9:10 Stephen Rothwell
2022-08-31 9:14 ` Matija Glavinic Pecotic
2021-10-25 23:25 Stephen Rothwell
2020-01-19 21:24 Stephen Rothwell
2020-01-19 21:31 ` Stephen Rothwell
2020-01-19 22:02 ` Russell King - ARM Linux admin
2015-05-29 1:09 Stephen Rothwell
2014-04-10 1:35 Stephen Rothwell
2011-03-02 14:13 Stephen Rothwell
2011-03-02 15:55 ` Nicolas Pitre
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=arm@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=sfr@canb.auug.org.au \
--cc=slash.tmp@free.fr \
--cc=wens@csie.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.