public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Starke, Daniel" <daniel.starke@siemens.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"jirislaby@kernel.org" <jirislaby@kernel.org>,
	"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 1/3] tty: n_gsm: add ioctl for DLC specific parameter configuration
Date: Tue, 28 Mar 2023 07:50:23 +0200	[thread overview]
Message-ID: <ZCKAH3y7qBmWNjf2@kroah.com> (raw)
In-Reply-To: <DB9PR10MB58810D7D5F76820DD19C686DE0889@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM>

On Tue, Mar 28, 2023 at 05:27:59AM +0000, Starke, Daniel wrote:
> Is there any blocking point which prevents this patch series from being
> merged?

Yes, me getting through my pending backlog:
	$ mdfrm -c ~/mail/todo/
	1211 messages in /home/gregkh/mail/todo/

Give me some time to catch up please.

To help out, and while you wait, please review other patches on the
mailing lists to help relieve the review load so that your patches can
get closer to the top of the list.

thanks,

greg k-h

      reply	other threads:[~2023-03-28  5:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 10:53 [PATCH v2 1/3] tty: n_gsm: add ioctl for DLC specific parameter configuration D. Starke
2023-03-15 10:53 ` [PATCH v2 2/3] tty: n_gsm: allow window size configuration D. Starke
2023-03-15 10:53 ` [PATCH v2 3/3] tty: n_gsm: add ioctl for DLC config via ldisc handle D. Starke
2023-03-28  5:27 ` [PATCH v2 1/3] tty: n_gsm: add ioctl for DLC specific parameter configuration Starke, Daniel
2023-03-28  5:50   ` gregkh [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=ZCKAH3y7qBmWNjf2@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.starke@siemens.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.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