From: Michael Zaidman <michael.zaidman@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-i2c@vger.kernel.org, Enrik.Berkhan@inka.de,
Michael Zaidman <michael.zaidman@gmail.com>,
Andrew Robertson <andrew.robertson@ftdichip.com>
Subject: Re: [PATCH v4 00/13] HID: ft260: fixes and performance improvements
Date: Fri, 11 Nov 2022 19:13:18 +0200 [thread overview]
Message-ID: <Y26CrhASiOuPXOl3@michael-VirtualBox> (raw)
In-Reply-To: <nycvar.YFH.7.76.2211111109490.6045@cbobk.fhfr.pm>
On Fri, Nov 11, 2022 at 11:19:32AM +0100, Jiri Kosina wrote:
> On Sat, 5 Nov 2022, Michael Zaidman wrote:
>
> > This patch series is an updated version of this one:
> > https://lore.kernel.org/all/20221030203403.4637-1-michael.zaidman@gmail.com/
> >
> > Changes since v3:
> > - Fixes for the kernel CI bot warnings
> > - We now do not miss NACK on the wakeup from the power saving mode
> > on the KVM installation reported by Enrik. For details, see
> > https://github.com/MichaelZaidman/hid-ft260/pull/7
> >
> > Changes since v2:
> >
> > - Remove SMBus Quick command support
> > - Missed NACK from big i2c read
> > - Wake up device from power saving mode
> > - Fix a NULL pointer dereference in ft260_i2c_write
> > - Missed NACK from busy device
> >
> > Changes since v1:
> >
> > - Do not populate hidraw device
> > - Avoid stale read buffer pointer
> >
> > Michael Zaidman (13):
> > HID: ft260: ft260_xfer_status routine cleanup
> > HID: ft260: improve i2c write performance
> > HID: ft260: support i2c writes larger than HID report size
> > HID: ft260: support i2c reads greater than HID report size
> > HID: ft260: improve i2c large reads performance
> > HID: ft260: do not populate /dev/hidraw device
> > HID: ft260: skip unexpected HID input reports
> > HID: ft260: remove SMBus Quick command support
> > HID: ft260: missed NACK from big i2c read
> > HID: ft260: wake up device from power saving mode
> > HID: ft260: fix a NULL pointer dereference in ft260_i2c_write
> > HID: ft260: missed NACK from busy device
> > HID: ft260: fix sparse warnings
>
> Hi Michael,
>
> this is now queued in hid.git#for-6.2/ft260.
>
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
Thanks, Jiri! Much appreciated.
Michael
prev parent reply other threads:[~2022-11-11 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 21:11 [PATCH v4 00/13] HID: ft260: fixes and performance improvements Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 01/13] HID: ft260: ft260_xfer_status routine cleanup Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 02/13] HID: ft260: improve i2c write performance Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 03/13] HID: ft260: support i2c writes larger than HID report size Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 04/13] HID: ft260: support i2c reads greater " Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 05/13] HID: ft260: improve i2c large reads performance Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 06/13] HID: ft260: do not populate /dev/hidraw device Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 07/13] HID: ft260: skip unexpected HID input reports Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 08/13] HID: ft260: remove SMBus Quick command support Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 09/13] HID: ft260: missed NACK from big i2c read Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 10/13] HID: ft260: wake up device from power saving mode Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 11/13] HID: ft260: fix a NULL pointer dereference in ft260_i2c_write Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 12/13] HID: ft260: missed NACK from busy device Michael Zaidman
2022-11-05 21:11 ` [PATCH v4 13/13] HID: ft260: fix 'cast to restricted' kernel CI bot warnings Michael Zaidman
2022-11-11 10:19 ` [PATCH v4 00/13] HID: ft260: fixes and performance improvements Jiri Kosina
2022-11-11 17:13 ` Michael Zaidman [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=Y26CrhASiOuPXOl3@michael-VirtualBox \
--to=michael.zaidman@gmail.com \
--cc=Enrik.Berkhan@inka.de \
--cc=andrew.robertson@ftdichip.com \
--cc=jikos@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).