public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Olof Johansson <olof@lixom.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	David Howells <dhowells@redhat.com>,
	Patrick Bellasi <patrick.bellasi@arm.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-kbuild@vger.kernel.org,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert kheaders feature
Date: Wed, 5 Feb 2020 21:48:41 +0000	[thread overview]
Message-ID: <20200205214841.GB1468203@kroah.com> (raw)
In-Reply-To: <CAEXW_YSU_Zm24R2TYFQd42CfXyotowv42BbvbvKfSFbZGUqOHQ@mail.gmail.com>

On Wed, Feb 05, 2020 at 01:35:56PM -0800, Joel Fernandes wrote:
> On Wed, Feb 5, 2020 at 1:33 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> [snip]
> > > > like the BTF approach is significantly better and said users are
> > > > hopefully moving forward to it quickly, and if they can't move
> > > > forward, then they're likely also not going to move forward to newer
> > > > kernels either?
> > >
> > > I think BCC runs on a lot of upstream machines. I think the migration
> > > strategy is a matter of opinion, one way is to take it out and cause some
> > > pain in the hope that users/tools will migrate soon (while probably carrying
> > > the reverted patches out of tree). Another is to migrate the tools first and
> > > then take it out (which has its own disadvantages such as introducing even
> > > more users of it while it is still upstream).
> >
> > Do we "know" what tools today require this, and what needs to be done to
> > "fix" them?  If we don't know that, then there's no way to drop this,
> > pretty much ever :(
> 
> Is there a real reason to drop it or a problem dropping this solves though?

Olof had some reasons, but as we were drinking at the time when it came
up last night, I can't really remember them specifically.  Hopefully he
does :)

But that didn't answer my question of "who is still using this"?  I was
hoping we actually knew this given it was created for specific users.

thanks,

greg k-h

  reply	other threads:[~2020-02-05 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 15:46 [PATCH] Revert kheaders feature Greg Kroah-Hartman
2020-02-05 16:02 ` Joel Fernandes
2020-02-05 16:41   ` Joel Fernandes
2020-02-05 16:55   ` Olof Johansson
2020-02-05 17:13     ` Joel Fernandes
2020-02-05 21:33       ` Greg Kroah-Hartman
2020-02-05 21:35         ` Joel Fernandes
2020-02-05 21:48           ` Greg Kroah-Hartman [this message]
2020-02-05 21:53             ` Joel Fernandes
2020-02-06  7:04               ` Greg Kroah-Hartman

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=20200205214841.GB1468203@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ast@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=joel@joelfernandes.org \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=olof@lixom.net \
    --cc=patrick.bellasi@arm.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.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