From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932188AbcGAOrX (ORCPT ); Fri, 1 Jul 2016 10:47:23 -0400 Received: from mout.web.de ([212.227.15.14]:63841 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752540AbcGAOrV (ORCPT ); Fri, 1 Jul 2016 10:47:21 -0400 Subject: Re: mfd: dm355evm_msp: Refactoring for add_child() To: Joe Perches References: <566ABCD9.1060404@users.sourceforge.net> <5682D228.7070902@users.sourceforge.net> <20160111082922.GB14104@x1> <05b7db2a-437a-60ac-d289-71d2150e7f5f@users.sourceforge.net> <20160608111442.GB14888@dell> <75c1cc23-3a2d-db78-d0f2-b5934b18e828@users.sourceforge.net> <20160628150725.GL24982@dell> <20160628163146.GG29166@dell> <69e96aa0-f3d9-d70d-c3ec-d39b5e9d9f14@users.sourceforge.net> <1467318883.24287.171.camel@perches.com> Cc: Lee Jones , LKML , kernel-janitors@vger.kernel.org, Julia Lawall From: SF Markus Elfring Message-ID: <447162e7-5183-e589-74bc-0023a1442ebd@users.sourceforge.net> Date: Fri, 1 Jul 2016 16:40:15 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <1467318883.24287.171.camel@perches.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:7DIIzhgDfL2u+NkPrdhCI/tMJ2F1KXfXe7rjO3orUyK8dYPK+hg 2TiZBljb2Po2QInfMt3Gcs/Y124vt4l6ccatj69UunMo8c32wkPMkdB+Wv0ZQGwAQj+vVK0 80OUQ2/F17jJ+vejvnCt3o8KdZ3eykFSUehPj2+Byqz9GbkVdcomNlu14tAXKwGkqNLSi6b CHYEXEu58KpkYaH8VDGIQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:jqjuPTD9u7k=:Nlpe34JwUHsKdh//cJBjuG ovNKB1l2OMoa1owk9RGxOIFumfZrgQWHnKcTa01QoNBuCqS+ZEe9+9Sw+jotqWo18jA+3YgSz 0d1HddZ0UOZ3DXhdCpabcJFfs+GqmOJneXjOMjTmZj61jIvVdG2UkCOnC+b5YWp0U/XkOOSPU Vh08gWx3tTrHFrqAoYXnJTAFVomQkKlp8qWF7deRPk2tRaKIgPsBX5uFEgNro2nOpE6HFkiQW nhhzXskH+rHFtOEGoN7BFbUxrO3kLHX/ciEfSH3u8RCLj92x4jRrV39zZvjJYj/d4PljQnsL6 bBjlQJdgPIC8oeZAkJZ9YcieD0cvm9oNSekOf0g0zBDymVHOz0iqAdJ5AV+hc6UabOgN+Y2KL NOPABKPbBpAD9ieHou0+FzmfnIuQNpDaMLe25tzkvheXGOf/1gzK9i865pCzwsPtaELaJC+v8 +Gp3lPcvVOoyRgmN/D/a66Gw+gyBLZJM3GPR3UMlJWd/UM5x2dpjEE9hSnLXYbK73m5iSAM/7 3Yj3z7s4FUPDBuNSy+M32jEehqy+O1inEdXEALcL4jCG7NvB3YuYXuxeFAdqOZM098S6lqnzr 3NicS+iGVAfgxfQYi7DI5lzzv0s1QduV2az5WJx9L+lVEWRT/y5yScFvubrAGYhpgKWjCjBcf rxtT/6NZjOk/sU/GOMjxICyzlB28S6gVw+0bGLfYh0zTCttl88/SXN+tEBymu/svnBTGGhkDZ 5HHpa4JM1VSlH3hJA26SCuzvUEIaScJlL6kMrWBg5j71saZLdzvkSJzyhmE7fj91A6/3Slhjz tzuyQYn Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Can you please fix your email client to _not_ send References: > and In-reply-to: headers when sending new patches? I prefer to associate some patches with previous relevant discussion directly. > Even better would be to use git send-email for these patches. This command can also support a parameter like "--thread", can't it? Would you like point any more views out about communication styles? Regards, Markus From mboxrd@z Thu Jan 1 00:00:00 1970 From: SF Markus Elfring Date: Fri, 01 Jul 2016 14:40:15 +0000 Subject: Re: mfd: dm355evm_msp: Refactoring for add_child() Message-Id: <447162e7-5183-e589-74bc-0023a1442ebd@users.sourceforge.net> List-Id: References: <566ABCD9.1060404@users.sourceforge.net> <5682D228.7070902@users.sourceforge.net> <20160111082922.GB14104@x1> <05b7db2a-437a-60ac-d289-71d2150e7f5f@users.sourceforge.net> <20160608111442.GB14888@dell> <75c1cc23-3a2d-db78-d0f2-b5934b18e828@users.sourceforge.net> <20160628150725.GL24982@dell> <20160628163146.GG29166@dell> <69e96aa0-f3d9-d70d-c3ec-d39b5e9d9f14@users.sourceforge.net> <1467318883.24287.171.camel@perches.com> In-Reply-To: <1467318883.24287.171.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Joe Perches Cc: Lee Jones , LKML , kernel-janitors@vger.kernel.org, Julia Lawall > Can you please fix your email client to _not_ send References: > and In-reply-to: headers when sending new patches? I prefer to associate some patches with previous relevant discussion directly. > Even better would be to use git send-email for these patches. This command can also support a parameter like "--thread", can't it? Would you like point any more views out about communication styles? Regards, Markus