linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Daniel Kiss <daniel.kiss@arm.com>,
	Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] Documentation: fix malformed table in filesystems/proc.rst
Date: Mon, 15 Jun 2020 15:54:37 +0200	[thread overview]
Message-ID: <20200615155437.619facac@coco.lan> (raw)
In-Reply-To: <20200615072217.0e59ea63@lwn.net>

Em Mon, 15 Jun 2020 07:22:17 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Sun, 14 Jun 2020 23:54:26 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
> 
> > On 6/14/20 11:53 PM, Mauro Carvalho Chehab wrote:  
> > > Em Sun, 14 Jun 2020 20:33:22 -0700
> > > Randy Dunlap <rdunlap@infradead.org> escreveu:
> > >     
> > >> From: Randy Dunlap <rdunlap@infradead.org>
> > >>
> > >> Fix malformed table in "proc.rst" by dropping a needless hyphen ('-').
> > >>
> > >> Documentation/filesystems/proc.rst:548: WARNING: Malformed table.
> > >> Text in column margin in table line 29.
> > >>
> > >> Fixes: 424037b77519 ("mm: smaps: Report arm64 guarded pages in smaps")
> > >> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > >> Cc: Daniel Kiss <daniel.kiss@arm.com>
> > >> Cc: Mark Brown <broonie@kernel.org>
> > >> Cc: Catalin Marinas <catalin.marinas@arm.com>    
> > > 
> > > I submitted an identical patch on Jan, 3.     
> > 
> > OK. Well, that's disappointing IMHO.  
> 
> Sorry if I have caused disappointment.
> 
> In any case, that's *June*, not January,

Sorry for the typo! Yeah, I meant *June*. 

> In any case, that's *June*, not January, that the patch was submitted.  I
> didn't apply it because, since the problem didn't come through docs-next,
> it didn't apply there.  Now that docs-next is caught up with 5.8-rc1 I can
> apply such things again...

Yeah, those malformed table are very likely due to merge conflicts on 
patches for v5.8.

Thanks,
Mauro

  reply	other threads:[~2020-06-15 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  3:33 [PATCH] Documentation: fix malformed table in filesystems/proc.rst Randy Dunlap
2020-06-15  6:53 ` Mauro Carvalho Chehab
2020-06-15  6:54   ` Randy Dunlap
2020-06-15 13:22     ` Jonathan Corbet
2020-06-15 13:54       ` Mauro Carvalho Chehab [this message]
2020-06-15 14:53       ` Randy Dunlap

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=20200615155437.619facac@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=daniel.kiss@arm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@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).