On Thu, 02 Jun 2016, Daniel Vetter wrote:
> On Thu, Jun 2, 2016 at 11:39 AM, Daniel Vetter wrote:
>> On Thu, Jun 2, 2016 at 9:16 AM, Jani Nikula
>> wrote:
>>> On Thu, 02 Jun 2016, Daniel Vetter wrote:
Further up in the state machinery we switch from STATE_NAME to
STATE_DOCBLOCK when
On Thu, Jun 2, 2016 at 11:39 AM, Daniel Vetter wrote:
> On Thu, Jun 2, 2016 at 9:16 AM, Jani Nikula
> wrote:
>> On Thu, 02 Jun 2016, Daniel Vetter wrote:
>>> Further up in the state machinery we switch from STATE_NAME to
>>> STATE_DOCBLOCK when we match /$doc_block/. Which means this
>>> block
On Thu, Jun 2, 2016 at 9:16 AM, Jani Nikula wrote:
> On Thu, 02 Jun 2016, Daniel Vetter wrote:
>> Further up in the state machinery we switch from STATE_NAME to
>> STATE_DOCBLOCK when we match /$doc_block/. Which means this
>> block of code here is entirely unreachable.
>>
>> Nuke it.
>
> kernel-
On Thu, 02 Jun 2016, Daniel Vetter wrote:
> Further up in the state machinery we switch from STATE_NAME to
> STATE_DOCBLOCK when we match /$doc_block/. Which means this
> block of code here is entirely unreachable.
>
> Nuke it.
kernel-doc currently supports multiple DOC: lines in a single kernel-
Further up in the state machinery we switch from STATE_NAME to
STATE_DOCBLOCK when we match /$doc_block/. Which means this
block of code here is entirely unreachable.
Nuke it.
Cc: Jani Nikula
Cc: linux-doc@vger.kernel.org
Cc: Jonathan Corbet
Signed-off-by: Daniel Vetter
---
scripts/kernel-doc
