public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Qing Wang <wangqing@vivo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the dmaengine tree
Date: Tue, 26 Oct 2021 10:56:54 +0530	[thread overview]
Message-ID: <YXeRngM36dOi6AMK@matsya> (raw)
In-Reply-To: <20211026160657.63ceb380@canb.auug.org.au>

On 26-10-21, 16:06, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the dmaengine tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> 
> Caused by commit
> 
>   981b43434b28 ("message: fusion: switch from 'pci_' to 'dma_' API")
> 
> I have used the dmaengine tree from next-20211025 for today.

Thanks Stephen,

I have fixed it up (dropped the offending commit, which should not
anyway go thru dmaengine tree)

-- 
~Vinod

  parent reply	other threads:[~2021-10-26  5:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  5:06 linux-next: build failure after merge of the dmaengine tree Stephen Rothwell
2021-10-26  5:07 ` Stephen Rothwell
2021-10-26  5:26 ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-10  2:46 Stephen Rothwell
2022-06-10  4:32 ` Vinod Koul
2023-09-29  3:13 Stephen Rothwell
2023-10-02 16:09 ` Vinod Koul
2023-10-10  3:54 Stephen Rothwell
2023-10-10  6:59 ` Vinod Koul
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30   ` Vinod Koul

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=YXeRngM36dOi6AMK@matsya \
    --to=vkoul@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wangqing@vivo.com \
    /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