From: Artem Bityutskiy <dedekind1@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/1 (variant 2)] remap-log: fix map generator
Date: Thu, 3 Nov 2011 16:01:52 +0200 [thread overview]
Message-ID: <1320328912-15148-3-git-send-email-dedekind1@gmail.com> (raw)
In-Reply-To: <1320328912-15148-1-git-send-email-dedekind1@gmail.com>
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
This patch fixes a bug in the 'parse_diff()' function. This function iterates
over every changed file and every hunk in this file and at each iteration it
prints the hunk's map for the _previous_ iteration. This is taken into account
when it switches to the next file - just before starting processing hunks in
this file, it prints the map for the last hunk of the _previous_ file.
However, if we are at the very last file or we have a diff which changes only
one single file, and the last hunk is processed - we do not print the map of
this last hunk and just exit. The result is a buggy map - because the map of
the very last hunk is not printed.
Here is a short example to demonstrate the bug. The diff is:
|||diff --git a/sound/soc/codecs/sn95031.c b/sound/soc/codecs/sn95031.c
|||index 920e7bb..8c43fdd 100644
|||--- a/sound/soc/codecs/sn95031.c
|||+++ b/sound/soc/codecs/sn95031.c
|||@@ -811,0 +812 @@ static int sn95031_pcm_hs_mute(struct snd_soc_dai *dai, int mute)
|||+ int tmp = !mute;
|||@@ -813 +814 @@ static int sn95031_pcm_hs_mute(struct snd_soc_dai *dai, int mute)
|||- SN95031_HSLVOLCTRL, BIT(7), (!mute << 7));
|||+ SN95031_HSLVOLCTRL, BIT(7), tmp << 7);
|||@@ -815 +816,3 @@ static int sn95031_pcm_hs_mute(struct snd_soc_dai *dai, int mute)
|||- SN95031_HSRVOLCTRL, BIT(7), (!mute << 7));
|||+ SN95031_HSRVOLCTRL, BIT(7), tmp << 7);
|||+ snd_soc_update_bits(dai->codec,
|||+ SN95031_DRIVEREN, BIT(0) | BIT(1), tmp | tmp << 1);
And remap-log generates an incorrect map:
M sound/soc/codecs/sn95031.c sound/soc/codecs/sn95031.c
1 1
812 813
813 0
814 815
815 0
Notice that the last map entry basically says that all lines in the old file
starting from line 815 have been deleted, which is not true - only one line
number 815 has been deleted.
The correct map should look like this:
M sound/soc/codecs/sn95031.c sound/soc/codecs/sn95031.c
1 1
812 813
813 0
814 815
815 0
816 819
To fix the bug this patch prints the map of the last hung just before
'parse_diff()' exits.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
---
tools/remap-log.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/tools/remap-log.c b/tools/remap-log.c
index 327b870..ee79ed9 100644
--- a/tools/remap-log.c
+++ b/tools/remap-log.c
@@ -424,6 +424,9 @@ void parse_diff(void)
break;
}
}
+
+ if (!suppress && skipping && from + to != 2)
+ printf("%d %d\n", from, to);
return;
Ediff:
die("odd diff");
--
1.7.7.1
next prev parent reply other threads:[~2011-11-03 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 14:01 [PATCH 0/1] " Artem Bityutskiy
2011-11-03 14:01 ` [PATCH 1/1 (variant 1)] " Artem Bityutskiy
2011-11-03 14:01 ` Artem Bityutskiy [this message]
2011-11-03 17:49 ` [PATCH 0/1] " Artem Bityutskiy
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=1320328912-15148-3-git-send-email-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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
Powered by JetHome