[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231101141705.4208d441@gandalf.local.home>
Date: Wed, 1 Nov 2023 14:17:05 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
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()
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
Powered by blists - more mailing lists