From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Steven King <sfking@fdwdc.com>
Cc: linux-m68k@vger.kernel.org, Angelo Dureghello <angelo@sysam.it>,
Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68knommu: remove dead code
Date: Sun, 27 Aug 2017 23:11:49 +0200 [thread overview]
Message-ID: <20170827211149.6evcbhfhrenotb3c@piout.net> (raw)
In-Reply-To: <201708271236.31222.sfking@fdwdc.com>
On 27/08/2017 at 12:36:31 -0700, Steven King wrote:
> On Sunday 27 August 2017 12:09:59 pm Alexandre Belloni wrote:
> > On 27/08/2017 at 13:22:09 +0200, Angelo Dureghello wrote:
> > > Hi,
> > >
> > > just to inform you that i have in mind to add spi(soon, at least seems
> > > just a matter con Kconfig changes) and usdhc(later)
> > > drivers/support for stmark2 mcf5441x based board.
> > > But no problem, in case i'll re-add the this code as needed.
> >
> > I think it is easy enough to reintroduce init_BSP with your patch. It is
> > unfortunate that this useless function stayed that way so long, waiting
> > for a real user :)
>
> I believe I was the original author, I dont remember why the code wasn't
> merged. I still have the branch, if some wants to take it over and see it
> gets merged I wouldn't have any objections ;-)
There were comments from Geert that were not addressed:
http://patchwork.ozlabs.org/patch/165328/
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-08-27 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 14:34 [PATCH] m68knommu: remove dead code Alexandre Belloni
2017-08-25 1:24 ` Greg Ungerer
2017-08-27 11:22 ` Angelo Dureghello
2017-08-27 19:09 ` Alexandre Belloni
2017-08-27 19:36 ` Steven King
2017-08-27 21:11 ` Alexandre Belloni [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=20170827211149.6evcbhfhrenotb3c@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=angelo@sysam.it \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking@fdwdc.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