From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 4/4] memorder: Remove 'snippet' meta command in stray litmus test
Date: Wed, 13 Feb 2019 08:04:26 -0800 [thread overview]
Message-ID: <20190213160426.GA10844@linux.ibm.com> (raw)
In-Reply-To: <20190212234542.GV4240@linux.ibm.com>
On Tue, Feb 12, 2019 at 03:45:42PM -0800, Paul E. McKenney wrote:
> On Wed, Feb 13, 2019 at 07:11:02AM +0900, Akira Yokosawa wrote:
> > On 2019/02/12 08:16:31 -0800, Paul E. McKenney wrote:
> > > On Wed, Feb 13, 2019 at 12:39:38AM +0900, Akira Yokosawa wrote:
> > >> >From 0ddf5c5ea4a66a0d6bff1b6c0ce32682459c20ad Mon Sep 17 00:00:00 2001
> > >> From: Akira Yokosawa <akiyks@gmail.com>
> > >> Date: Tue, 12 Feb 2019 23:18:29 +0900
> > >> Subject: [PATCH 4/4] memorder: Remove 'snippet' meta command in stray litmus test
> > >>
> > >> C-SB+o-rcusync-o+rl-rul-o.litmus is identical to
> > >> C-SB+o-rcusync-o+rl-o-rul-o.litmus and causes "make" to emit
> > >> warning:
> > >>
> > >> target 'CodeSamples/formal/herd/C-SB+o-rcusync-o+rl-o-rul-o@whole.fcv'
> > >> given more than once in the same rule
> > >>
> > >> This commit removes "snippet" meta commands in the test.
> > >> Just removing the file can cause a build error afterward.
> > >> A "make clean" will resolve the error, but keeping the file
> > >> looks like a reasonable approach to avoid surprising people.
> > >> The file can be removed in the near future when most active
> > >> users have updated snippets.d.
> > >
> > > Unless I am confused, this litmus test appears as Listing 15.37.
> >
> > Listing 15.37 is "C-SB+o-rcusync-o+rl-o-rul-o".
> > The file I modified is "C-SB+o-rcusync-o+rl-rul-o.litmus" (note the
> > missing "-o-" in the final part") but contains the same test
> > "C-SB+o-rcusync-o+rl-o-rul-o". There exists
> > C-SB+o-rcusync-o+rl-o-rul-o.litmus which contains the same test
> > "C-SB+o-rcusync-o+rl-o-rul-o". So C-SB+o-rcusync-o+rl-rul-o.litmus
> > can be safely removed. But this patch removes the snippet meta-commands
> > instead.
> >
> > Have I made the point clearer?
>
> You have! My confusion stemmed from the fact that these two files
> are identical, as you say:
>
> CodeSamples/formal/herd/C-SB+o-rcusync-o+rl-rul-o.litmus
> CodeSamples/formal/herd/C-SB+o-rcusync-o+rl-o-rul-o.litmus
>
> I was searching based on the name within the file rather than the
> filename. In short, we can just get rid of the unused file.
>
> Apologies for my confusion!
And I have removed it with your Reported-by, and thank you for catching this!
Thanx, Paul
next prev parent reply other threads:[~2019-02-13 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 15:31 [PATCH 0/4] formal/spinhint: Clarify hashtable sizes used in tables Akira Yokosawa
2019-02-12 15:33 ` [PATCH 1/4] formal/spinhint: Clarify hashtable sizes used in Tables 12.2 and 12.3 Akira Yokosawa
2019-02-12 15:35 ` [PATCH 2/4] Set default fontfamily for snippets of 'fancyvrb' Akira Yokosawa
2019-02-12 15:37 ` [PATCH 3/4] Change monospace font of snippets for targets 'mss', 'msns', and 'msn' Akira Yokosawa
2019-02-12 15:39 ` [PATCH 4/4] memorder: Remove 'snippet' meta command in stray litmus test Akira Yokosawa
2019-02-12 16:16 ` Paul E. McKenney
2019-02-12 22:11 ` Akira Yokosawa
2019-02-12 23:45 ` Paul E. McKenney
2019-02-13 16:04 ` Paul E. McKenney [this message]
2019-02-12 16:38 ` [PATCH 0/4] formal/spinhint: Clarify hashtable sizes used in tables Paul E. McKenney
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=20190213160426.GA10844@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.org \
/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