public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Linux Kernel Functional Testing <lkft@linaro.org>,
	KERNEL SELFTEST FRAMEWORK <linux-kselftest@vger.kernel.org>,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	lkft-triage@lists.linaro.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"Chang S. Bae" <chang.seok.bae@intel.com>,
	Len Brown <len.brown@intel.com>, Borislav Petkov <bp@suse.de>,
	Stas Sergeev <stsp@list.ru>, Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Andy Lutomirski <luto@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Nathan Chancellor <nathan@kernel.org>,
	llvm@lists.linux.dev, Naresh Kamboju <naresh.kamboju@linaro.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: sigaltstack: fix -Wuninitialized
Date: Mon, 20 Mar 2023 17:30:15 -0600	[thread overview]
Message-ID: <155a112f-c6e7-57a0-b8bd-6b3bde85d685@kernel.org> (raw)
In-Reply-To: <CAKwvOdnM9WjxHY_uw_0nyhGTZDuQ+730NrX2sgw9cBLkrhF8oA@mail.gmail.com>

On 3/20/23 12:41, Nick Desaulniers wrote:
> Hi Shuah,
> Did this get picked up? Just checking it doesn't fall through the cracks.
> EOM
> 

Thanks for the ping. Now applied Applied to linux-kselftest fixes
branch for rc4.

Somehow this one didn't show up in my inbox and responses made it
fine. I have to check what's happening to emails on my end.

thanks,
-- Shuah


      reply	other threads:[~2023-03-20 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 19:59 [PATCH] selftests: sigaltstack: fix -Wuninitialized Nick Desaulniers
2023-03-09  0:01 ` Kees Cook
2023-03-13  9:50 ` Naresh Kamboju
2023-03-20 18:41   ` Nick Desaulniers
2023-03-20 23:30     ` shuah [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=155a112f-c6e7-57a0-b8bd-6b3bde85d685@kernel.org \
    --to=shuah@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=bp@suse.de \
    --cc=chang.seok.bae@intel.com \
    --cc=keescook@chromium.org \
    --cc=len.brown@intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=luto@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=skhan@linuxfoundation.org \
    --cc=stsp@list.ru \
    --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