From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754112AbbAaWUd (ORCPT ); Sat, 31 Jan 2015 17:20:33 -0500 Received: from mout.web.de ([212.227.17.12]:50678 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750898AbbAaWUa (ORCPT ); Sat, 31 Jan 2015 17:20:30 -0500 Message-ID: <54CD5529.5060209@users.sourceforge.net> Date: Sat, 31 Jan 2015 23:20:25 +0100 From: SF Markus Elfring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Lino Sanfilippo , "David S. Miller" , Jamal Hadi Salim , netdev@vger.kernel.org CC: LKML , kernel-janitors@vger.kernel.org, Julia Lawall Subject: Re: [PATCH] net: sched: One function call less in em_meta_change() after error detection References: <5307CAA2.8060406@users.sourceforge.net> <530A086E.8010901@users.sourceforge.net> <530A72AA.3000601@users.sourceforge.net> <530B5FB6.6010207@users.sourceforge.net> <530C5E18.1020800@users.sourceforge.net> <530CD2C4.4050903@users.sourceforge.net> <530CF8FF.8080600@users.sourceforge.net> <530DD06F.4090703@users.sourceforge.net> <5317A59D.4@users.sourceforge.net> <54CD042E.6030606@users.sourceforge.net> <54CD115C.8070801@gmx.de> <54CD4D91.9080801@users.sourceforge.net> <54CD5404.1010004@gmx.de> In-Reply-To: <54CD5404.1010004@gmx.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:30cc6OmM3MxTxXSXi66sFy/qtu2CNAyQoi9QLlAHAMvPXtjVuuK oQAT8T9CPr+IlyVxRNSof9yfLPs0sRg1tP7DGa7B5zw1o4HYM85Q0Ma7OJ7lK84gI4roOBd eTEDO3GT+g7OdwLg1Z6SWjLmgujbveVcoEGaHTmccJXJTzxM45EJRYoyAGc7UM/BdO3Gf6Z uwl/sS1TjjUC9tkcJj/rw== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> I find that all these cases correspond to the current Linux coding >> style documentation, doesn't it? > > Sure, I think it does. Thanks for your acknowledgement. > But it was not coding style violation what I was reffering to. Do you suggest any fine-tuning for the affected documentation so that I would tweak my update suggestion once more? Regards, Markus