From: Johan Hovold <johan@kernel.org>
To: Crescent Hsieh <crescentcy.hsieh@moxa.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
FangpingFP.Cheng@moxa.com, Epson.Chiang@moxa.com,
EddieSY.Lin@moxa.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] USB: serial: mxuport: add MUX50U support and updates
Date: Mon, 5 Oct 2026 10:15:47 +0200 [thread overview]
Message-ID: <asNcs43KeyEPfyK6@hovoldconsulting.com> (raw)
In-Reply-To: <asM46PTPs_8C3q4v@moxa-ThinkCentre-M90t>
On Mon, Oct 05, 2026 at 01:43:04PM +0800, Crescent Hsieh wrote:
> Just a gentle follow-up on this series, which was posted nearly two
> months ago. I understand that it is still in your queue. Please let me
> know if there is anything I can do to help with the review.
Yeah, sorry about the delay. Will try to look at it shortly but
probably not before next week due to conferences.
Johan
prev parent reply other threads:[~2026-10-05 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 6:04 Crescent Hsieh
2026-08-11 6:04 ` [PATCH v3 1/6] USB: serial: mxuport: clean up product ID definitions and device table Crescent Hsieh
2026-08-11 6:04 ` [PATCH v3 2/6] USB: serial: mxuport: clean up firmware version handling Crescent Hsieh
2026-08-11 6:04 ` [PATCH v3 3/6] USB: serial: mxuport: add MUX50U-based device support Crescent Hsieh
2026-08-11 6:04 ` [PATCH v3 4/6] USB: serial: add generic write control callbacks Crescent Hsieh
2026-08-11 6:05 ` [PATCH v3 5/6] USB: serial: mxuport: handle SEND_NEXT transmit flow control Crescent Hsieh
2026-08-11 6:05 ` [PATCH v3 6/6] USB: serial: mxuport: support RS485 mode configuration Crescent Hsieh
2026-09-10 3:03 ` [PATCH v3 0/6] USB: serial: mxuport: add MUX50U support and updates Crescent Hsieh
2026-09-10 12:56 ` Johan Hovold
2026-09-10 12:57 ` Johan Hovold
2026-10-05 5:43 ` Crescent Hsieh
2026-10-05 8:15 ` Johan Hovold [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=asNcs43KeyEPfyK6@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=EddieSY.Lin@moxa.com \
--cc=Epson.Chiang@moxa.com \
--cc=FangpingFP.Cheng@moxa.com \
--cc=crescentcy.hsieh@moxa.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®