All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Ivan Bornyakov <i.bornyakov@metrotek.ru>
Cc: linux-fpga@vger.kernel.org,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Moritz Fischer" <mdf@kernel.org>, "Wu Hao" <hao.wu@intel.com>,
	"Tom Rix" <trix@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	linux-kernel@vger.kernel.org, system@metrotek.ru
Subject: Re: [PATCH v5 0/3] Reliability improvements for Microchip MPF FPGA manager
Date: Mon, 9 Jan 2023 14:13:16 +0800	[thread overview]
Message-ID: <Y7uwfCPAl15Db8G6@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20230109054742.ola6gafnn2ikyuqa@x260>

On 2023-01-09 at 08:47:42 +0300, Ivan Bornyakov wrote:
> On Fri, Dec 30, 2022 at 12:29:19PM +0300, Ivan Bornyakov wrote:
> > A couple of reliability improvements for Microchip Polarfire FPGA
> > manager:
> >  * move SPI I/O buffers out of stack
> >  * rewrite status polling routine in a time measurable way
> > 
> > Also improve mpf_ops_write() code readability by separating single data
> > frame writing routine.
> > 
> > ChangeLog:
> >   v1:
> > [https://lore.kernel.org/linux-fpga/20221223123854.8023-1-i.bornyakov@metrotek.ru/]
> >   v2:
> >     * split into 3 distinct patches
> > [https://lore.kernel.org/linux-fpga/20221226142326.8111-1-i.bornyakov@metrotek.ru/]
> >   v3:
> >     * fix polling stop condition in mpf_poll_status() as Ilpo suggested.
> > [https://lore.kernel.org/linux-fpga/20221227100450.2257-1-i.bornyakov@metrotek.ru/]
> >   v4:
> >     * more verbose comment for mpf_poll_status()
> > [https://lore.kernel.org/linux-fpga/20221229104604.2496-1-i.bornyakov@metrotek.ru/]
> >   v5:
> >     * revord "fpga: microchip-spi: move SPI I/O buffers out of stack"
> >       commit message "Use allocated buffers" -> "Use cacheline aligned
> >       buffers"
> >     * drop __aligned(ARCH_KMALLOC_MINALIGN) attribute of struct mpf_priv
> >       member "rx". tx and rx are used synchronously by dma, they could
> >       share a cacheline.
> > 
> > Ivan Bornyakov (3):
> >   fpga: microchip-spi: move SPI I/O buffers out of stack
> >   fpga: microchip-spi: rewrite status polling in a time measurable way
> >   fpga: microchip-spi: separate data frame write routine
> > 
> >  drivers/fpga/microchip-spi.c | 145 +++++++++++++++++++----------------
> >  1 file changed, 79 insertions(+), 66 deletions(-)
> > 
> > -- 
> > 2.38.2
> > 
> 
> Friendly ping.
> 

Patch #1 is good to me now. And applied this series to for-next

Thanks,
Yilun

      reply	other threads:[~2023-01-09  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  9:29 [PATCH v5 0/3] Reliability improvements for Microchip MPF FPGA manager Ivan Bornyakov
2022-12-30  9:29 ` [PATCH v5 1/3] fpga: microchip-spi: move SPI I/O buffers out of stack Ivan Bornyakov
2022-12-30  9:29 ` [PATCH v5 2/3] fpga: microchip-spi: rewrite status polling in a time measurable way Ivan Bornyakov
2022-12-30  9:29 ` [PATCH v5 3/3] fpga: microchip-spi: separate data frame write routine Ivan Bornyakov
2023-01-09  5:47 ` [PATCH v5 0/3] Reliability improvements for Microchip MPF FPGA manager Ivan Bornyakov
2023-01-09  6:13   ` Xu Yilun [this message]

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=Y7uwfCPAl15Db8G6@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=conor.dooley@microchip.com \
    --cc=hao.wu@intel.com \
    --cc=i.bornyakov@metrotek.ru \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=system@metrotek.ru \
    --cc=trix@redhat.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 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.