From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pata_pcmcia: add EBSA110's PCMCIA slot support
Date: Fri, 17 Mar 2017 10:13:13 -0400 [thread overview]
Message-ID: <20170317141313.GC5078@htj.duckdns.org> (raw)
In-Reply-To: <11380780.Ccg1NEX8q5@amdc3058>
Hello,
On Fri, Mar 17, 2017 at 03:08:56PM +0100, Bartlomiej Zolnierkiewicz wrote:
> To be honest, the main point here is to make Russell happy. ;-)
>
> This is the second time he brought EBSA110 issue while talking about
> conversion of ARM platforms to use libata PATA so I've finally decided
> to do the patch just to have a reference example of how to deal with
> this and similar devices in a proper way.
>
> Even though the patch can't be tested EBSA110 is still a supported ARM
> platform and the patch should work fine in theory (+ it cannot break
> anything). OTOH it adds an extra code which has some cost from the
> long-term maintenance POV. Anyway, it is up to you to decide what to
> do with it. :-)
It's fairly low impact and I don't think it's gonna add noticeable
maintenance overhead at all, so that part is fine but it's super weird
to add code which we know not to have any users. It looks like we
can't even test it.
What's the end game here? Is it part of the effort to remove ide? If
so, I have no objection to that but think it isn't a pressing issue
either and the ultimate decision has to come from Dave.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-17 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170314175046epcas1p43f98daad14a2bac7f314e7d39e120232@epcas1p4.samsung.com>
2017-03-14 17:50 ` [PATCH] pata_pcmcia: add EBSA110's PCMCIA slot support Bartlomiej Zolnierkiewicz
2017-03-16 21:26 ` Tejun Heo
2017-03-17 11:59 ` Bartlomiej Zolnierkiewicz
2017-03-17 13:39 ` Tejun Heo
2017-03-17 14:08 ` Bartlomiej Zolnierkiewicz
2017-03-17 14:13 ` Tejun Heo [this message]
2017-03-17 15:51 ` Bartlomiej Zolnierkiewicz
2017-03-20 13:00 ` Bartlomiej Zolnierkiewicz
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=20170317141313.GC5078@htj.duckdns.org \
--to=tj@kernel.org \
--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).