From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 1A20B1B1F0 for ; Sat, 29 Dec 2018 01:10:03 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Dec 2018 16:10:02 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,411,1539673200"; d="scan'208";a="305884225" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga006.fm.intel.com with ESMTP; 28 Dec 2018 16:10:02 -0800 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 28 Dec 2018 16:10:02 -0800 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.209]) by FMSMSX113.amr.corp.intel.com ([169.254.13.137]) with mapi id 14.03.0415.000; Fri, 28 Dec 2018 16:10:02 -0800 From: "Wiles, Keith" To: users Thread-Topic: uncrustify configuration file. Thread-Index: AQHUnwrXIKZvS6LpBk6Xxj8FQOcLkQ== Date: Sat, 29 Dec 2018 00:10:01 +0000 Message-ID: <11BE608E-17EC-4E5B-9347-6587BC6D0B40@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.12.154] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [dpdk-users] uncrustify configuration file. X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2018 00:10:04 -0000 I have been playing with uncrustify http://uncrustify.sourceforge.net/ and = working on a configuration file for DPDK coding style. The configuration file located here https://github.com/pktgen/uncrustify-dp= dk.git seems to get close the right style. Maybe it could be a good start o= n making sure submitted code is close to the right style. I give no guarant= ees and make sure you review the changes to your code after running this co= nfig. If you want to make it better then you can fork it on GitHub and send me a = pull request. Regards, Keith