linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] Disable CONFIG_UACCESS_WITH_MEMCPY in Atmel config.
Date: Wed, 30 Sep 2015 00:53:17 +0200	[thread overview]
Message-ID: <20150929225317.GA9993@piout.net> (raw)
In-Reply-To: <20150929221800.GR21513@n2100.arm.linux.org.uk>

On 29/09/2015 at 23:18:01 +0100, Russell King - ARM Linux wrote :
> On Wed, Sep 30, 2015 at 12:01:40AM +0200, Alexandre Belloni wrote:
> > Hi,
> > 
> > On 29/09/2015 at 22:59:46 +0200, Jean-Christian de Rivaz wrote :
> > > Without the explicit disabling, the user will be asked and could possibly
> > > give the wrong answer as the help look as a cool feature and the condition
> > > is very hard to understand.
> > > 
> > 
> > That is not true, if you remove it from the defconfig, it will simply be
> > disabled in the final config.
> > 
> > Moreover, I would prefer a better commit message than "Russell said so"
> 
> Well, if people are going to take that kind of attitude, then I'm not
> going to bother fixing it at all.  I've got better things to do than
> chase after bugs in almost unused code and code which people shouldn't
> be enabling on their platforms.
> 
> It's not "Russell said so" but "Nicolas, the author of the code, said so."
> I'm merely passing the information along.  Search the archives if you don't
> believe me, it's been discussed in the last couple of months, including
> potentially removing this code.
> 
> I regard this code as a maintanence burden, one that I personally can do
> without.
> 

Come on, I never said it was not worth fixing, I'm just saying the
commit message doesn't carry the proper explanation. I would prefer
something a bit more technical.
A better commit message could point to the discussion you are referring
to for example so that the maintainers (btw they are not in copy) don't
have to look it up themselves.


-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-29 22:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 20:03 [PATCH 1/1] Disable CONFIG_UACCESS_WITH_MEMCPY in Atmel config jc at eclis.ch
2015-09-29 20:13 ` Nicolas Pitre
2015-09-29 20:35 ` Uwe Kleine-König
2015-09-29 20:59   ` Jean-Christian de Rivaz
2015-09-29 22:01     ` Alexandre Belloni
2015-09-29 22:18       ` Russell King - ARM Linux
2015-09-29 22:53         ` Alexandre Belloni [this message]
2015-09-29 23:19           ` Nicolas Pitre
  -- strict thread matches above, loose matches on Subject: below --
2015-09-29 22:32 jc at eclis.ch
2015-09-30  6:10 ` Uwe Kleine-König
2015-09-30 10:13   ` Jean-Christian de Rivaz

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=20150929225317.GA9993@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --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).