Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932424AbcDLIIo (ORCPT ); Tue, 12 Apr 2016 04:08:44 -0400 Received: from mga11.intel.com ([192.55.52.93]:52682 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932391AbcDLIIm (ORCPT ); Tue, 12 Apr 2016 04:08:42 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,472,1455004800"; d="asc'?scan'208";a="956801587" From: Felipe Balbi To: "Du\, Changbin" Cc: "gregkh\@linuxfoundation.org" , "linux-usb\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" Subject: RE: [PATCH] usb: dwc3: free dwc->regset on dwc3_debugfs_exit In-Reply-To: <0C18FE92A7765D4EB9EE5D38D86A563A05CFEB0F@shsmsx102.ccr.corp.intel.com> References: <1460108522-31664-1-git-send-email-changbin.du@intel.com> <87bn5gpo1v.fsf@intel.com> <0C18FE92A7765D4EB9EE5D38D86A563A05CFE203@shsmsx102.ccr.corp.intel.com> <87shyso0tp.fsf@intel.com> <0C18FE92A7765D4EB9EE5D38D86A563A05CFE28D@shsmsx102.ccr.corp.intel.com> <87mvp0ny81.fsf@intel.com> <0C18FE92A7765D4EB9EE5D38D86A563A05CFE62A@shsmsx102.ccr.corp.intel.com> <877fg3mjti.fsf@intel.com> <0C18FE92A7765D4EB9EE5D38D86A563A05CFEB0F@shsmsx102.ccr.corp.intel.com> User-Agent: Notmuch/0.21+96~g9bbc54b (http://notmuchmail.org) Emacs/25.0.90.3 (x86_64-pc-linux-gnu) Date: Tue, 12 Apr 2016 11:06:42 +0300 Message-ID: <87mvozl08d.fsf@intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2027 Lines: 60 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, "Du, Changbin" writes: > Hi, Balbi, > >> > Hmm, I agree from this point. I will combine this patch with other two >> patches >> > (due to their dependency). And I'd like remove the 'dwc->root=3DNULL' = as >> well, >>=20 >> you are creating a dependency that doesn't exist. Please stop that. You >> should have two separate branches based on v4.6-rc3 (or, if you prefer, >> one based on my testing/fixes and another based on my testing/next). On >> one branch you have *only* $subject and you fix *all* the memory >> leaks. On the other branch you have the other two patches. >>=20 >> Ignore the fact that we might have a conflict, that's for git (and >> maintainers) to handle when they happen. >>=20 >> Again, don't create dependencies between fixes for the -rc cycle and >> changes for the next merge window. >>=20 > Thanks for dedicated explanation. I was concern about the conflict. yeah, no problem ;-) > Now it is very clear for me to handle such situation. good :-) glad we could sort it out. =2D-=20 balbi --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXDKyTAAoJEIaOsuA1yqREOqQP/jSHh1bsWUCp0I58SgJzD8Gt MfHKR76z0Fs+zzPCTgbLXkvDTytjpyHD/zA5RVuQiPcsuLKJTE86oxcUZxIJST7k tXM6utDVeoWdAJFy1DkDdXfhNLbbmfROA+7ISnHbLkVoI18SrL/V1qqeV3PKAYAx Ln6tMbDmA4y7LdNQ0meLC+KS8bpSgn7cEBr5tiGGMk4lYD7foUBZLxjerOW5ONIb nbbWEW6QyCGACFfoBL0b4WtBkFlhEJ7Qrqixe8wrXbmU/nVmxmHKLdkmMFfu/chL 5mgglYwBCTnv0hHON2DBLhGh4tmWICuIxC9+vIBuAX3lu91gbflphDfutNgXOMBs FP3z6s8O/58yb/9E2e0lOAK1HUpEVtBnlOIxzPkkcTl+RGdQF7qR2B5iBl92eH73 q1EKS/XyF05YjYpd4Uy1FbRB2TjtXW0KTjypzcmHpofFwxSt808UkW1QDb2iTMhc fWf2JuMwyP64NW1dr+yEiXZ+Ca0+HTivOdlistoemEnAhyz/6u6TOQNRwMczWqxM tbnTZbdtLaqXh3rKeXsO4gMusIUye+3S3S1eSAi/TasKTb+LdhHPtiWHsCAcf1co Xt7QrB+EW5lVf48PGrBjTfjJIuhu0ZIP1aG8FBttolWmnu/ysJExmUd8gx0TQtY2 iwhpT1F7Z70Z1cVgB1sM =iuQT -----END PGP SIGNATURE----- --=-=-=--