linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v4 00/26] Fix some doc build warnings/errors and broken links
Date: Fri, 15 Jun 2018 17:52:03 -0300	[thread overview]
Message-ID: <20180615175203.19bc4abc@coco.lan> (raw)
In-Reply-To: <20180615130951.303a3ebb@lwn.net>

Em Fri, 15 Jun 2018 13:09:51 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Fri, 15 Jun 2018 13:30:28 -0300
> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> 
> > As discussed during the review of v2, your plans were to merge
> > things with potential to conflict with merges by the end of the
> > merge window. So, I'm resubmitting it in order to help you with
> > that.  
> 
> Is there any chance you could send them directly Linusward with my ack?
> I'm fighting a few real-world complications at the moment, and barely
> have time to breathe...

Ok, I'll send him a pull request (likely tomorrow), adding your
ack on the patches at this series.

Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2018-06-15 20:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 16:30 [PATCH v4 00/26] Fix some doc build warnings/errors and broken links Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 01/26] docs: can.rst: fix a footnote reference Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 02/26] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 03/26] arch/*: Kconfig: fix documentation for NMI watchdog Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 04/26] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-06-15 18:22   ` James Morris
2018-06-20 15:26   ` Rob Herring
2018-06-15 16:30 ` [PATCH v4 05/26] docs: Fix some broken references Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 06/26] media: dvb: fix location of get_dvb_firmware script Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 07/26] media: dvb: point to the location of the old README.dvb-usb file Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 08/26] media: v4l: fix broken video4linux docs locations Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 09/26] media: max2175: fix location of driver's companion documentation Mauro Carvalho Chehab
2018-06-15 16:34   ` Ramesh Shanmugasundaram
2018-06-15 16:30 ` [PATCH v4 10/26] scripts/documentation-file-ref-check: fix help message Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 11/26] scripts/documentation-file-ref-check: accept more wildcards at filenames Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 12/26] scripts/documentation-file-ref-check: add a fix logic for DT Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 13/26] scripts/documentation-file-ref-check: hint: dash or underline Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 14/26] scripts/documentation-file-ref-check: get rid of false-positives Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 15/26] scripts/documentation-file-ref-check: check tools/*/Documentation Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 16/26] docs: Fix more broken references Mauro Carvalho Chehab
2018-06-15 16:41   ` Miguel Ojeda
2018-06-15 16:30 ` [PATCH v4 17/26] bindings: nvmem/zii: Fix location of nvmem.txt Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 18/26] kernel-parameters.txt: fix pointers to sound parameters Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 19/26] MAINTAINERS: fix location of some display DT bindings Mauro Carvalho Chehab
2018-06-15 23:38   ` Eric Anholt
2018-06-15 16:30 ` [PATCH v4 20/26] MAINTAINERS: fix location of DT npcm files Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 21/26] devicetree: fix some bindings file names Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 22/26] devicetree: fix name of pinctrl-bindings.txt Mauro Carvalho Chehab
2018-06-18  5:48   ` Lee Jones
2018-06-15 16:30 ` [PATCH v4 23/26] devicetree: fix a series of wrong file references Mauro Carvalho Chehab
2018-06-18  5:49   ` Lee Jones
2018-06-28 13:53   ` Bjorn Helgaas
2018-08-07  7:04   ` Chen-Yu Tsai
2018-06-15 16:30 ` [PATCH v4 24/26] ABI: sysfs-devices-system-cpu: remove a broken reference Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 25/26] Documentation: rstFlatTable.py: fix " Mauro Carvalho Chehab
2018-06-15 16:30 ` [PATCH v4 26/26] fix a series of Documentation/ broken file name references Mauro Carvalho Chehab
2018-06-16 15:52   ` Rafael J. Wysocki
2018-06-19  4:14   ` Vinod
2018-06-15 19:09 ` [PATCH v4 00/26] Fix some doc build warnings/errors and broken links Jonathan Corbet
2018-06-15 20:52   ` Mauro Carvalho Chehab [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=20180615175203.19bc4abc@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@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).