From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Martin Hundebøll" <martin@geanix.com>
Cc: "Jiri Slaby" <jslaby@suse.com>,
"Alan Cox" <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, "Sean Nyekjær" <sean@geanix.com>,
"Esben Haabendal" <esben@geanix.com>
Subject: Re: [PATCHv4] tty: n_gsm: add ioctl to map serial device to mux'ed tty
Date: Thu, 22 Aug 2019 14:18:47 -0700 [thread overview]
Message-ID: <20190822211847.GA3287@kroah.com> (raw)
In-Reply-To: <a67bba41-a92a-1b8f-c8f8-25efe3687695@geanix.com>
On Thu, Aug 22, 2019 at 09:28:07PM +0200, Martin Hundebøll wrote:
> Hi Greg,
>
> Just a friendly "ping" on this patch.
Sorry for the delay, given that no one else has objected to it, I'll go
queue it up now.
thanks,
greg k-h
prev parent reply other threads:[~2019-08-22 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 21:12 [PATCHv4] tty: n_gsm: add ioctl to map serial device to mux'ed tty Martin Hundebøll
2019-08-22 19:28 ` Martin Hundebøll
2019-08-22 21:18 ` Greg Kroah-Hartman [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=20190822211847.GA3287@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=esben@geanix.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@geanix.com \
--cc=sean@geanix.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