[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ee352f12-084d-45d4-9c8e-172e073b7e36@wanadoo.fr>
Date: Wed, 1 Nov 2023 22:59:25 +0100
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: gregkh@...uxfoundation.org, keescook@...omium.org,
willy@...radead.org, senozhatsky@...omium.org, list@...l.com,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
"Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH 0/2] seq_buf: Export seq_buf_putc() &nd seq_buf_puts()
Le 01/11/2023 à 19:17, Steven Rostedt a écrit :
> On Wed, 1 Nov 2023 18:59:04 +0100
> Christophe JAILLET <christophe.jaillet@...adoo.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
Powered by blists - more mailing lists