From: Juri Lelli <juri.lelli@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: Juri Lelli <juri.lelli@redhat.com>,
kbuild-all@01.org, tglx@linutronix.de, bigeasy@linutronix.de,
rostedt@goodmis.org, linux-rt-users@vger.kernel.org,
linux-kernel@vger.kernel.org, williams@redhat.com
Subject: Re: [RT PATCH v2] net/xfrm/xfrm_ipcomp: Protect scratch buffer with local_lock
Date: Tue, 20 Aug 2019 08:42:03 +0200 [thread overview]
Message-ID: <20190820064203.GB6860@localhost.localdomain> (raw)
In-Reply-To: <201908201356.Pffozrxv%lkp@intel.com>
Hi,
On 20/08/19 13:35, kbuild test robot wrote:
> Hi Juri,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [cannot apply to v5.3-rc5 next-20190819]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
This seems to be indeed the case, as this patch is for RT v4.19-rt
stable tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git v4.19-rt
I was under the impression that putting "RT" on the subject line (before
PATCH) would prevent build bot to pick this up, but maybe something
else/different is needed?
Thanks,
Juri
next prev parent reply other threads:[~2019-08-20 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:27 [RT PATCH v2] net/xfrm/xfrm_ipcomp: Protect scratch buffer with local_lock Juri Lelli
2019-08-19 19:57 ` Steven Rostedt
2019-08-20 6:43 ` Juri Lelli
2019-08-20 5:35 ` kbuild test robot
2019-08-20 6:42 ` Juri Lelli [this message]
2019-08-21 1:43 ` Li, Philip
2019-08-21 6:44 ` Juri Lelli
2019-08-21 7:00 ` bigeasy
2019-08-20 8:28 ` Sebastian Andrzej Siewior
2019-09-04 5:53 ` Joerg Vehlow
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=20190820064203.GB6860@localhost.localdomain \
--to=juri.lelli@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.