Return-path: Received: from mail-gw1-out.broadcom.com ([216.31.210.62]:56482 "EHLO mail-gw1-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755217AbbAGXHG (ORCPT ); Wed, 7 Jan 2015 18:07:06 -0500 Message-ID: <54ADBC13.70100@broadcom.com> (sfid-20150108_000741_052748_744FB174) Date: Thu, 8 Jan 2015 00:06:59 +0100 From: Arend van Spriel MIME-Version: 1.0 To: Johannes Berg CC: Giel van Schijndel , Andy Shevchenko , , Kalle Valo , Eliad Peller , "John W. Linville" , Arik Nemtsov , "open list:TI WILINK WIRELES..." , open list: "NETWORKING DRIVERS" , ; Subject: Re: [PATCH 2/2] Fix copy-paste bug: assign from src struct not dest References: <20150107191836.GA18978@salidar.dom.custoft.eu> <1420668978.3407.28.camel@sipsolutions.net> In-Reply-To: <1420668978.3407.28.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8"; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 01/07/15 23:16, Johannes Berg wrote: > On Wed, 2015-01-07 at 20:18 +0100, Giel van Schijndel wrote: > >> IMO the aligned block of code has the significant advantage of taking >> advantage of humans' ability to spot things that break a pattern. Which >> in this case becomes *very* visible when properly aligned, because >> without the alignment there is no (visual) pattern (or at least not one >> very suitable for my "visual processing system", I know the same applies >> to at least some others). > > Yeah, well, but why even invoke that "visual processing system"? > > If you look, for example, at the __skb_clone function it just uses a > macro: > > #define C(x) n->x = skb->x This requires fixed names so I generally prefer to add them: #define C(d, s, f) (d)->f = (s)->f > and then > > C(len); > C(data_len); C(acx, conf, window_size); C(acx, conf, increase_time); Regards, Arend > > etc. > > johannes > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/