From: Michael Zaidman <michael.zaidman@gmail.com>
To: Daniel Beer <daniel.beer@igorinstitute.com>,
Christina Quast <contact@christina-quast.de>
Cc: linux-serial@vger.kernel.org, ilpo.jarvinen@linux.intel.com,
johan@kernel.org, gregkh@linuxfoundation.org,
David Lamparter <equinox@diac24.net>,
Jiri Kosina <jikos@kernel.org>,
Michael Zaidman <michael.zaidman@gmail.com>
Subject: Re: [PATCH v4 RESEND] hid-ft260: Add serial driver
Date: Wed, 31 Jan 2024 17:48:55 +0200 [thread overview]
Message-ID: <Zbpr531rSxCsDKck@m2> (raw)
In-Reply-To: <ZbnoiUhM7sOt7/a6@fermat.nev>
On Wed, Jan 31, 2024 at 07:28:25PM +1300, Daniel Beer wrote:
> On Mon, Jan 29, 2024 at 12:07:48AM +0200, Michael Zaidman wrote:
> > I pushed changes into https://github.com/MichaelZaidman/hid-ft260/tree/uart
> > branch and would appreciate your review and feedback before preparing the
> > cumulative patch set.
> >
> > I addressed the first FIXME. Please correct me if I did not get right what
> > you meant.
> >
> > I am still doubting regarding the second FIXME. I see only three tty drivers
> > are using the kfifo_avail and kfifo_len to retrieve the write room and number
> > of chars in the buffer, and neither use locking. What was your concern?
>
> I don't see anything obviously wrong, but I'm probably not the best
> person to be reviewing this -- Christina has spent the most time on it
> recently, and I think the FIXME comments are hers.
>
Thanks, Daniel, for your feedback.
I see, it's my mistake. I should have reached out to both of you.
I added multiple fine-grained commits to simplify the review.
Christina, can you clarify the FIXME issue and review the changes?
Thanks,
Michael
next prev parent reply other threads:[~2024-01-31 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:31 [PATCH v4 RESEND] hid-ft260: Add serial driver Christina Quast
2023-12-28 11:50 ` Christina Quast
2024-01-02 21:42 ` Michael Zaidman
2024-01-16 21:44 ` Michael Zaidman
2024-01-16 21:34 ` Michael Zaidman
2024-01-16 21:43 ` Daniel Beer
2024-01-17 20:43 ` Michael Zaidman
2024-01-20 18:41 ` Michael Zaidman
2024-01-20 22:13 ` Daniel Beer
2024-01-21 9:12 ` Michael Zaidman
2024-01-28 22:07 ` Michael Zaidman
2024-01-31 6:28 ` Daniel Beer
2024-01-31 15:48 ` Michael Zaidman [this message]
[not found] ` <041c7445-fd59-4615-bb9a-7958b93113e8@christina-quast.de>
2024-02-02 9:04 ` Michael Zaidman
2024-02-10 22:03 ` Michael Zaidman
2024-02-01 11:07 ` Christina Quast
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=Zbpr531rSxCsDKck@m2 \
--to=michael.zaidman@gmail.com \
--cc=contact@christina-quast.de \
--cc=daniel.beer@igorinstitute.com \
--cc=equinox@diac24.net \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=johan@kernel.org \
--cc=linux-serial@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