From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Lennox Wu <lennox.wu@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RESEND] score: remove unused CPU_SCORE7 Kconfig parameter
Date: Mon, 10 Mar 2014 09:45:20 +0100 [thread overview]
Message-ID: <531D7BA0.9040802@free-electrons.com> (raw)
In-Reply-To: <CAF0htA5OyL=cm7z5BMy1r7OcW_a-4WGEUbLzveR4fWgAC5av0Q@mail.gmail.com>
On 03/08/2014 07:34 AM, Lennox Wu wrote:
> HI Michael,
> According to my record, I had told you we have another
> processor(2013/11/4), hence, we need the parameter.
> We just wirte it done first. Do you remember it?
Hi Lennox,
I missed your reply because it got deleted by mistake. My apologies!
However, I agree with Paul in the sense that keeping such a parameter
for a long time before it is actually used just adds some unnecessary
noise, hiding the parameters that would really need removing.
And indeed, it will be hard to stop other people from reporting this
again in the future...
Thank you for your replies.
Cheers,
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
prev parent reply other threads:[~2014-03-10 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 9:58 [PATCH] score: remove unused CPU_SCORE7 Kconfig parameter Michael Opdenacker
2013-11-04 14:52 ` Lennox Wu
2013-11-04 15:03 ` Michael Opdenacker
2013-12-09 5:33 ` [PATCH][RESEND] " Michael Opdenacker
2014-03-08 5:26 ` [PATCH] [RESEND] " Michael Opdenacker
2014-03-08 6:34 ` Lennox Wu
2014-03-08 20:00 ` Paul Bolle
2014-03-08 20:27 ` Lennox Wu
2014-03-08 21:02 ` Paul Bolle
2014-03-09 5:33 ` Lennox Wu
2014-03-10 8:45 ` Michael Opdenacker [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=531D7BA0.9040802@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.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