From: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oskar Schirmer <oskar-fYPSZ7JpQqsAvxtiuMwx3w@public.gmane.org>
Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org"
<linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org>,
Chris Zankel <chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org>
Subject: Re: i2c: removal of s6000 driver
Date: Fri, 23 May 2014 17:57:13 +0400 [thread overview]
Message-ID: <CAMo8Bf+ApZUWB27zkCTBy7MLVaf3r4GiMFhFftocmJOScVSQww@mail.gmail.com> (raw)
In-Reply-To: <20140523131722.GA28143@curry>
On Fri, May 23, 2014 at 5:17 PM, Oskar Schirmer <oskar-fYPSZ7JpQqsAvxtiuMwx3w@public.gmane.org> wrote:
> Removing drivers without a replacement tested and running
> doesn't make much sense, except one chooses to drop support
> for the whole S6 thing right away. Which I don't support.
Oscar, do you mean that you don't support the platform or that
you don't support its removal?
I'm pretty sure it's broken now, since there's no hardware to test on
and even no compiler for it (IIRC a recent attempt to get a toolchain
overlay for s6000 failed, see
http://lists.linux-xtensa.org/pipermail/linux-xtensa/Week-of-Mon-20130617/001099.html
).
--
Thanks.
-- Max
next prev parent reply other threads:[~2014-05-23 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 11:30 i2c: removal of s6000 driver Wolfram Sang
2014-05-23 13:17 ` Oskar Schirmer
2014-05-23 13:57 ` Max Filippov [this message]
2014-05-23 17:33 ` czankel
[not found] ` <537F8652.1090807-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org>
2014-05-24 15:47 ` Oskar Schirmer
2014-05-27 22:35 ` Daniel Glöckner
[not found] ` <20140527223557.GA9594-G/SgeDpXzeDLoDKTGw+V6w@public.gmane.org>
2014-06-09 22:06 ` Wolfram Sang
2014-06-11 8:51 ` Daniel Glöckner
2014-07-28 14:43 ` Daniel Glöckner
[not found] ` <20140728144330.GA31207-QdrG9jWwCLEAvxtiuMwx3w@public.gmane.org>
2014-08-09 14:07 ` Wolfram Sang
2014-05-24 10:21 ` Wolfram Sang
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=CAMo8Bf+ApZUWB27zkCTBy7MLVaf3r4GiMFhFftocmJOScVSQww@mail.gmail.com \
--to=jcmvbkbc-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org \
--cc=oskar-fYPSZ7JpQqsAvxtiuMwx3w@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).