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, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 00/22] Some documentation fixes
Date: Fri, 7 Jun 2019 15:44:30 -0300 [thread overview]
Message-ID: <20190607154430.4879976d@coco.lan> (raw)
In-Reply-To: <20190607115521.6bf39030@lwn.net>
Em Fri, 7 Jun 2019 11:55:21 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Tue, 4 Jun 2019 11:17:34 -0300
> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
>
> > Fix several warnings and broken links.
> >
> > This series was generated against linux-next, but was rebased to be applied at
> > docs-next. It should apply cleanly on either tree.
> >
> > There's a git tree with all of them applied on the top of docs/docs-next
> > at:
> >
> > https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v2
>
> So I'll admit I've kind of lost track of which of these are applied, which
> have comments, etc. When you feel things have settled, can you get me an
> updated set and I'll get them applied?
What I usually do here to check what was already applied (besides
looking e-mails) is to reset my tree against yours, then pull from
linux-next and pull from my old branch with those patches.
Then, I reset again to your tree, in order to make easier for you
to apply. It should be noticed that, due to this, you might actually
see a few more warnings on your tree, if a patch on this series
fix an issue that it is at linux next but didn't arrive your
tree.
Yet, all patches apply cleanly on your tree.
After doing that, there are 17 patches yet to be applied. Two new
patches are now needed too, due to vfs.txt -> vfs.rst and
pci.txt -> pci.rst renames.
The patches against your tree are at:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v3.3
For convenience, I'm sending them again as a new patch series
(with the two extra patches fixing the recent issues).
Thanks,
Mauro
next prev parent reply other threads:[~2019-06-07 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 14:17 [PATCH v2 00/22] Some documentation fixes Mauro Carvalho Chehab
2019-06-04 14:17 ` [PATCH v2 02/22] isdn: mISDN: remove a bogus reference to a non-existing doc Mauro Carvalho Chehab
2019-06-04 14:17 ` [PATCH v2 05/22] docs: bpf: get rid of two warnings Mauro Carvalho Chehab
2019-06-04 14:17 ` [PATCH v2 16/22] docs: net: dpio-driver.rst: fix two codeblock warnings Mauro Carvalho Chehab
2019-06-04 14:17 ` [PATCH v2 17/22] docs: net: sja1105.rst: fix table format Mauro Carvalho Chehab
2019-06-07 17:55 ` [PATCH v2 00/22] Some documentation fixes Jonathan Corbet
2019-06-07 18:44 ` Mauro Carvalho Chehab [this message]
2019-06-08 19:44 ` Jonathan Corbet
2019-06-09 2:31 ` Mauro Carvalho Chehab
2019-06-09 2:33 ` Mauro Carvalho Chehab
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=20190607154430.4879976d@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 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).