linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v2 12/22] docs: gpio: driver.rst: fix a bad tag
Date: Sat, 8 Jun 2019 06:42:08 -0300	[thread overview]
Message-ID: <20190608064208.12e0e145@coco.lan> (raw)
In-Reply-To: <CACRpkdayQdrtqO3aygY1uDG0LCX_9rVnSnxP5F_C-KMZURTAYA@mail.gmail.com>

Hi Linus,

Em Sat, 8 Jun 2019 00:08:10 +0200
Linus Walleij <linus.walleij@linaro.org> escreveu:

> On Tue, Jun 4, 2019 at 4:18 PM Mauro Carvalho Chehab
> <mchehab+samsung@kernel.org> wrote:
> 
> > With ReST, [foo]_ means a reference to foo, causing this warning:
> >
> >     Documentation/driver-api/gpio/driver.rst:419: WARNING: Unknown target name: "devm".
> >
> > Fix it by using a literal for the name.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>  
> 
> Looks identical to the v1 I already applied, so keeping
> that one.

Thanks for applying it.

Yeah, it should be identical (and so it should be the v3 I sent yesterday).

v2 and v3 are just rebases on the top of linux-next.

Thanks,
Mauro

  reply	other threads:[~2019-06-08  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1559656538.git.mchehab+samsung@kernel.org>
2019-06-04 14:17 ` [PATCH v2 12/22] docs: gpio: driver.rst: fix a bad tag Mauro Carvalho Chehab
2019-06-07 22:08   ` Linus Walleij
2019-06-08  9:42     ` Mauro Carvalho Chehab [this message]
2019-06-04 14:17 ` [PATCH v2 19/22] docs: fix broken documentation links 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=20190608064208.12e0e145@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=corbet@lwn.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).