From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Hebb <tommyhebb@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
linux-doc@vger.kernel.org (open list:DOCUMENTATION)
Subject: Re: [PATCH] Documentation: arm: clean up Marvell Berlin family info
Date: Wed, 16 May 2018 13:12:11 -0600 [thread overview]
Message-ID: <20180516131211.01ebf987@lwn.net> (raw)
In-Reply-To: <20180514215511.17328-1-tommyhebb@gmail.com>
On Mon, 14 May 2018 17:55:10 -0400
Thomas Hebb <tommyhebb@gmail.com> wrote:
> Remove dead links, make spacing consistent, and note that the family was
> acquired by Synaptics in 2017.
>
> Signed-off-by: Thomas Hebb <tommyhebb@gmail.com>
Applied to the docs tree, thanks.
jon
--
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
prev parent reply other threads:[~2018-05-16 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 21:55 [PATCH] Documentation: arm: clean up Marvell Berlin family info Thomas Hebb
2018-05-16 19:12 ` Jonathan Corbet [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=20180516131211.01ebf987@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tommyhebb@gmail.com \
--cc=trivial@kernel.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).