From: Greg KH <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Richard Leitner <richard.leitner@skidata.com>,
linux-usb@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] usb: usb251xb: drop some unused defines
Date: Mon, 19 Aug 2019 12:41:04 +0200 [thread overview]
Message-ID: <20190819104104.GA6530@kroah.com> (raw)
In-Reply-To: <20190819100211.26791-1-u.kleine-koenig@pengutronix.de>
On Mon, Aug 19, 2019 at 12:02:11PM +0200, Uwe Kleine-König wrote:
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> drivers/usb/misc/usb251xb.c | 5 -----
> 1 file changed, 5 deletions(-)
I can't take a patch without any changelog text.
And you forgot to cc: the usb maintainer, so there's no way this was
going to get merged :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-19 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 10:02 [PATCH] usb: usb251xb: drop some unused defines Uwe Kleine-König
2019-08-19 10:41 ` Greg KH [this message]
2019-08-19 10:59 ` Uwe Kleine-König
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=20190819104104.GA6530@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-usb@vger.kernel.org \
--cc=richard.leitner@skidata.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).