linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "S. Fricke" <silvio.fricke@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Ming Lei <ming.lei@canonical.com>,
	"Luis R . Rodriguez" <mcgrof@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v3 2/4] Documentation/atomic_ops.txt: convert to ReST markup
Date: Sun, 27 Nov 2016 15:53:34 +0100	[thread overview]
Message-ID: <20161127145334.GH14150@sfserver> (raw)
In-Reply-To: <20161125215814.GA3061@worktop.programming.kicks-ass.net>

Hi Peter,

> On Fri, Nov 25, 2016 at 03:59:45PM +0100, Silvio Fricke wrote:
> > ... and move to core-api folder.
> > 
> > Signed-off-by: Silvio Fricke <silvio.fricke@gmail.com>
> > ---
> >  Documentation/atomic_ops.txt => Documentation/core-api/atomic_ops.rst | 777 +++++++++++++++++++++++++++++++++++++-----------------------------------
> >  Documentation/core-api/index.rst                                      |   1 +-
> >  Documentation/process/volatile-considered-harmful.rst                 |   3 +-
> >  3 files changed, 404 insertions(+), 377 deletions(-)
> 
> Not a fan of this. The atomic_ops.txt file needs a lot of love, and I
> wouldn't want to edit a .rst file.

What is the problem with this rst-file? atomic_ops.rst are not so different to
the txt variant.


I will drop this patch.

Best regards,
Silvio


-- 
-- S. Fricke ---------------------------------------- silvio@port1024.net --
   Diplom-Informatiker (FH)
   Linux-Development                         Matrix: @silvio:port1024.net   
----------------------------------------------------------------------------

  reply	other threads:[~2016-11-27 14:53 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 12:42 [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-24 12:42 ` [PATCH 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-24 12:42 ` [PATCH 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-24 12:42 ` [PATCH 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-24 19:46 ` [PATCH 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Mauro Carvalho Chehab
2016-11-25 10:02 ` [PATCH v2 " Silvio Fricke
2016-11-25 10:02   ` [PATCH v2 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 13:03     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 13:25     ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 13:47       ` S. Fricke
2016-11-25 13:58         ` Mauro Carvalho Chehab
2016-11-25 10:02   ` [PATCH v2 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 13:34     ` Mauro Carvalho Chehab
2016-11-25 14:59   ` [PATCH v3 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-25 14:59     ` [PATCH v3 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-25 20:53       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 2/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-25 21:01       ` Mauro Carvalho Chehab
2016-11-25 21:58       ` Peter Zijlstra
2016-11-27 14:53         ` S. Fricke [this message]
2016-11-27 18:36           ` Jani Nikula
2016-11-27 23:59         ` Jonathan Corbet
2016-11-28  7:26           ` Peter Zijlstra
2016-11-28  8:44             ` Daniel Vetter
2016-11-28 10:20               ` Peter Zijlstra
2016-11-28 11:08                 ` Mauro Carvalho Chehab
2016-11-28 11:54                   ` Peter Zijlstra
2016-11-28 13:46                     ` Daniel Vetter
2016-11-28 15:14                       ` Mauro Carvalho Chehab
2016-11-28 11:16                 ` Jani Nikula
2016-11-28 11:56                   ` Peter Zijlstra
2016-11-28 12:32                     ` Jani Nikula
2016-11-28 14:13                 ` Daniel Vetter
2016-11-28 14:29                   ` Jonathan Corbet
2016-11-25 14:59     ` [PATCH v3 3/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-25 21:10       ` Mauro Carvalho Chehab
2016-11-25 14:59     ` [PATCH v3 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-11-25 20:50       ` Mauro Carvalho Chehab
2016-12-01 16:11         ` Luis R. Rodriguez
2016-12-01 16:45           ` Greg Kroah-Hartman
2016-11-28 17:30     ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 1/4] Documentation/assoc_array.txt: convert to ReST markup Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 2/4] Documentation/local_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 3/4] Documentation/atomic_ops.txt: " Silvio Fricke
2016-11-28 17:30       ` [PATCH v4 4/4] firmware: remove warning at documentation generation time Silvio Fricke
2016-12-01  0:51       ` [PATCH v4 0/4] core-api ReST: assoc_array, atomic_ops, local_ops Jonathan Corbet
2016-12-01 15:49         ` Luis R. Rodriguez

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=20161127145334.GH14150@sfserver \
    --to=silvio.fricke@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=peterz@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).