From: "George G. Davis" <george_davis@mentor.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Chris Brandt <chris.brandt@renesas.com>,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Andy Lowe <andy_lowe@mentor.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
<devicetree@vger.kernel.org>, Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] serial: sh-sci: disable DMA for uart_console
Date: Tue, 14 May 2019 12:16:04 -0400 [thread overview]
Message-ID: <20190514161604.GD18528@mam-gdavis-lt> (raw)
In-Reply-To: <20190514155450.GB6508@kunai>
Hello Wolfram,
On Tue, May 14, 2019 at 05:54:51PM +0200, Wolfram Sang wrote:
>
> > > > Fixes: https://patchwork.kernel.org/patch/10929511/
> > >
> > > I don't think this is an appropriate reference, as it points to a patch that
> > > was never applied.
> >
> > I included it as a link to an upstream problem report similar to other commits
> > that I previewed. The link provides the extra context that I was perhaps to
> > lazy to note in the commit header.
>
> We have a "Link:" tag for things like this, e.g.:
>
> Link: https://patchwork.kernel.org/patch/10929511/
Right, I've changed it to a Link instead.
Thanks!
--
Regards,
George
prev parent reply other threads:[~2019-05-14 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 15:47 [PATCH v2] serial: sh-sci: disable DMA for uart_console George G. Davis
2019-05-14 8:28 ` Geert Uytterhoeven
2019-05-14 15:30 ` George G. Davis
2019-05-14 15:54 ` Wolfram Sang
2019-05-14 16:16 ` George G. Davis [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=20190514161604.GD18528@mam-gdavis-lt \
--to=george_davis@mentor.com \
--cc=andy_lowe@mentor.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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).