From: shuah <shuah@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tycho Andersen <tycho@tycho.ws>, shuah <shuah@kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the kselftest tree
Date: Wed, 4 Sep 2019 08:07:59 -0600 [thread overview]
Message-ID: <9e918857-0ff2-3a36-3445-76eb739697c5@kernel.org> (raw)
In-Reply-To: <20190902073909.7fc3fe5e@canb.auug.org.au>
On 9/1/19 3:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> c321d43b8da1 ("selftests/seccomp: fix build on older kernels")
>
> Fixes tag
>
> Fixes: Commit 201766a20e30 ("ptrace: add PTRACE_GET_SYSCALL_INFO request")
>
> has these problem(s):
>
> - leading word 'Commit' unexpected
>
Thanks. I fixed the one in the commit log. I will fix this one as well.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-09-04 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 21:39 linux-next: Fixes tag needs some work in the kselftest tree Stephen Rothwell
2019-09-04 14:07 ` shuah [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-13 15:05 Stephen Rothwell
2019-05-13 15:57 ` shuah
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=9e918857-0ff2-3a36-3445-76eb739697c5@kernel.org \
--to=shuah@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tycho@tycho.ws \
/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;
as well as URLs for NNTP newsgroup(s).