public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Steven Miao <realmz6@gmail.com>,
	adi-buildroot-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin: bf537: rename "CONFIG_ADT7310" and friends
Date: Thu, 13 Feb 2014 18:03:04 +0100	[thread overview]
Message-ID: <1392310984.23598.15.camel@x220> (raw)
In-Reply-To: <52FCF2CD.9000008@roeck-us.net>

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


      reply	other threads:[~2014-02-13 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 11:43 [PATCH] Blackfin: bf537: rename "CONFIG_ADT7310" and friends Paul Bolle
2013-03-25 11:55 ` [uclinux-dist-devel] " Lars-Peter Clausen
2013-03-25 12:01   ` Paul Bolle
2013-03-25 15:22 ` Guenter Roeck
2013-03-25 15:45   ` Lars-Peter Clausen
2014-02-13  9:57     ` Paul Bolle
2014-02-13 10:31       ` Paul Bolle
2014-02-13 16:29         ` Guenter Roeck
2014-02-13 17:03           ` Paul Bolle [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=1392310984.23598.15.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=realmz6@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