linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: daniel.vetter@ffwll.ch, gregkh@linuxfoundation.org,
	yepeilin.cs@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] Fonts: font_acorn_8x8: Replace discarded const qualifier
Date: Mon, 2 Nov 2020 10:23:43 +0000	[thread overview]
Message-ID: <20201102102343.GK1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20201101131122.GD4127@dell>

On Sun, Nov 01, 2020 at 01:11:22PM +0000, Lee Jones wrote:
> On Sat, 31 Oct 2020, Russell King - ARM Linux admin wrote:
> 
> > On Fri, Oct 30, 2020 at 06:18:22PM +0000, Lee Jones wrote:
> > > Commit 09e5b3fd5672 ("Fonts: Support FONT_EXTRA_WORDS macros for
> > 
> > Your commit ID does not exist in mainline kernels, which makes this
> > confusing. The commit ID you should be using is 6735b4632def.
> 
> Ah yes, quite right.  That is the ID from android-3.18 where this
> issue was first seen and fixed against.  I will fix it up for
> Mainline.
> 
> Does the fix look okay to you though Russell?

Frankly, I don't know. Looking at the commit itself, it looks safe,
but it depends what this "extra" data is being used for. From what
I can see, the commit in question just adds the additional opaque
data as a member named "extra", and one is left to guess what it's
use as.

I'd have thought a small structure with named members would have
been the minimum given our standards for in-kernel code.

Why was the "const" dropped in the first place? Does this "extra"
member get written to somewhere?

So, sorry, no idea. This looks to me like a very unsatisfactory
commit, and probably something that got a very poor review.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2020-11-02 10:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 18:18 [PATCH 1/1] Fonts: font_acorn_8x8: Replace discarded const qualifier Lee Jones
2020-10-31  5:09 ` Peilin Ye
2020-10-31 10:27 ` Russell King - ARM Linux admin
2020-11-01 13:11   ` Lee Jones
2020-11-02 10:23     ` Russell King - ARM Linux admin [this message]
2020-11-02 10:30       ` Russell King - ARM Linux admin
2020-11-02 16:12       ` Peilin Ye
2020-11-02 10:56 ` Daniel Vetter
2020-11-02 11:09   ` Lee Jones
2020-11-02 11:18     ` Daniel Vetter
2020-11-02 11:30       ` Lee Jones
2020-11-02 14:50         ` Daniel Vetter
2020-11-02 16:17           ` Peilin Ye
2020-11-02 16:24             ` Lee Jones
2020-11-02 16:25               ` Lee Jones
2020-11-02 16:34               ` Peilin Ye
2020-11-02 18:32 ` [PATCH v2 1/1] Fonts: " Peilin Ye
2020-11-03  8:53   ` Lee Jones
2020-11-03  8:58     ` Daniel Vetter
2020-11-03  9:15       ` Greg KH
2020-11-03  9:52         ` Daniel Vetter
2020-11-03 10:55           ` Lee Jones
2020-11-03 11:42             ` Peilin Ye
2020-11-07  5:19             ` Peilin Ye
2020-11-07 15:36               ` Greg KH

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=20201102102343.GK1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yepeilin.cs@gmail.com \
    /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).