linux-kernel - Re: [PATCH] Blackfin: bf537: rename "CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1392310984.23598.15.camel@x220>
Date:	Thu, 13 Feb 2014 18:03:04 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Lars-Peter Clausen <lars@...afoo.de>,
	Steven Miao <realmz6@...il.com>,
	adi-buildroot-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Blackfin: bf537: rename "CONFIG_ADT7310" and friends

On Thu, 2014-02-13 at 08:29 -0800, Guenter Roeck wrote:
> On 02/13/2014 02:31 AM, Paul Bolle wrote:
> > On Thu, 2014-02-13 at 10:57 +0100, Paul Bolle wrote:
> >> This issue is still present in v3.14-rc2. Guenter's suggestion is the
> >> easiest way out. Should I submit a trivial patch that just removes the
> >> dead code depending on never defined CONFIG_ADT7310 and
> >> CONFIG_ADT7310_MODULE?
> >
> 
> My suggestion was to remove the ifdefs, not the code, and if I
> understand the reply correctly that won't work because in that
> case multiple devices would be registered with the SPI core
> on the same SPI interface.

Then I misinterpreted your suggestion. But removing the dead code
remains the easiest way out, of course. (Note that the code has only
been dead since v3.8, ie only a year now.)

> > And that is probably also true for for CONFIG_ADT7410 and
> > CONFIG_ADT7410_MODULE. See https://lkml.org/lkml/2013/5/13/497 (and my
> > follow up to that message).
> 
> Both Jean and myself sent Reviewed-by/Acked-by feedback.
> Not being the maintainers, that is pretty much all we can do.
>  From there it is really up to the maintainer to accept
> or reject the patches.

Jean and you are included in (some of) the threads regarding a few
blackfin patches I sent last year. I forgot why you two are. Anyhow,
those patches were (mostly) ignored by the people working on blackfin.
The maintainer appears to be more responsive now. So I figured it might
be worthwhile to send reminders. Maybe I have more luck this time.


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/