From: cristian.birsan@microchip.com (cristian.birsan at microchip.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH linux-next v2 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes
Date: Tue, 28 Mar 2017 19:07:35 +0300 [thread overview]
Message-ID: <cover.1490715349.git.cristian.birsan@microchip.com> (raw)
From: Cristian Birsan <cristian.birsan@microchip.com>
This patch series provides fixes, based on the feedback received on the mailing list, for
the following:
- fifo table parameters validation against device tree values
- coding style
- message display for EP configuration error
- Kconfig comments for fifo_mode=0
Changes since v1:
- Removed static for usba_config_fifo_table() function from "Check fifo
configuration values against device tree" patch
Cristian Birsan (4):
usb: gadget: udc: atmel: Check fifo configuration values against
device tree
usb: gadget: udc: atmel: Minor code cleanup
usb: gadget: udc: atmel: Use dev_warn() to display EP configuration
error
usb: gadget: udc: atmel: Update Kconfig help for fifo_mode = 0
drivers/usb/gadget/udc/Kconfig | 5 ++--
drivers/usb/gadget/udc/atmel_usba_udc.c | 47 ++++++++++++++++++++++-----------
2 files changed, 35 insertions(+), 17 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: <cristian.birsan@microchip.com>
To: <nicolas.ferre@atmel.com>, <balbi@kernel.org>,
<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: [PATCH linux-next v2 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes
Date: Tue, 28 Mar 2017 19:07:35 +0300 [thread overview]
Message-ID: <cover.1490715349.git.cristian.birsan@microchip.com> (raw)
From: Cristian Birsan <cristian.birsan@microchip.com>
This patch series provides fixes, based on the feedback received on the mailing list, for
the following:
- fifo table parameters validation against device tree values
- coding style
- message display for EP configuration error
- Kconfig comments for fifo_mode=0
Changes since v1:
- Removed static for usba_config_fifo_table() function from "Check fifo
configuration values against device tree" patch
Cristian Birsan (4):
usb: gadget: udc: atmel: Check fifo configuration values against
device tree
usb: gadget: udc: atmel: Minor code cleanup
usb: gadget: udc: atmel: Use dev_warn() to display EP configuration
error
usb: gadget: udc: atmel: Update Kconfig help for fifo_mode = 0
drivers/usb/gadget/udc/Kconfig | 5 ++--
drivers/usb/gadget/udc/atmel_usba_udc.c | 47 ++++++++++++++++++++++-----------
2 files changed, 35 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2017-03-28 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 16:07 cristian.birsan at microchip.com [this message]
2017-03-28 16:07 ` [PATCH linux-next v2 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes cristian.birsan
2017-03-28 16:07 ` [PATCH linux-next v2 1/4] usb: gadget: udc: atmel: Check fifo configuration values against device tree cristian.birsan at microchip.com
2017-03-28 16:07 ` cristian.birsan
2017-03-30 10:38 ` Felipe Balbi
2017-03-30 10:38 ` Felipe Balbi
2017-03-28 16:07 ` [PATCH linux-next v2 2/4] usb: gadget: udc: atmel: Minor code cleanup cristian.birsan at microchip.com
2017-03-28 16:07 ` cristian.birsan
2017-03-28 16:07 ` [PATCH linux-next v2 3/4] usb: gadget: udc: atmel: Use dev_warn() to display EP configuration error cristian.birsan at microchip.com
2017-03-28 16:07 ` cristian.birsan
2017-03-30 10:39 ` Felipe Balbi
2017-03-30 10:39 ` Felipe Balbi
2017-03-28 16:07 ` [PATCH linux-next v2 4/4] usb: gadget: udc: atmel: Update Kconfig help for fifo_mode = 0 cristian.birsan at microchip.com
2017-03-28 16:07 ` cristian.birsan
2017-03-29 8:38 ` [PATCH linux-next v2 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes Nicolas Ferre
2017-03-29 8:38 ` Nicolas Ferre
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=cover.1490715349.git.cristian.birsan@microchip.com \
--to=cristian.birsan@microchip.com \
--cc=linux-arm-kernel@lists.infradead.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 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.