linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: compressed: discard ksym/kcrctab input section
Date: Fri, 20 Oct 2017 17:54:33 +0100	[thread overview]
Message-ID: <20171020165433.GI20805@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAKv+Gu_FqQjXLH6C8+pVyvfWqgL+e2g8geRG+t0kBxt49ObY-Q@mail.gmail.com>

On Fri, Oct 20, 2017 at 05:36:08PM +0100, Ard Biesheuvel wrote:
> Why would you have to choose between these patches? You can simply
> apply mine as a bug fix, and postpone the le_struct.h discussion for
> the next cycle.

It's not a choice between these two patches.  I think we need Arnd's
patch, because we know that fixes Romain Izard's problem.  If I apply
just your patch, then Gregory stops complaining, and there'll be
nothing to remind us of this issue - Romain isn't shouting about it.
That's a problem, because it's a real bug that then gets forgotten
about.

Or do we have evidence that your patch fixes Romain Izard's problem
as well?  I don't see any such suggestion.

So, let me go back to the dart board... I just don't have the
information to be able to make any decision on this, so stop asking
me for a decision on something I know nothing about.  Either provide
me with some information I can base a decision on, or stop asking
for a decision.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  reply	other threads:[~2017-10-20 16:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 15:31 [PATCH] ARM: compressed: discard ksym/kcrctab input section Ard Biesheuvel
2017-09-08 15:39 ` Gregory CLEMENT
2017-09-08 15:41   ` Ard Biesheuvel
2017-10-04 12:16 ` Gregory CLEMENT
2017-10-04 12:20   ` Ard Biesheuvel
2017-10-04 12:43     ` Russell King - ARM Linux
2017-10-09 12:39       ` Ard Biesheuvel
2017-10-12  9:24         ` Gregory CLEMENT
2017-10-12  9:45           ` Russell King - ARM Linux
2017-10-12 19:03             ` Ard Biesheuvel
2017-10-20 15:25               ` Gregory CLEMENT
2017-10-20 15:28                 ` Ard Biesheuvel
2017-10-20 16:11                   ` Russell King - ARM Linux
2017-10-20 16:20                     ` Ard Biesheuvel
2017-10-20 16:32                       ` Russell King - ARM Linux
2017-10-20 16:36                         ` Ard Biesheuvel
2017-10-20 16:54                           ` Russell King - ARM Linux [this message]
2017-10-20 17:12                             ` Ard Biesheuvel
2017-10-21  7:56 ` Matthias Brugger
2017-10-21  8:14   ` Ard Biesheuvel
2017-10-22 22:00     ` Matthias Brugger
2017-10-23  9:29       ` Russell King - ARM Linux
2017-10-23 11:48         ` Russell King - ARM Linux
2017-10-23 21:17           ` Matthias Brugger
2017-10-23 22:19             ` Russell King - ARM Linux
2017-10-24  6:51               ` Matthias Brugger
2017-10-23 21:15         ` Matthias Brugger
2017-10-23 21:32     ` Matthias Brugger
2017-10-23 22:29       ` Russell King - ARM Linux
2017-10-24  8:36       ` Andrea Adami

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=20171020165433.GI20805@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).