From: Andreas Larsson <andreas@gaisler.com>
To: Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, software@gaisler.com
Subject: Re: [PATCH v2 0/7] usb: gadget: gr_udc: OF and ep.maxpacket_limit improvements and fix of GFP_KERNEL in atomic context
Date: Tue, 15 Apr 2014 13:41:54 +0200 [thread overview]
Message-ID: <534D1B02.2020804@gaisler.com> (raw)
In-Reply-To: <1395933359-7109-1-git-send-email-andreas@gaisler.com>
On 2014-03-27 16:15, Andreas Larsson wrote:
> This patchset:
> - Adds some OF related improvements suggested by Mark
> Rutland.
> - Adds ep.maxpacket_limit to the debugfs file and adds a check if
> gr_ep_enable is called with a maxpacket value greater than
> ep.maxpacket_limit.
> - Fixes a bug where GFP_KERNEL was used in atomic context
>
> Andreas Larsson (7):
> usb: gadget: gr_udc: Make struct platform_device variable name
> clearer and use platform_set/get_drvdata
> usb: gadget: gr_udc: Expand devicetree documentation
> usb: gadget: gr_udc: Use platform_get_irq instead of
> irq_of_parse_and_map
> usb: gadget: gr_udc: Use of_property_read_u32_index to access arrays
> usb: gadget: gr_udc: Add ep.maxpacket_limit to debugfs information
> usb: gadget: gr_udc: Return error code when trying to set
> ep.maxpacket > ep.maxpacket_limit
> usb: gadget: gr_udc: Use GFP_ATOMIC when allocating under help
> spinlock
>
> Documentation/devicetree/bindings/usb/gr-udc.txt | 22 +++++----
> drivers/usb/gadget/gr_udc.c | 53 ++++++++++++----------
> 2 files changed, 42 insertions(+), 33 deletions(-)
Anyone got feedback or reasons this cannot be accepted?
Best regards,
Andreas Larsson
prev parent reply other threads:[~2014-04-15 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:15 [PATCH v2 0/7] usb: gadget: gr_udc: OF and ep.maxpacket_limit improvements and fix of GFP_KERNEL in atomic context Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 1/7] usb: gadget: gr_udc: Make struct platform_device variable name clearer and use platform_set/get_drvdata Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 2/7] usb: gadget: gr_udc: Expand devicetree documentation Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 3/7] usb: gadget: gr_udc: Use platform_get_irq instead of irq_of_parse_and_map Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 4/7] usb: gadget: gr_udc: Use of_property_read_u32_index to access arrays Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 5/7] usb: gadget: gr_udc: Add ep.maxpacket_limit to debugfs information Andreas Larsson
2014-03-27 15:15 ` [PATCH v2 6/7] usb: gadget: gr_udc: Return error code when trying to set ep.maxpacket > ep.maxpacket_limit Andreas Larsson
2014-03-27 15:15 ` [PATCH 7/7] usb: gadget: gr_udc: Use GFP_ATOMIC when allocating under help spinlock Andreas Larsson
2014-04-01 10:15 ` [PATCH v2 7/7] usb: gadget: gr_udc: Use GFP_ATOMIC when allocating under held spinlock Andreas Larsson
2014-04-15 11:41 ` Andreas Larsson [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=534D1B02.2020804@gaisler.com \
--to=andreas@gaisler.com \
--cc=balbi@ti.com \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=software@gaisler.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