From: Felipe Balbi <balbi@ti.com>
To: "Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Cc: balbi@ti.com, Belisko Marek <marek.belisko@gmail.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
linux-serial@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: DTR gpio handling removed by 985bfd54c826c0ba873ca0adfd5589263e0c6ee2
Date: Fri, 15 Aug 2014 08:24:44 -0500 [thread overview]
Message-ID: <20140815132444.GA11781@saruman.home> (raw)
In-Reply-To: <B18DC75F-EA0E-456F-996E-2F4BF496B68B@goldelico.com>
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
Hi,
On Fri, Aug 15, 2014 at 08:08:44AM +0200, Dr. H. Nikolaus Schaller wrote:
> Hi Felipe,
>
> Am 15.08.2014 um 00:58 schrieb Felipe Balbi <balbi@ti.com>:
>
> > Hi,
> >
> > On Thu, Aug 14, 2014 at 11:04:58PM +0200, Belisko Marek wrote:
> >> during 3.15 release was removed by commit
> >> 985bfd54c826c0ba873ca0adfd5589263e0c6ee2 code which was added by
> >> 9574f36fb801035f6ab0fbb1b53ce2c12c17d100 by Neil Brown. We're using
> >> DTR gpio in gta04 device. I plan to post DT binding for DTR gpio +
> >> documentation and find out that Neil's code was removed by Felipe.
> >> Greg can you please revert mentioned commit? We're using DTR gpio in
> >> gta04 device. Or is there other way how to proceed? Thanks.
> >
> > there are *NO* users of that in tree, if you're using it, then please
> > add a proper DTS for your device and figure out a way of passing DTR
> > gpio through DT.
>
> In fact we are in the middle of preparing DT and driver patches for
> upstreaming the out of tree drivers Neil is mentioning. So there are
> no users *yet* and maybe we are the first one.
right, and that's why it was removed. How would we even know that the
code works when there are no users for it ?
> Neil has already completely argued and commented on that topic:
>
> https://lkml.org/lkml/2014/4/23/736
>
> Unfortunately he acked the removal with a completely non-technical
> argument:
>
> > Just at the moment I'm finding it hard to care.
> > So
> > Acked-by: NeilBrown <neilb@suse.de>
>
> Now we have the problem that it got kicked out while we were preparing
> the other parts :(
>
> On the other hand, please consider that we don’t have the manpower and
> knowledge to modify bigger parts of Linux besides plumbing together
> parts that already exist and add drivers and DT nodes.
>
> So please consider again to re-add
> 9574f36fb801035f6ab0fbb1b53ce2c12c17d100.
>
> Or should we resubmit it together with our DT/drivers where we use it?
submit it together with your patches but it would be a lot better to see
that turned into something generic, which was commented on the same
thread IIRC.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-15 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAfyv36aMkE5e6Bo1hy1md+Z5EjrZjP+foZTyncp5GFtnaL_sg@mail.gmail.com>
2014-08-14 22:58 ` DTR gpio handling removed by 985bfd54c826c0ba873ca0adfd5589263e0c6ee2 Felipe Balbi
2014-08-15 6:08 ` Dr. H. Nikolaus Schaller
2014-08-15 13:24 ` Felipe Balbi [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=20140815132444.GA11781@saruman.home \
--to=balbi@ti.com \
--cc=hns@goldelico.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=neilb@suse.de \
/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).