From: David Daney <ddaney.cavm@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Ungerer <gerg@snapgear.com>
Subject: Re: [PATCH] Remove v850 from linux/elf-em.h
Date: Mon, 21 Mar 2016 09:39:32 -0700 [thread overview]
Message-ID: <56F023C4.6060501@gmail.com> (raw)
In-Reply-To: <56ECA836.7030307@landley.net>
On 03/18/2016 06:15 PM, Rob Landley wrote:
> On 03/18/2016 12:46 PM, David Daney wrote:
>> I am not going to comment on it any more, but [commenting more]
>
> Yes you are. (And did then too.)
>
>> On 03/17/2016 07:32 PM, Rob Landley wrote:
>> [...]
>>>
>>> As I explained last email, userspace uses the libc header, not the linux
>>> header,
>>
>> The fallacy in this argument is the assertion that we know what
>> userspace does.
>
> Userspace programs that did that already broke on earlier symbol removals.
>
>> Userspace could easily do:
>>
>> #include <linux/elf-em.h>
>> .
>> case SYMBOL_YOU_WANT_TO_REMOVE:
>>
>> ¡BOOM! it is broken.
>
> So you're assuming I don't know how headers get used by userspace.
Yes, exactly. Don't feel bad about it though, because nobody else knows
either.
> That's nice. Clearly, I never would have thought of that.
>
> Once again, "As I explained last email", symbols have been removed from
> this particular header before.
Since you know, a priori, that symbols in that file are never used by
userspace, why not send a patch that moves it to include/linux/elf-em.h
so that userspace doesn't see it? Then you could remove as many symbols
as you like.
David Daney
[...]
prev parent reply other threads:[~2016-03-21 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 21:10 [PATCH] Remove v850 from linux/elf-em.h Rob Landley
2016-03-15 23:22 ` David Daney
2016-03-16 7:11 ` Rob Landley
2016-03-17 22:09 ` David Daney
2016-03-18 2:32 ` Rob Landley
2016-03-18 17:46 ` David Daney
2016-03-19 1:15 ` Rob Landley
2016-03-21 16:39 ` David Daney [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=56F023C4.6060501@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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