devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Dave Kleikamp <shaggy@kernel.org>,
	alsa-devel@alsa-project.org,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Evgeniy Polyakov <zbr@ioremap.net>,
	linux-cifs@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Chen-Yu Tsai <wens@csie.org>,
	devicetree@vger.kernel.org, Evgeniy Dushistov <dushistov@mail.ru>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	samba-technical@lists.samba.org,
	Liam Girdwood <lgirdwood@gmail.com>linux
Subject: Re: [PATCH 0/6] ReST conversion patches not applied yet
Date: Wed, 31 Jul 2019 17:26:13 -0300	[thread overview]
Message-ID: <20190731172613.32d65ad8@coco.lan> (raw)
In-Reply-To: <20190731202007.GI4369@sirena.org.uk>

Em Wed, 31 Jul 2019 21:20:07 +0100
Mark Brown <broonie@kernel.org> escreveu:

> On Wed, Jul 31, 2019 at 02:17:34PM -0600, Jonathan Corbet wrote:
> > Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:  
> 
> > > As promised, this is the rebased version of the patches that were not applied
> > > from the /26 patch series because you had merge conflicts.
> > > 
> > > They're all based on your docs-next branch, so should apply fine.
> > > 
> > > The first one fixes all but one error with a broken reference.
> > > 
> > > The only broken reference right now is due to a DT patch with was not
> > > accepted (no idea why), but whose driver is upstream.  
> 
> > All but 5/6 applied, thanks.  
> 
> Oh, I still hadn't reviewed this version of the SPI stuff :(

It is basically the one sent on that /26 patch series, just rebased
on the top of docs-next.

> There were outstanding questions about where it was going to get moved
> to but if I read the diff correctly it looks like it didn't actually get
> moved in the end?

Yeah, it doesn't have the move. My understanding from our discussions
is that we didn't reach a conclusion.

In any case, I can send a separate patch with the move part once
we reach an agreement about what's the best way to proceed (or you
can do it directly, if you prefer so).

Thanks,
Mauro

  reply	other threads:[~2019-07-31 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 20:08 [PATCH 0/6] ReST conversion patches not applied yet Mauro Carvalho Chehab
2019-07-31 20:08 ` [PATCH 1/6] docs: fix a couple of new broken references Mauro Carvalho Chehab
2019-07-31 20:21   ` Rob Herring
2019-07-31 20:36   ` Dave Kleikamp
2019-07-31 20:08 ` [PATCH 2/6] docs: writing-schema.md: convert from markdown to ReST Mauro Carvalho Chehab
2019-07-31 20:45   ` Rob Herring
2019-07-31 20:48     ` Jonathan Corbet
2019-07-31 21:30       ` Rob Herring
2019-07-31 20:17 ` [PATCH 0/6] ReST conversion patches not applied yet Jonathan Corbet
2019-07-31 20:20   ` Mark Brown
2019-07-31 20:26     ` Mauro Carvalho Chehab [this message]
2019-07-31 20:37       ` Mark Brown
2019-07-31 21:27         ` Mauro Carvalho Chehab
2019-07-31 21:55           ` Mark Brown

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=20190731172613.32d65ad8@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dushistov@mail.ru \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=mchehab@infradead.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=shaggy@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=wens@csie.org \
    --cc=zbr@ioremap.net \
    /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).