From: Ninad Palsule <ninad@linux.ibm.com>
To: jk@ozlabs.org, joel@jms.id.au, alistair@popple.id.au,
eajames@linux.ibm.com, linux-fsi@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Cc: Ninad Palsule <ninad@linux.ibm.com>
Subject: [PATCH v2 0/2] fsi: sbefifo: fixes
Date: Mon, 11 Sep 2023 17:38:07 -0500 [thread overview]
Message-ID: <20230911223809.3505431-1-ninad@linux.ibm.com> (raw)
Hello,
Please review the version 2 of patchset. I have incorporated review
comments by Joel.
Ninad Palsule (2):
fsi: sbefifo: Bump up user write cmd length
fsi: sbefifo: Validate pending user write
drivers/fsi/fsi-sbefifo.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.39.2
next reply other threads:[~2023-09-12 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 22:38 Ninad Palsule [this message]
2023-09-11 22:38 ` [PATCH v2 1/2] fsi: sbefifo: Bump up user write cmd length Ninad Palsule
2023-09-11 22:38 ` [PATCH v2 2/2] fsi: sbefifo: Validate pending user write Ninad Palsule
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=20230911223809.3505431-1-ninad@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox