From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Alan Stern <stern@rowland.harvard.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/7] Universal Serial Bus: Removing Acronyms
Date: Wed, 1 Apr 2020 13:13:00 +0200 [thread overview]
Message-ID: <20200401111300.GB2070530@kroah.com> (raw)
In-Reply-To: <AM7PR04MB7157968F8BC12AC42CD397B38BC90@AM7PR04MB7157.eurprd04.prod.outlook.com>
On Wed, Apr 01, 2020 at 10:26:25AM +0000, Peter Chen wrote:
>
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> > > On Wed, Apr 01, 2020 at 10:32:42AM +0300, Felipe Balbi wrote:
> > >> 764 files changed, 86304 insertions(+), 86304 deletions(-)
> > >
> > > Ah, a nice tiny patchset, I'll try to sneak this in during the merge
> > > window now :)
> >
> > That's great, Greg. It'll help hundreds of people, I'm sure.
> >
> > > nice job...
> >
> > Thank you
> >
> > > greg "I know what day this is..." k-h
> >
> > felipe "I've been mostly confined" balbi
> >
> > --
>
> Just one small comment, it may let the code line exceed 80 characters often,
> is it OK? Or the 80 characters per line is not mandatory?
It's ok, it gives people who like running checkpatch.pl something to do :)
next prev parent reply other threads:[~2020-04-01 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 7:32 [PATCH 0/7] Universal Serial Bus: Removing Acronyms Felipe Balbi
2020-04-01 7:32 ` [PATCH 3/7] universal host controller interface: remove acronyms Felipe Balbi
2020-04-01 7:38 ` [PATCH 0/7] Universal Serial Bus: Removing Acronyms Greg Kroah-Hartman
2020-04-01 7:44 ` Felipe Balbi
2020-04-01 10:26 ` Peter Chen
2020-04-01 11:13 ` Greg Kroah-Hartman [this message]
2020-04-01 11:34 ` Felipe Balbi
2020-04-01 14:43 ` Alan Stern
2020-04-02 2:15 ` Chunfeng Yun
2020-04-01 18:06 ` Thinh Nguyen
2020-04-01 18:48 ` Thinh Nguyen
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=20200401111300.GB2070530@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=peter.chen@nxp.com \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.