From: John Kacur <jkacur@redhat.com>
To: Sultan Alsawaf <sultan@kerneltoast.com>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
sebastian@breakpoint.cc, tglx@linutronix.de, rostedt@goodmis.org
Subject: Re: [PATCH] rt-tests: backfire: Don't include asm/uaccess.h directly
Date: Tue, 17 Sep 2019 16:14:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.21.1909171613150.3853@planxty> (raw)
In-Reply-To: <20190917071546.GA27627@sultan-box>
On Tue, 17 Sep 2019, Sultan Alsawaf wrote:
> On Mon, Sep 16, 2019 at 11:57:32PM +0200, John Kacur wrote:
> > Signed-off-by: John Kacur <jkacur@redhat.com>
> > But please in the future
> > 1. Don't cc lkml on this
> > 2. Include the maintainers in your patch
>
> Hi,
>
> Thanks for the sign-off. I was following the instructions listed here:
> https://wiki.linuxfoundation.org/realtime/communication/send_rt_patches
Those are the instructions for rt kernel code.
rt-tests is a users space program to test the performance of the rt
kernel.
Always just check if there is a MAINTAINERS file (there is)
when you clone the git repo.
Thanks
John
>
> I couldn't find any documentation of how to send patches for rt-tests. Is there
> a different set of patch submission instructions on a wiki somewhere I missed?
>
> Thanks,
> Sultan
>
next prev parent reply other threads:[~2019-09-17 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 19:13 [PATCH] rt-tests: backfire: Don't include asm/uaccess.h directly Sultan Alsawaf
2019-09-16 21:57 ` John Kacur
2019-09-17 7:15 ` Sultan Alsawaf
2019-09-17 10:28 ` Kurt Kanzenbach
2019-09-17 14:14 ` John Kacur [this message]
2019-09-17 10:24 ` Sebastian Andrzej Siewior
2019-09-17 14:12 ` John Kacur
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=alpine.LFD.2.21.1909171613150.3853@planxty \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sebastian@breakpoint.cc \
--cc=sultan@kerneltoast.com \
--cc=tglx@linutronix.de \
/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