public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: zhong jiang <zhongjiang@huawei.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4/mballoc: Remove unneeded variable "err"
Date: Sun, 5 Aug 2018 10:49:02 -0400	[thread overview]
Message-ID: <20180805144902.GB26138@thunk.org> (raw)
In-Reply-To: <5B66F4B5.8030908@huawei.com>

On Sun, Aug 05, 2018 at 08:59:33PM +0800, zhong jiang wrote:
>  I create the diff in this patch again ,but get the same result .
>  the git version is git version 1.7.12.4 but I create the diff in
>  git version 1.8.3.1. It shows the correct function name.

Ah, OK, so it was a git bug.  Whew!  Glad to have that mystery solved.  :-)

        	      	    	      	     - Ted

      reply	other threads:[~2018-08-05 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 11:04 [PATCH] ext4/mballoc: Remove unneeded variable "err" zhong jiang
2018-08-04 21:24 ` Theodore Y. Ts'o
2018-08-05 12:59   ` zhong jiang
2018-08-05 14:49     ` Theodore Y. Ts'o [this message]

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=20180805144902.GB26138@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhongjiang@huawei.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