From: me at tobin.cc (Tobin C. Harding)
Subject: [PATCH v3 0/7] lib/string: Add strscpy_pad() function
Date: Fri, 8 Mar 2019 08:18:58 +1100 [thread overview]
Message-ID: <20190307211858.GA28495@eros.localdomain> (raw)
In-Reply-To: <20190306214934.GA16461@eros.localdomain>
On Thu, Mar 07, 2019 at 08:49:34AM +1100, Tobin C. Harding wrote:
> On Thu, Mar 07, 2019 at 08:42:19AM +1100, Tobin C. Harding wrote:
> > Hi,
>
> Man, I didn't see the merge window was open, I thought rc8 only came out
> on Sunday.
>
> Sorry, please ignore this. Will re-send again later in the cycle.
Multiple people have suggested to me (offlist) that it is fine to go
right ahead and send patches whenever.
Shuah, do you take patches to kselftest at any stage of the dev cycle?
Kees, same question please?
thanks,
Tobin.
WARNING: multiple messages have this Message-ID (diff)
From: me@tobin.cc (Tobin C. Harding)
Subject: [PATCH v3 0/7] lib/string: Add strscpy_pad() function
Date: Fri, 8 Mar 2019 08:18:58 +1100 [thread overview]
Message-ID: <20190307211858.GA28495@eros.localdomain> (raw)
Message-ID: <20190307211858.64_2FIMPMCoK6M7rka4-NkoY-VB-P3pPcJwlKnHbpXg@z> (raw)
In-Reply-To: <20190306214934.GA16461@eros.localdomain>
On Thu, Mar 07, 2019@08:49:34AM +1100, Tobin C. Harding wrote:
> On Thu, Mar 07, 2019@08:42:19AM +1100, Tobin C. Harding wrote:
> > Hi,
>
> Man, I didn't see the merge window was open, I thought rc8 only came out
> on Sunday.
>
> Sorry, please ignore this. Will re-send again later in the cycle.
Multiple people have suggested to me (offlist) that it is fine to go
right ahead and send patches whenever.
Shuah, do you take patches to kselftest at any stage of the dev cycle?
Kees, same question please?
thanks,
Tobin.
next prev parent reply other threads:[~2019-03-07 21:18 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 21:42 [PATCH v3 0/7] lib/string: Add strscpy_pad() function tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-03-06 21:42 ` [PATCH v3 1/7] lib/test_printf: Add empty module_exit function tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:24 ` keescook
2019-04-02 21:24 ` Kees Cook
2019-03-06 21:42 ` [PATCH v3 2/7] kselftest: Add test runner creation script tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:27 ` keescook
2019-04-02 21:27 ` Kees Cook
2019-04-02 21:33 ` rdunlap
2019-04-02 21:33 ` Randy Dunlap
2019-04-04 23:16 ` me
2019-04-04 23:16 ` Tobin C. Harding
2019-03-06 21:42 ` [PATCH v3 3/7] kselftest/lib: Use new shell runner to define tests tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:29 ` keescook
2019-04-02 21:29 ` Kees Cook
2019-04-02 21:45 ` keescook
2019-04-02 21:45 ` Kees Cook
2019-04-02 21:51 ` keescook
2019-04-02 21:51 ` Kees Cook
2019-03-06 21:42 ` [PATCH v3 4/7] kselftest: Add test module framework header tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:31 ` keescook
2019-04-02 21:31 ` Kees Cook
2019-03-06 21:42 ` [PATCH v3 5/7] lib: Use new kselftest header tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:32 ` keescook
2019-04-02 21:32 ` Kees Cook
2019-03-06 21:42 ` [PATCH v3 6/7] lib/string: Add strscpy_pad() function tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:35 ` keescook
2019-04-02 21:35 ` Kees Cook
2019-03-06 21:42 ` [PATCH v3 7/7] lib: Add test module for strscpy_pad tobin
2019-03-06 21:42 ` Tobin C. Harding
2019-04-02 21:36 ` keescook
2019-04-02 21:36 ` Kees Cook
2019-03-06 21:49 ` [PATCH v3 0/7] lib/string: Add strscpy_pad() function me
2019-03-06 21:49 ` Tobin C. Harding
2019-03-07 21:18 ` me [this message]
2019-03-07 21:18 ` Tobin C. Harding
2019-03-07 22:43 ` keescook
2019-03-07 22:43 ` Kees Cook
2019-03-08 5:23 ` me
2019-03-08 5:23 ` Tobin C. Harding
2019-03-08 16:18 ` keescook
2019-03-08 16:18 ` Kees Cook
2019-04-02 21:37 ` keescook
2019-04-02 21:37 ` Kees Cook
2019-04-03 0:25 ` me
2019-04-03 0:25 ` Tobin C. Harding
2019-04-03 0:29 ` shuah
2019-04-03 0:29 ` 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=20190307211858.GA28495@eros.localdomain \
--to=linux-kselftest@vger.kernel.org \
/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).