[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAG=yYw=t1-oZy5=E1j_=Qwx_0epmPhqQPJD2HkCYpQnxDroT2g@mail.gmail.com>
Date: Mon, 28 Jan 2019 23:55:14 +0530
From: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
To: lkml <linux-kernel@...r.kernel.org>
Subject: Fwd: [PATCH] selftests: kmod: worked on errors which breaks the
overall execution of the test script
---------- Forwarded message ---------
From: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Date: Mon, Jan 28, 2019 at 11:33 PM
Subject: Re: [PATCH] selftests: kmod: worked on errors which breaks
the overall execution of the test script
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Shuah Khan <shuah@...nel.org>, lkml
<linux-kernel@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
>
> on what
> distribution and version of bash does this break?
$cat /etc/issue
Debian GNU/Linux buster/sid \n \l
$
$uname -a
Linux debian 5.0.0-rc1+ #3 SMP Fri Jan 25 21:27:20 IST 2019 x86_64 GNU/Linux
$echo $BASH_VERSION
5.0.0(1)-release
$
>
> The commit log should
> refer to this and it would help me confirm the issue.
i like to send another version of patch which has things in the commit log
>
> > because an array is passed
> Which is the array?
${TEST_DATA#*:*:}
the above stuff sometimes contains array but not initially
>
> get_test_enabled() is supposed to do what you do open-handed here.
> So the better question is why are you getting an array returned
> for your version of bash.
>
iam not returning an array but ${TEST_DATA#*:*:} sometimes holds array
--
software engineer
rajagiri school of engineering and technology
--
software engineer
rajagiri school of engineering and technology
Powered by blists - more mailing lists