From: Milian Reichardt <mreichardt95@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: wsa-dev@sang-engineering.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: misc: ldusb: Fixed coding style issues
Date: Fri, 03 Mar 2017 11:08:40 +0100 [thread overview]
Message-ID: <1488535720.27091.1.camel@gmail.com> (raw)
In-Reply-To: <20170303062443.GA31497@kroah.com>
Am Freitag, den 03.03.2017, 07:24 +0100 schrieb Greg KH:
> Please be specific as to exactly what issues you are fixing up. And
> don't do multiple things in the same patch, each different thing
> needs
> to be broken up into an individual patch.
Thanks for the feedback. I'll brake things up in different patches
split into the type of error I'm fixing and describe them in more
detail.
greetings,
Milian Reichardt
prev parent reply other threads:[~2017-03-03 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 23:55 [PATCH] USB: misc: ldusb: Fixed coding style issues Milian Reichardt
2017-03-03 6:24 ` Greg KH
2017-03-03 10:08 ` Milian Reichardt [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=1488535720.27091.1.camel@gmail.com \
--to=mreichardt95@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wsa-dev@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).