All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	llvm@lists.linux.dev
Subject: Re: [GIT PULL]: dmaengine updates for v6.8
Date: Fri, 19 Jan 2024 17:01:37 +0530	[thread overview]
Message-ID: <ZapdmU1vdA5BCulf@matsya> (raw)
In-Reply-To: <20240118191148.GA3329935@dev-arch.thelio-3990X>

Hi Nathan,

On 18-01-24, 12:11, Nathan Chancellor wrote:
> > Jan Kuliga (8):
> >       dmaengine: xilinx: xdma: Get rid of unused code
> >       dmaengine: xilinx: xdma: Add necessary macro definitions
> >       dmaengine: xilinx: xdma: Ease dma_pool alignment requirements
> >       dmaengine: xilinx: xdma: Rework xdma_terminate_all()
> >       dmaengine: xilinx: xdma: Add error checking in xdma_channel_isr()
> >       dmaengine: xilinx: xdma: Add transfer error reporting
> >       dmaengine: xilinx: xdma: Prepare the introduction of interleaved DMA transfers
> >       dmaengine: xilinx: xdma: Implement interleaved DMA transfers
> 
> This pull request appears to be missing some fixes for the clang
> warnings introduced by this series, which will break the build with
> CONFIG_WERROR=y:
> 
> https://lore.kernel.org/20231222-dma-xilinx-xdma-clang-fixes-v1-0-84a18ff184d2@kernel.org/

Sorry my bad to have missed these fixes, picking them now...

-- 
~Vinod

  reply	other threads:[~2024-01-19 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 17:24 [GIT PULL]: dmaengine updates for v6.8 Vinod Koul
2024-01-18 19:11 ` Nathan Chancellor
2024-01-19 11:31   ` Vinod Koul [this message]
2024-01-20 19:37 ` Vinod Koul
2024-01-20 23:08   ` pr-tracker-bot
2024-01-20 23:08 ` pr-tracker-bot

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=ZapdmU1vdA5BCulf@matsya \
    --to=vkoul@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=torvalds@linux-foundation.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.