public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michal Nazarewicz <m.nazarewicz@samsung.com>
Cc: linux-usb@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4.1 5/8] USB: g_ffs: the FunctionFS gadget driver
Date: Wed, 5 May 2010 16:42:06 -0700	[thread overview]
Message-ID: <20100505234206.GA10165@kroah.com> (raw)
In-Reply-To: <2dfc60eedd6b15c55c33d462db51f775657e8120.1273061972.git.mina86@mina86.com>

On Wed, May 05, 2010 at 02:25:55PM +0200, Michal Nazarewicz wrote:
> The Function Filesystem (FunctioFS) lets one create USB
> composite functions in user space in the same way as GadgetFS
> lets one create USB gadgets in user space.  This allows
> creation of composite gadgets such that some of the functions
> are implemented in kernel space (for instance Ethernet, serial
> or mass storage) and other are implemented in user space.
> 
> Signed-off-by: Michal Nazarewicz <m.nazarewicz@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> There was a trivial bug in my previous patch.  The delta is:
> 
> diff --git a/drivers/usb/gadget/g_ffs.c b/drivers/usb/gadget/g_ffs.c
> index bed3641..4b0e4a0 100644
> --- a/drivers/usb/gadget/g_ffs.c
> +++ b/drivers/usb/gadget/g_ffs.c
> @@ -369,9 +369,8 @@ static int gfs_unbind(struct usb_composite_dev *cdev)
>  
>  
>  static int __gfs_do_config(struct usb_configuration *c,
> -			   int (*eth)(struct usb_configuration *c,
> -				      u8 ethaddr[ETH_ALEN]),
> -			   u8 ethaddr[ETH_ALEN])
> +			   int (*eth)(struct usb_configuration *c, u8 *ethaddr),
> +			   u8 *ethaddr)
>  {
>  	int ret;
> 
> ETH_ALEN is not defined if g_ffs is configured not to include ECM nor RNDIS.
> 
> Sorry about the confusion.

No problem, I merged it with the previous patch.

thanks,

greg k-h

  reply	other threads:[~2010-05-05 23:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 10:53 [PATCHv4 0/8] The FunctionFS composite function Michal Nazarewicz
2010-05-05 10:53 ` [PATCHv4 1/8] wait_event_interruptible_locked() interface Michal Nazarewicz
2010-05-05 10:53   ` [PATCHv4 2/8] fs/timerfd.c: make use of wait_event_interruptible_locked_irq() Michal Nazarewicz
2010-05-05 10:53     ` [PATCHv4 3/8] USB: gadget: __init and __exit tags removed Michal Nazarewicz
2010-05-05 10:53       ` [PATCHv4 4/8] USB: f_fs: the FunctionFS driver Michal Nazarewicz
2010-05-05 10:53         ` [PATCHv4 5/8] USB: g_ffs: the FunctionFS gadget driver Michal Nazarewicz
2010-05-05 10:53           ` [PATCHv4 6/8] USB: ffs-test: FunctionFS testing program Michal Nazarewicz
2010-05-05 10:53             ` [PATCHv4 7/8] USB: testusb: an USB testing application Michal Nazarewicz
2010-05-05 10:53               ` [PATCHv4 8/8] USB: testusb: testusb compatibility with FunctionFS gadget Michal Nazarewicz
2010-05-05 12:25           ` [PATCHv4.1 5/8] USB: g_ffs: the FunctionFS gadget driver Michal Nazarewicz
2010-05-05 23:42             ` Greg KH [this message]
2010-05-06  8:44 ` [PATCHv4 0/8] The FunctionFS composite function Michał Nazarewicz

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=20100505234206.GA10165@kroah.com \
    --to=greg@kroah.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.nazarewicz@samsung.com \
    --cc=m.szyprowski@samsung.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