From: Felipe Balbi <balbi@kernel.org>
To: cristian.birsan@microchip.com, nicolas.ferre@atmel.com,
gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ludovic.desroches@atmel.com,
alexandre.belloni@free-electrons.com,
boris.brezillon@free-electrons.com,
Cristian Birsan <cristian.birsan@microchip.com>
Subject: Re: [PATCH linux-next v3 2/4] usb: gadget: udc: atmel: Minor code cleanup
Date: Wed, 05 Apr 2017 15:33:00 +0300 [thread overview]
Message-ID: <87efx7ghkz.fsf@linux.intel.com> (raw)
In-Reply-To: <1be887c4aeddab99e78238282b2cdd2ebc61a595.1491201365.git.cristian.birsan@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Hi,
cristian.birsan@microchip.com writes:
> From: Cristian Birsan <cristian.birsan@microchip.com>
>
> Minor code cleanup based on feedback received on mailinglist.
>
> Signed-off-by: Cristian Birsan <cristian.birsan@microchip.com>
> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
patch 1 applied fine, patch 2 didn't. Please rebase on testing/next
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-04-05 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 7:19 [PATCH linux-next v3 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes cristian.birsan
2017-04-03 7:19 ` [PATCH linux-next v3 1/4] usb: gadget: udc: atmel: Check fifo configuration values against device tree cristian.birsan
2017-04-03 7:19 ` [PATCH linux-next v3 2/4] usb: gadget: udc: atmel: Minor code cleanup cristian.birsan
2017-04-05 12:33 ` Felipe Balbi [this message]
2017-04-07 16:05 ` m91496
2017-04-03 7:19 ` [PATCH linux-next v3 3/4] usb: gadget: udc: atmel: Use dev_err() to display EP configuration error cristian.birsan
2017-04-03 7:19 ` [PATCH linux-next v3 4/4] usb: gadget: udc: atmel: Update Kconfig help for fifo_mode = 0 cristian.birsan
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=87efx7ghkz.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cristian.birsan@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.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
Powered by JetHome