public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.com>,
	kees@kernel.org, andy@kernel.org, akpm@linux-foundation.org,
	linux@rasmusvillemoes.dk, senozhatsky@chromium.org,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] printf: Remove unused 'bprintf'
Date: Sun, 1 Dec 2024 11:58:09 +0000	[thread overview]
Message-ID: <Z0xPUWMps0BzAQKe@gallifrey> (raw)
In-Reply-To: <20241130223936.136b2f1c@rorschach.local.home>

* Steven Rostedt (rostedt@goodmis.org) wrote:
> On Sun, 1 Dec 2024 02:47:49 +0000
> "Dr. David Alan Gilbert" <linux@treblig.org> wrote:
> 
> > > > suggested at https://lore.kernel.org/r/20241002104807.42b4b64e@gandalf.local.home  
> > > 
> > > Yeah, since I'm basically the only user of it, it's best it goes through my
> > > testing.  
> > 
> > Hmm, did you pick this one up?
> 
> Sorry, it wasn't in my patchwork and was missed.

No problem.

> I can add it and Linus
> may even take it after -rc1. Or I'll have it in iinux-next for the next
> merge window.

Please do; no rush.

Dave

> -- Steve
> 
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2024-12-01 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 17:31 [PATCH v2] printf: Remove unused 'bprintf' linux
2024-10-03  8:13 ` Petr Mladek
2024-10-03 15:13   ` Steven Rostedt
2024-12-01  2:47     ` Dr. David Alan Gilbert
2024-12-01  3:39       ` Steven Rostedt
2024-12-01 11:58         ` Dr. David Alan Gilbert [this message]
2024-12-01 16:19           ` Steven Rostedt

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=Z0xPUWMps0BzAQKe@gallifrey \
    --to=linux@treblig.org \
    --cc=akpm@linux-foundation.org \
    --cc=andy@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.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