[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180629111130.fa4cc7d2bcd55e07a5298c1c@arm.com>
Date: Fri, 29 Jun 2018 11:11:30 -0500
From: Kim Phillips <kim.phillips@....com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Thomas Richter <tmricht@...ux.vnet.ibm.com>,
Michael Petlan <mpetlan@...hat.com>,
Hendrik Brückner
<brueckner@...ux.vnet.ibm.com>,
Sandipan Das <sandipan@...ux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] perf test shell: make perf inet_pton test more
portable
On Fri, 29 Jun 2018 12:21:55 -0300
Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> Em Thu, Jun 21, 2018 at 03:32:50PM -0500, Kim Phillips escreveu:
> > On Thu, 21 Jun 2018 12:18:00 -0300
> > Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> >
> > > Would be good if we had some utility that given a two files, one with
> > > regexps, could tell if, line by line, those expressions matched, better,
> > > one that is present in all these OSes...
> >
> > I didn't find any, but given the two-file notion might be acceptable,
> > hopefully you might find the following more readable/acceptable?:
>
> Looks better, you build the expected lines in a separate file, then read
> both it and the output, then do the matching, cleaner. And I assume it
> works with dash, right?
Yes, of course :)
I'll re-send via a new v2 series as 1/2 wasn't git-am friendly, and
I've uncovered another minor bashism.
Kim
Powered by blists - more mailing lists