From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753351Ab1LLQSQ (ORCPT ); Mon, 12 Dec 2011 11:18:16 -0500 Received: from mailhub.sw.ru ([195.214.232.25]:14007 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751203Ab1LLQSP (ORCPT ); Mon, 12 Dec 2011 11:18:15 -0500 Message-ID: <4EE6293D.2020903@parallels.com> Date: Mon, 12 Dec 2011 20:18:05 +0400 From: Stanislav Kinsbursky User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: "J. Bruce Fields" CC: "Trond.Myklebust@netapp.com" , "linux-nfs@vger.kernel.org" , Pavel Emelianov , "neilb@suse.de" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , James Bottomley , "davem@davemloft.net" , "devel@openvz.org" Subject: Re: [PATCH 1/4] SUNRPC: use passed network namespace context in rpc_parse_scope_id() References: <20111207111716.17273.63010.stgit@localhost6.localdomain6> <20111207112016.17273.44510.stgit@localhost6.localdomain6> <20111208204749.GC32505@fieldses.org> <4EE625E1.7000502@parallels.com> <20111212160722.GF18185@fieldses.org> In-Reply-To: <20111212160722.GF18185@fieldses.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 12.12.2011 20:07, J. Bruce Fields пишет: > On Mon, Dec 12, 2011 at 08:03:45PM +0400, Stanislav Kinsbursky wrote: >> 09.12.2011 00:47, J. Bruce Fields пишет: >>> On Wed, Dec 07, 2011 at 03:20:16PM +0300, Stanislav Kinsbursky wrote: >>>> Use incomming network context in rpc_parse_scope_id() instead of hard-coded >>> >>> Changelogs are a little confusing; I might have said "allow >>> rpc_parse_cope_id() caller to pass in network context instead of using >>> hard-code "init_net"." >> >> Probably, you variant is better. My English is not good enough to >> write descriptive and, in the same time, clear and short comments to >> patches. > > Uh, and mine's got a problm or two as well. ("hard-code" should be > "hard-coded" in the above.) > > My main complaint was just that "incoming network context" sounds like > it refers to the network context associated with an incoming rpc > request. But actually all you're doing is using the network context > passed in by the caller. > > --b. Yep, agreed. I'll resend next patch set version with better comments. -- Best regards, Stanislav Kinsbursky