From: Johan Hovold <johan@kernel.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: gregkh <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>
Subject: Re: Re: [PATCH] USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode
Date: Wed, 24 Aug 2022 11:26:53 +0200 [thread overview]
Message-ID: <YwXu3ZDozZczJxuh@hovoldconsulting.com> (raw)
In-Reply-To: <7491a855.2224.182cf117a99.Coremail.slark_xiao@163.com>
On Wed, Aug 24, 2022 at 04:56:45PM +0800, Slark Xiao wrote:
> At 2022-08-16 17:50:01, "gregkh" <gregkh@linuxfoundation.org> wrote:
> >On Tue, Aug 16, 2022 at 05:40:35PM +0800, Slark Xiao wrote:
> >> Any response?
> >
> >To what?
> >
> >It was the middle of the merge window, we can't do anything with new
> >patches until after -rc1 is out, and then we have a few thousand to dig
> >through afterward.
> >
> >Relax, there is no rush here.
> >
> >thanks,
> >
> >greg k-h
> Hi Greg,
> Now v6.0-rc2 is out for several days. I still didn't find any progress about this commit.
> Normally such commit would be committed into Johan Hovold's personal project firstly:
> index: kernel/git/johan/usb-serial.git and waitting for merge window.
> In some sub-system, the merge window would be closed after rc4.
> So Johan or Greg , could you help handle this asap?
Again, relax. I haven't had time to process my queue after the merge
window and some holiday. Nothing is lost and I'll get to your patch in
time.
Johan
next prev parent reply other threads:[~2022-08-24 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 3:30 [PATCH] USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode Slark Xiao
[not found] ` <54f2b923.341c.182a606bab3.Coremail.slark_xiao@163.com>
2022-08-16 9:50 ` gregkh
2022-08-24 8:56 ` Slark Xiao
2022-08-24 9:26 ` Johan Hovold [this message]
2022-08-24 9:29 ` Re:Re: " Slark Xiao
2022-08-29 13:36 ` Johan Hovold
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=YwXu3ZDozZczJxuh@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=slark_xiao@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox