All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Daniel Kiss <daniel.kiss@arm.com>,
	Yang Shi <yang.shi@linux.alibaba.com>,
	Mark Brown <broonie@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net,
	Luigi Semenzato <semenzato@chromium.org>,
	Aubrey Li <aubrey.li@linux.intel.com>,
	Kees Cook <keescook@chromium.org>, Chao Yu <chao@kernel.org>,
	NeilBrown <neilb@suse.de>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] a couple documentation fixes
Date: Mon, 8 Jun 2020 09:20:27 -0600	[thread overview]
Message-ID: <20200608092027.46363063@lwn.net> (raw)
In-Reply-To: <cover.1591137229.git.mchehab+huawei@kernel.org>

On Wed,  3 Jun 2020 00:38:12 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> It follows a couple of fixes for two tables that got broken, probably due to
> some conflict between the ReST conversion patches and ungoing updates.
> 
> IMO, it would be nice to have those two applied during the merge window,
> as they produce a too noisy output.

The problems all came from trees other than docs-next, so the patch
doesn't apply there now.  I'll merge with mainline after -rc1 and, if the
problems haven't been fixed elsewhere, I'll apply the patches then.

Thanks,

jon

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Yang Shi <yang.shi@linux.alibaba.com>,
	Kees Cook <keescook@chromium.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	NeilBrown <neilb@suse.de>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Aubrey Li <aubrey.li@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Luigi Semenzato <semenzato@chromium.org>,
	Mark Brown <broonie@kernel.org>,
	linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-f2fs-devel@lists.sourceforge.net,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Kiss <daniel.kiss@arm.com>
Subject: Re: [f2fs-dev] [PATCH 0/2] a couple documentation fixes
Date: Mon, 8 Jun 2020 09:20:27 -0600	[thread overview]
Message-ID: <20200608092027.46363063@lwn.net> (raw)
In-Reply-To: <cover.1591137229.git.mchehab+huawei@kernel.org>

On Wed,  3 Jun 2020 00:38:12 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> It follows a couple of fixes for two tables that got broken, probably due to
> some conflict between the ReST conversion patches and ungoing updates.
> 
> IMO, it would be nice to have those two applied during the merge window,
> as they produce a too noisy output.

The problems all came from trees other than docs-next, so the patch
doesn't apply there now.  I'll merge with mainline after -rc1 and, if the
problems haven't been fixed elsewhere, I'll apply the patches then.

Thanks,

jon


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2020-06-08 15:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 22:38 [PATCH 0/2] a couple documentation fixes Mauro Carvalho Chehab
2020-06-02 22:38 ` [f2fs-dev] " Mauro Carvalho Chehab
2020-06-02 22:38 ` [PATCH 1/2] fs: docs: f2fs.rst: fix a broken table Mauro Carvalho Chehab
2020-06-02 22:38   ` [f2fs-dev] " Mauro Carvalho Chehab
2020-06-08  1:41   ` Chao Yu
2020-06-08  1:41     ` Chao Yu
2020-06-02 22:38 ` [PATCH 2/2] docs: fs: proc.rst: fix a warning due to a merge conflict Mauro Carvalho Chehab
2020-06-03  9:54   ` Mark Brown
2020-06-03 19:12   ` Kees Cook
2020-06-19 19:58   ` Jonathan Corbet
2020-06-08 15:20 ` Jonathan Corbet [this message]
2020-06-08 15:20   ` [f2fs-dev] [PATCH 0/2] a couple documentation fixes Jonathan Corbet

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=20200608092027.46363063@lwn.net \
    --to=corbet@lwn.net \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aubrey.li@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=chao@kernel.org \
    --cc=daniel.kiss@arm.com \
    --cc=jaegeuk@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=neilb@suse.de \
    --cc=semenzato@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=yang.shi@linux.alibaba.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.