From: holler@ahsoftware.de (Alexander Holler)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci fixes for v3.12-rc
Date: Fri, 20 Sep 2013 19:45:59 +0200 [thread overview]
Message-ID: <523C89D7.4090006@ahsoftware.de> (raw)
In-Reply-To: <CAOesGMi4z_wVVe6GfyWQ+7OApH0pHJe3ak90smJtf4nyJbu14A@mail.gmail.com>
Am 20.09.2013 19:40, schrieb Olof Johansson:
> Hi,
>
> On Thu, Sep 19, 2013 at 11:06 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>> Am 19.09.2013 19:48, schrieb Olof Johansson:
>>> Hi Sekhar,
>>>
>>> On Thu, Sep 19, 2013 at 3:22 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>>>> The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
>> ...
>>
>>>> 3) A patch to complete the DT support for EDMA. Without
>>>> this patch, the DT support for EDMA cannot be used.
>>>> There are no in-tree DT users of EDMA currently but
>>>> nevertheless the patch fixes a previously incomplete
>>>> implementation.
>>>
>>> Finishing incomplete work is not a fix, especially if the users aren't
>>> in-tree. The other patches are just fine to include though.
>>
>> It fixes problems for all people which are not using the provided DT's
>> but using edma in their own DT. So I don't understand your arguing as DT
>> got introduced to not only support in-tree configs. It clearly fixes
>> problems.
>
> Right, that was the smaller part of the argument. The bigger is:
> Completing a feature is not a fix. If the whole feature didn't make it
> in for a release, then the rest goes into the next release.
Bureaucrazy at it's best.
Regards,
Alexander Holler
prev parent reply other threads:[~2013-09-20 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 10:22 [GIT PULL] DaVinci fixes for v3.12-rc Sekhar Nori
2013-09-19 17:48 ` Olof Johansson
2013-09-20 4:54 ` Sekhar Nori
2013-09-20 6:06 ` Alexander Holler
2013-09-20 17:40 ` Olof Johansson
2013-09-20 17:45 ` Alexander Holler [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=523C89D7.4090006@ahsoftware.de \
--to=holler@ahsoftware.de \
--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).