From: Greg KH <greg@kroah.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: make usb_interrupt_msg() a static inline
Date: Wed, 4 Dec 2019 18:21:07 +0100 [thread overview]
Message-ID: <20191204172107.GF3627415@kroah.com> (raw)
In-Reply-To: <20191204143035.31751-1-info@metux.net>
On Wed, Dec 04, 2019 at 03:30:35PM +0100, Enrico Weigelt, metux IT consult wrote:
> usb_interrupt_msg() effectively is just an alias for usb_bulk_msg(),
> no need for being an real function, thus converting it to an
> inline function.
>
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
You also didn't even cc: the proper people as per
scripts/get_maintainer.pl so you obviously didn't even want the patch to
be reviewed or applied :(
prev parent reply other threads:[~2019-12-04 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 14:30 [PATCH] usb: make usb_interrupt_msg() a static inline Enrico Weigelt, metux IT consult
2019-12-04 17:20 ` Greg KH
2019-12-04 17:21 ` Greg KH [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=20191204172107.GF3627415@kroah.com \
--to=greg@kroah.com \
--cc=info@metux.net \
--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;
as well as URLs for NNTP newsgroup(s).