[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ce27a85e-ce86-a16f-cd1d-eeb953e9575c@xilinx.com>
Date: Mon, 17 Dec 2018 13:28:42 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Mark Brown <broonie@...nel.org>,
Michal Simek <michal.simek@...inx.com>
CC: Maruthi Srinivas Bayyavarapu
<maruthi.srinivas.bayyavarapu@...inx.com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Vishal Sagar <vsagar@...inx.com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <alsa-devel@...a-project.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] ASoC: xlnx: Add i2s driver
On 17. 12. 18 13:24, Mark Brown wrote:
> On Fri, Dec 14, 2018 at 07:50:43AM +0100, Michal Simek wrote:
>> On 13. 12. 18 16:31, Mark Brown wrote:
>>> On Sat, Dec 08, 2018 at 12:02:37AM +0530, Maruthi Srinivas Bayyavarapu wrote:
>
>>>> @@ -0,0 +1,185 @@
>>>> +// SPDX-License-Identifier: GPL-2.0
>>>> +/*
>>>> + * Xilinx ASoC I2S audio support
>>>> + *
>
>>> This looks otherwise good so I've applied it but please send a followup
>>> patch converting the entire comment block to C++ style so this looks
>>> more consistent.
>
>> Is it the rule for your subsystems? Or did it come from any generic
>> agreement how this should be handled in .c files?
>
> It's mainly me, it's certainly not a consistent policy.
>
ok.
Maruthi: Please send that patch which Mark is asking about.
Thanks,
Michal
Powered by blists - more mailing lists