From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752508AbdLKOpd (ORCPT ); Mon, 11 Dec 2017 09:45:33 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:40537 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750759AbdLKOpa (ORCPT ); Mon, 11 Dec 2017 09:45:30 -0500 X-Google-Smtp-Source: ACJfBov5LrFdpp14EsXJ/N/Ik+OW7M9tfzE0y06StYNbH0Uui2ZFjnkj3mhmueiBE/DuGTXt9okNsg== Date: Mon, 11 Dec 2017 15:45:26 +0100 From: Ingo Molnar To: alexander.levin@verizon.com Cc: "linux-kernel@vger.kernel.org" , Peter Zijlstra Subject: Re: [PATCH 2/2] tools/lib/lockdep: add empty declaration for early_param Message-ID: <20171211144526.5qha6jmg6m4nlpyx@gmail.com> References: <20171207161057.7406-1-alexander.levin@verizon.com> <20171207161057.7406-3-alexander.levin@verizon.com> <20171208060920.u56ee3kkyyqdmjol@gmail.com> <20171208062010.yrcbazicfut7pmk2@gmail.com> <20171208140322.cmt3engara5tymq6@sasha-lappy> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20171208140322.cmt3engara5tymq6@sasha-lappy> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * alexander.levin@verizon.com wrote: > On Fri, Dec 08, 2017 at 07:20:10AM +0100, Ingo Molnar wrote: > > > >* Ingo Molnar wrote: > > > >> > >> * alexander.levin@verizon.com wrote: > >> > >> > Fixes a compilation error: > >> > > >> > CC lockdep.o > >> > In file included from lockdep.c:28:0: > >> > ../../../kernel/locking/lockdep.c:89:13: error: expected declaration specifiers or ‘...’ before string constant > >> > early_param("crossrelease_fullstack", allow_crossrelease_fullstack); > >> > ^~~~~~~~~~~~~~~~~~~~~~~~ > >> > ../../../kernel/locking/lockdep.c:89:39: error: expected declaration specifiers or ‘...’ before ‘allow_crossrelease_fullstack’ > >> > early_param("crossrelease_fullstack", allow_crossrelease_fullstack); > >> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> > >> Ugh, this changelog was in DOS format (had extra \r's) - how did that happen? > > > >Hm, so it's because the second patch email was sent as as a base64 encoded email: > > > > Content-Transfer-Encoding: base64 > > > >totally not recommended and git-send-email will not do that - what happened? > > I'm not sure, this was sent using git-send-email... Weird - will let you know if it happens again. Thanks, Ingo