All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>,
	linux-kernel@vger.kernel.org
Cc: Krishna Kurapati <quic_kriskura@quicinc.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: fix max_segment_size malformed table
Date: Wed, 10 Jan 2024 13:04:02 -0800	[thread overview]
Message-ID: <9e3f8028-c799-43f2-9eca-492fbf8b1dee@infradead.org> (raw)
In-Reply-To: <9b22d817-c0d9-4e85-cda7-7843907a70a1@gmail.com>



On 1/10/24 12:38, Sergei Shtylyov wrote:
> On 1/10/24 11:35 PM, Randy Dunlap wrote:
> 
>> Sphinx reports a malformed table due to the table begin/end line
>> segments being too short for the word "max_segment_size", so
>> extend them by one more '=' character to prevent to error.
> 
>    s/to error/the error/?

yes, thanks.

> 
>> Documentation/usb/gadget-testing.rst:459: ERROR: Malformed table.
>> Text in column margin in table line 9.
>>
>> Fixes: 1900daeefd3e ("usb: gadget: ncm: Add support to update wMaxSegmentSize via configfs")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Krishna Kurapati <quic_kriskura@quicinc.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: linux-usb@vger.kernel.org
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
> [...]
> 
> MBR, Sergey

-- 
#Randy

      reply	other threads:[~2024-01-10 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 20:35 [PATCH] usb: gadget: fix max_segment_size malformed table Randy Dunlap
2024-01-10 20:38 ` Sergei Shtylyov
2024-01-10 21:04   ` Randy Dunlap [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=9e3f8028-c799-43f2-9eca-492fbf8b1dee@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_kriskura@quicinc.com \
    --cc=sergei.shtylyov@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.