[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0C18FE92A7765D4EB9EE5D38D86A563A05CEBDCF@shsmsx102.ccr.corp.intel.com>
Date: Thu, 7 Apr 2016 05:21:17 +0000
From: "Du, Changbin" <changbin.du@...el.com>
To: Felipe Balbi <balbi@...nel.org>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 0/3] Improvement, fix and new entry for dwc3 debugfs
> before I review your patches, one comment
>
> changbin.du@...el.com writes:
> > From: "Du, Changbin" <changbin.du@...el.com>
> >
> > The first patch removed unnecessary checking for debugfs api call;
> > The second patch fix a memory leak issue;
> > The third patch add one new entry to debufs.
> >
> > Du, Changbin (3):
> > usb: dwc3: make dwc3_debugfs_init return value be void
>
> this is _not_ a fix
>
> > usb: dwc3: free dwc->regset on dwc3_debugfs_exit
>
> but this is. Why isn't this, at least, the first patch in the list ? In
> fact, it would be preferred that this patch be sent by itself and the
> following two patches should be on another branch completely without any
> dependencies to the memory leak fix.
>
> --
> Balbi
Sure, Balbi. This will be better. I will send out patch v3 and another independent
patch. Also include changelog as Greg required. Thanks for checking.
Regards,
Du, Changbin
Powered by blists - more mailing lists