Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jan Kara <jack@suse.cz>
Cc: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>,
	linux-kernel@vger.kernel.org, Jan Kara <jack@suse.com>,
	Yangtao Li <frank.li@vivo.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	loongarch@lists.linux.dev, linux-mips@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH] quota: remove CONFIG_PRINT_QUOTA_WARNING code
Date: Thu, 30 Jul 2026 16:48:16 +0200	[thread overview]
Message-ID: <2026073007-nearby-debtless-cfd6@gregkh> (raw)
In-Reply-To: <5cxumyfngrzddts3igtfqhogyabpjf5jywabpjclimnzy5pug6@e34tyng6thbg>

On Mon, Jul 27, 2026 at 09:53:30PM +0200, Jan Kara wrote:
> On Wed 22-07-26 08:01:55, Jiri Slaby (SUSE) wrote:
> > CONFIG_PRINT_QUOTA_WARNING was marked as BROKEN in 2023 by 36d532d713db
> > ("quota: mark PRINT_QUOTA_WARNING as BROKEN").
> > 
> > The code is apparently unused and uninteresting, so remove it all, incl.
> > the abuse of TTY.
> > 
> > Signed-off-by: Jiri Slaby (SUSE) <jirislaby@kernel.org>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Jan Kara <jack@suse.com>
> > Cc: Yangtao Li <frank.li@vivo.com>
> 
> OK, I'm for trying this because so far nobody was complaining about the
> feature getting marked as BROKEN. Let's see how it goes...

Great!

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

      reply	other threads:[~2026-07-30 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  6:01 [PATCH] quota: remove CONFIG_PRINT_QUOTA_WARNING code Jiri Slaby (SUSE)
2026-07-27 19:53 ` Jan Kara
2026-07-30 14:48   ` Greg Kroah-Hartman [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=2026073007-nearby-debtless-cfd6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=chenhuacai@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=jirislaby@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=tsbogend@alpha.franken.de \
    /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