linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pavel Pisa <pisa@fel.cvut.cz>
Cc: Xu Yilun <yilun.xu@linux.intel.com>,
	jgg@nvidia.com, m.szyprowski@samsung.com, yilun.xu@intel.com,
	linux-fpga@vger.kernel.org, mdf@kernel.org,
	linux-kernel@vger.kernel.org, Michal Simek <michal.simek@amd.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH 1/1] fpga: zynq_fpga: Fix the wrong usage of dma_map_sgtable()
Date: Tue, 19 Aug 2025 07:25:57 +0200	[thread overview]
Message-ID: <2025081907-wireless-entail-08d5@gregkh> (raw)
In-Reply-To: <202508190039.02454.pisa@fel.cvut.cz>

On Tue, Aug 19, 2025 at 12:39:02AM +0200, Pavel Pisa wrote:
> Hello Greg and others,
> 
> please, is there some progress/decision about the fix for mainline?
> 
> Our daily test of mainline Linux kernel build and test of CAN
> communication latency on Zynq system with loaded CTU CAN FD
> IP core ends with unresponsive kernel. The last successful
> mainline build is from July 29
>  
>   run-250729-042256-hist+6.16.0-g283564a43383+oaat-kern.json
>   https://canbus.pages.fel.cvut.cz/can-latester/
> 
> I have analyzed the cause and reported (August 4) that mainline
> Zynq runtime FPGA bitstream loading was broken by patch
> 
>   37e00703228a ("zynq_fpga: use sgtable-based scatterlist wrappers")
> 
> Xu Yilun and others from the FPGA community reacted promptly
> with the fix on August 6. The fix has propagated into linux-next.
> Is there a plan to accept it for the 6.17 version, or would it be
> accepted only for 6.18?

It's in my "to apply" queue to get to for 6.17-final.

Please give us a chance to catch up, August is usually a time for
vacations :)

thanks,

greg k-h

  reply	other threads:[~2025-08-19  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  7:06 [PATCH 0/1] Last minute FPGA fix for v6.17-rc1 Xu Yilun
2025-08-06  7:06 ` [PATCH 1/1] fpga: zynq_fpga: Fix the wrong usage of dma_map_sgtable() Xu Yilun
2025-08-18 22:39   ` Pavel Pisa
2025-08-19  5:25     ` Greg KH [this message]
2025-08-23 18:39       ` Pavel Pisa

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=2025081907-wireless-entail-08d5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jgg@nvidia.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mdf@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=mkl@pengutronix.de \
    --cc=pisa@fel.cvut.cz \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.intel.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;
as well as URLs for NNTP newsgroup(s).