public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/ioctl_loop01: Add linux git tag
Date: Fri, 8 May 2020 15:40:11 +0800	[thread overview]
Message-ID: <5EB50CDB.5060909@cn.fujitsu.com> (raw)
In-Reply-To: <1588916828-4228-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>

Hi Xu,

The commit actually fixes the failure of ioctl_loop01 so I will apply it 
shortly.
Acked-by: Xiao Yang <yangx.jy@cn.fujitsu.com>

Thanks,
Xiao Yang
On 2020/5/8 13:47, Yang Xu wrote:
> Signed-off-by: Yang Xu<xuyang2018.jy@cn.fujitsu.com>
> ---
>   testcases/kernel/syscalls/ioctl/ioctl_loop01.c | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/testcases/kernel/syscalls/ioctl/ioctl_loop01.c b/testcases/kernel/syscalls/ioctl/ioctl_loop01.c
> index faef22e47..2d9733f95 100644
> --- a/testcases/kernel/syscalls/ioctl/ioctl_loop01.c
> +++ b/testcases/kernel/syscalls/ioctl/ioctl_loop01.c
> @@ -12,6 +12,9 @@
>    * For LO_FLAGS_PARTSCAN flag, it is the same as LO_FLAGS_AUTOCLEAR flag.
>    * But we also check whether we can scan partition table correctly ie check
>    * whether /dev/loopnp1 and /sys/bloclk/loop0/loop0p1 existed.
> + *
> + * It is also a regression test for kernel
> + * commit 10c70d95c0f2 ("block: remove the bd_openers checks in blk_drop_partitions").
>    */
>
>   #include<stdio.h>
> @@ -137,5 +140,9 @@ static struct tst_test test = {
>   		"loop",
>   		NULL
>   	},
> +	.tags = (const struct tst_tag[]) {
> +		{"linux-git", "10c70d95c0f2"},
> +		{}
> +	},
>   	.needs_tmpdir = 1,
>   };




      reply	other threads:[~2020-05-08  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  5:47 [LTP] [PATCH] syscalls/ioctl_loop01: Add linux git tag Yang Xu
2020-05-08  7:40 ` Xiao Yang [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=5EB50CDB.5060909@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=ltp@lists.linux.it \
    /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