From: Steven King <sfking@fdwdc.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Bolle <pebolle@tiscali.nl>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x
Date: Tue, 20 May 2014 13:50:35 -0700 [thread overview]
Message-ID: <201405201350.35661.sfking@fdwdc.com> (raw)
In-Reply-To: <CAMuHMdVbRJOO1fvMDOeVH1j5HiDY=FMA35us0u7oP2jbYS=NAQ@mail.gmail.com>
On Tuesday 20 May 2014 1:19:26 pm Geert Uytterhoeven wrote:
> Hi Paul,
>
> On Tue, May 20, 2014 at 9:28 PM, Paul Bolle <pebolle@tiscali.nl> wrote:
> > In v3.6 both a check for CONFIG_I2C_COLDFIRE and two checks for
> > CONFIG_RTC_DRV_M5441x were added to the code for the coldfire platform
> > (in m525x.c and in m5441x.c respectively). Neither of these macros can
> > be matched to a Kconfig symbol.
> >
> > Is a series that adds these Kconfig symbols pending?
>
> For the former, Steven King (cc) submitted patches in 2010 and 2012.
> For the latter, he submitted patches in 2012.
>
> Seems like they were never integrated...
Indeed.
At this point, they're pretty much superfluous so if someone were to submit a patch removing them, they would not get any objections from me.
next prev parent reply other threads:[~2014-05-20 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 19:28 m68knommu: CONFIG_I2C_COLDFIRE and CONFIG_RTC_DRV_M5441x Paul Bolle
2014-05-20 20:19 ` Geert Uytterhoeven
2014-05-20 20:50 ` Steven King [this message]
2014-05-20 21:01 ` Paul Bolle
2014-05-20 21:16 ` Steven King
2014-05-21 15:46 ` Yannick GICQUEL
2014-05-21 15:55 ` Paul Bolle
2014-05-21 21:47 ` Steven King
2014-05-23 8:19 ` Yannick GICQUEL
2014-05-22 1:04 ` Greg Ungerer
2014-05-23 6:44 ` Yannick GICQUEL
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=201405201350.35661.sfking@fdwdc.com \
--to=sfking@fdwdc.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=pebolle@tiscali.nl \
/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