From: Jonathan Corbet <corbet@lwn.net>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Jiri Kosina <trivial@kernel.org>,
linux-doc@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] DMA-API: Spelling s/This/Think/
Date: Fri, 22 May 2015 07:16:48 -0600 [thread overview]
Message-ID: <20150522071648.6f18c82c@lwn.net> (raw)
In-Reply-To: <20150522122953.GX3140@localhost>
On Fri, 22 May 2015 17:59:53 +0530
Vinod Koul <vinod.koul@intel.com> wrote:
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Looks good to me, but the question si which tree does this go thru..
I'll take it through the docs tree.
Thanks,
jon
prev parent reply other threads:[~2015-05-22 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 11:57 [PATCH trivial] DMA-API: Spelling s/This/Think/ Geert Uytterhoeven
2015-05-22 12:29 ` Vinod Koul
2015-05-22 12:55 ` Geert Uytterhoeven
2015-05-22 13:16 ` 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=20150522071648.6f18c82c@lwn.net \
--to=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=vinod.koul@intel.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