Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Ilpo Järvinen" <ilpo.jarvinen-pxSi+dnQzZMxHbG02/KK1g@public.gmane.org>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	David Miller <davem@davemloft.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	chuck.lever@oracle.com, trond@netapp.com,
	linux-nfs@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net/sunrpc/xprtsock.c: some common code found
Date: Sun, 8 Feb 2009 00:25:43 -0500	[thread overview]
Message-ID: <20090208052543.GA20689@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0902071831210.2805-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>

On Sat, Feb 07, 2009 at 06:56:03PM +0200, Ilpo J=C3=A4rvinen wrote:
> I personally think that people were honestly just mislead to think th=
at
> diff-funcs output is part of the patch

Yes, exactly, in my case, that's all it was--the "diff" I thought I saw
in my 2-second skim looked odd, and I figured a comment might have
gotten dropped off in the process of replying and adding cc's--hence th=
e
original question.

Anyway, the patch looks obviously fine to me, and the diff-func and
codiff output are helpful.  (Where's diff-func from?)

In similar cases in the future, if you want to cater to the more tired
and/or mentally challenged among us (which may just be me), some clue
that visually distinguishes the quoted diff output in the comment might
help; e.g., maybe indent it like the below.

(But that's intended as a suggestion, not a requirement.)

--b.

Subject: Re: [PATCH] net/sunrpc/xprtsock.c: some common code found

diff-func output suggests these functions are very similar:

	$ diff-funcs xs_udp_write_space net/sunrpc/xprtsock.c
	 ...(etc)

and codiff shows the space savings:

	$ codiff net/sunrpc/xprtsock.o net/sunrpc/xprtsock.o.new
	...(etc)

Signed-off-by: Ilpo J=C3=A4rvinen <ilpo.jarvinen-pxSi+dnQzZMxHbG02/KK1g@public.gmane.org>

  parent reply	other threads:[~2009-02-08  5:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0902062247500.31842@wrl-59.cs.helsinki.fi>
     [not found] ` <Pine.LNX.4.64.0902062251501.31842@wrl-59.cs.helsinki.fi>
     [not found]   ` <20090206212043.GA1216@fieldses.org>
     [not found]     ` <20090206.140714.201930500.davem@davemloft.net>
     [not found]       ` <CAF18546-B024-40C9-8276-8FCD89C98E72@oracle.com>
2009-02-06 22:58         ` [PATCH] net/sunrpc/xprtsock.c: some common code found Ilpo Järvinen
     [not found]           ` <Pine.LNX.4.64.0902070040530.31875-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-07  3:22             ` David Miller
2009-02-07 16:23               ` Trond Myklebust
     [not found]                 ` <1234023804.17241.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-07 16:56                   ` Ilpo Järvinen
2009-02-07 17:22                     ` Trond Myklebust
     [not found]                       ` <1234027321.17241.25.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-08  3:00                         ` David Miller
     [not found]                     ` <Pine.LNX.4.64.0902071831210.2805-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-08  5:25                       ` J. Bruce Fields [this message]
2009-02-09 17:29                         ` Chuck Lever
2009-02-10 13:12                           ` Ilpo Järvinen
     [not found]                             ` <Pine.LNX.4.64.0902101417550.31742-x/A8LOkYjdVsRR2hCrRKtT03IgOmwywn@public.gmane.org>
2009-02-10 17:12                               ` Chuck Lever
2009-02-10 13:20                         ` Ilpo Järvinen
2009-02-10 22:28                           ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090208052543.GA20689@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen-pxSi+dnQzZMxHbG02/KK1g@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trond@netapp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox