From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: gregkh@linuxfoundation.org, keescook@chromium.org,
willy@infradead.org, senozhatsky@chromium.org, list@mail.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH 0/2] seq_buf: Export seq_buf_putc() &nd seq_buf_puts()
Date: Wed, 1 Nov 2023 22:59:25 +0100 [thread overview]
Message-ID: <ee352f12-084d-45d4-9c8e-172e073b7e36@wanadoo.fr> (raw)
In-Reply-To: <20231101141705.4208d441@gandalf.local.home>
Le 01/11/2023 à 19:17, Steven Rostedt a écrit :
> On Wed, 1 Nov 2023 18:59:04 +0100
> Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
>
>> seq_buf_putc() has a potential real use-case (link in the patch), but
>> seq_buf_puts() has currently no forseen use-case, so I have split it in 2
>> patches if only the 1st one is accepted.
>>
>> Christophe JAILLET (2):
>> seq_buf: Export seq_buf_putc()
>> seq_buf: Export seq_buf_puts()
>>
>> lib/seq_buf.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>
> I can pull these in as I'm getting ready for my pull request to Linus soon
> (and just kicked off my testing).
>
> Or do you need them as part of the patch you mentioned? When does that need
> to go in? Can it wait till it hits Linus's tree?
>
> -- Steve
>
You timing will be mine, no need to hurry.
I'll see when it reaches -next.
Thanks for taking care of it.
CJ
prev parent reply other threads:[~2023-11-01 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 17:59 Christophe JAILLET
2023-11-01 17:59 ` [PATCH 1/2] seq_buf: Export seq_buf_putc() Christophe JAILLET
2023-11-01 17:59 ` [PATCH 2/2] seq_buf: Export seq_buf_puts() Christophe JAILLET
2023-11-01 18:17 ` [PATCH 0/2] seq_buf: Export seq_buf_putc() &nd seq_buf_puts() Steven Rostedt
2023-11-01 21:59 ` Christophe JAILLET [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=ee352f12-084d-45d4-9c8e-172e073b7e36@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list@mail.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®