From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Georgios Tsotsos <tsotsos@gmail.com>
Cc: devel@driverdev.osuosl.org, James Hogan <jhogan@kernel.org>,
linux-kernel@vger.kernel.org,
Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [PATCH v5] Staging: octeon-usb: Using defined error codes and applying coding style.
Date: Mon, 30 Jul 2018 10:51:49 +0200 [thread overview]
Message-ID: <20180730085149.GA8460@kroah.com> (raw)
In-Reply-To: <20180729222936.27608-1-tsotsos@gmail.com>
On Mon, Jul 30, 2018 at 01:29:36AM +0300, Georgios Tsotsos wrote:
> Replaced -1 with defined error code EINVAL
>
> Signed-off-by: Georgios Tsotsos <tsotsos@gmail.com>
> ---
> v2: Apply coding style to function cvmx_usb_poll_channel
> v3: Break down function cvmx_usb_poll_channel
> v4: Return defined error code and applying coding style for function calls
> v5: Fixing wrong patch applied before with typo on dev_err and applying coding
> style as suggested on v3
>
> drivers/staging/octeon-usb/octeon-hcd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Ugh, I have no idea anymore what patches to apply from you for this
driver, sorry, there are too many flying around.
Take a day off, relax, and then resend all of your pending patches as
one series, properly numbered, and we can go from there. I've dropped
all of your patches from my queue for now.
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-30 8:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 15:41 [PATCH v2 0/3] Staging: octeon-usb fixes for coding style, SPDX and readability Georgios Tsotsos
2018-07-26 13:30 ` [PATCH 1/3] Staging: octeon-usb: Adding SPDX license identifier Georgios Tsotsos
2018-07-26 15:41 ` [PATCH v2 " Georgios Tsotsos
2018-07-26 13:30 ` [PATCH 2/3] Staging: octeon-usb: Change coding style of CVMX_WAIT_FOR_FIELD32 marco Georgios Tsotsos
2018-07-26 15:41 ` [PATCH v2 " Georgios Tsotsos
2018-07-27 15:15 ` Greg Kroah-Hartman
2018-07-28 15:48 ` Georgios Tsotsos
2018-07-29 11:40 ` [PATCH v3 0/2] Staging: octeon-usb: Changed CVMX_WAIT_FOR_FIELD32 macro Georgios Tsotsos
2018-07-29 11:40 ` [PATCH v3 1/2] Staging: octeon-usb: Change multiple calling of CVMX_USBCX_GRSTCTL Georgios Tsotsos
2018-07-29 12:44 ` Greg Kroah-Hartman
2018-07-29 14:13 ` [PATCH v4 " Georgios Tsotsos
2018-07-29 11:40 ` [PATCH v3 2/2] Staging: octeon-usb: Changes macro CVMX_WAIT_FOR_FIELD32 to function call Georgios Tsotsos
2018-07-29 19:27 ` Aaro Koskinen
2018-07-29 14:13 ` [PATCH v4 " Georgios Tsotsos
2018-07-26 13:30 ` [PATCH 3/3] Staging: octeon-usb: Breaks down cvmx_usb_poll_channel() Georgios Tsotsos
2018-07-26 15:41 ` [PATCH v2 " Georgios Tsotsos
2018-07-26 16:31 ` Joe Perches
2018-07-26 22:08 ` Georgios Tsotsos
2018-07-29 11:41 ` [PATCH v3 0/1] " Georgios Tsotsos
2018-07-29 11:41 ` [PATCH v3 1/1] " Georgios Tsotsos
2018-07-29 12:43 ` Greg Kroah-Hartman
2018-07-29 14:33 ` [PATCH v4 1/1] Staging: octeon-usb: Using defined error codes and applying coding style Georgios Tsotsos
2018-07-29 20:21 ` Aaro Koskinen
2018-07-29 21:17 ` Georgios Tsotsos
2018-07-29 22:29 ` [PATCH v5] " Georgios Tsotsos
2018-07-30 8:51 ` Greg Kroah-Hartman [this message]
2018-07-30 20:18 ` Georgios Tsotsos
2018-07-29 14:52 ` [PATCH v3 1/1] Staging: octeon-usb: Breaks down cvmx_usb_poll_channel() Georgios Tsotsos
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=20180730085149.GA8460@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaro.koskinen@iki.fi \
--cc=devel@driverdev.osuosl.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tsotsos@gmail.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