From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: mach-shmobile: FIXME message in file pm-sh732.c
Date: Fri, 11 Jul 2014 17:44:43 +0200 [thread overview]
Message-ID: <20140711154443.GD1777@verge.net.au> (raw)
In-Reply-To: <CAPDOMVgi-GMQp101eZewVBOK_nFD8UJ04UydQ6bxa6Y5FP_VgQ@mail.gmail.com>
On Fri, Jul 11, 2014 at 11:24:12AM -0400, Nick Krause wrote:
> On Fri, Jul 11, 2014 at 5:34 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Jul 04, 2014 at 12:34:58AM -0400, Nick Krause wrote:
> >> While searching for FIX ME messages when using cscope on the latest kernels I
> >> get a message on 68 of this file and was wondering what I need to define SMFRAM
> >> as in order for it to point to things needed to support this portion
> >> of the hardware.
> >
> > Hi Nick,
> >
> > while I don't have a technical answer to your question I do believe
> > that the code in question will be removed in the not too distant future
> > along with support for the sh7372 SoC.
>
> Why are we removing support for this SoC? Is there any reason?
Because it is rather old hardware which is most likely not used against
mainline by anyone other than those maintaining the code and moving it over
to use multiplatform, CCF, and the like appears to be more work thank it is
worth.
next prev parent reply other threads:[~2014-07-11 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 4:34 mach-shmobile: FIXME message in file pm-sh732.c Nick Krause
2014-07-11 9:34 ` Simon Horman
2014-07-11 15:24 ` Nick Krause
2014-07-11 15:44 ` Simon Horman [this message]
2014-07-11 15:56 ` Nick Krause
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=20140711154443.GD1777@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).