From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [PATCH V2 1/3] dma: add Qualcomm Technologies HIDMA management driver Date: Thu, 5 Nov 2015 08:43:00 -0600 Message-ID: <563B6AF4.1010806@codeaurora.org> References: <1446444460-21600-1-git-send-email-okaya@codeaurora.org> <1446444460-21600-2-git-send-email-okaya@codeaurora.org> <56378D38.9050509@codeaurora.org> <56379CD6.5020807@codeaurora.org> <5637A1EB.9080002@codeaurora.org> <5637ABD1.5060707@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Sinan Kaya , dmaengine@vger.kernel.org, Christopher Covington , "jcm@redhat.com" , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Vinod Koul , Dan Williams , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" List-Id: devicetree@vger.kernel.org Rob Herring wrote: > I'm saying document it as "qcom,-hidma-mgmt" and when you have > the part number update the binding. Meanwhile push on the powers that > be to decide on a part number. Got it. But we should we do about this: static const struct of_device_id qcom_hidma_mgmt_match[] = { { .compatible = "qcom,hidma-mgmt-1.0", }, {}, }; -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.