From: Vinod Koul <vinod.koul@intel.com>
To: Geliang Tang <geliangtang@163.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Jiri Kosina <trivial@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/9] dma: fix a trivial typo
Date: Sun, 25 Oct 2015 04:17:46 +0530 [thread overview]
Message-ID: <20151024224746.GK27370@localhost> (raw)
In-Reply-To: <918fdb002ec3b2a9fc5a5d364c0fbaff2f77c5cc.1445181079.git.geliangtang@163.com>
On Sun, Oct 18, 2015 at 11:31:10PM +0800, Geliang Tang wrote:
> s/regsiter/register/
>
Applied, now
Please ensure the patches have right subsystem names. You can use git log on
that file/subsystem to find the convention used
I have fixed it up before applying
--
~Vinod
next prev parent reply other threads:[~2015-10-24 22:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 15:29 [PATCH 1/9] drm: fix trivial typos Geliang Tang
2015-10-18 15:31 ` [PATCH 2/9] scsi: " Geliang Tang
2015-10-18 15:31 ` [PATCH 3/9] net: " Geliang Tang
2015-10-18 15:31 ` [PATCH 4/9] dma: fix a trivial typo Geliang Tang
2015-10-18 15:31 ` [PATCH 5/9] staging: wilc1000: fix trivial typos Geliang Tang
2015-10-18 15:31 ` [PATCH 6/9] clk: keystone: fix a trivial typo Geliang Tang
2015-10-18 15:31 ` [PATCH 7/9] input: keyboard: " Geliang Tang
2015-10-18 15:31 ` [PATCH 8/9] parport: " Geliang Tang
2015-10-18 15:31 ` [PATCH 9/9] usb: gadget: " Geliang Tang
2015-10-27 10:46 ` [PATCH 8/9] parport: " Sudip Mukherjee
2015-10-20 16:41 ` [PATCH 7/9] input: keyboard: " Dmitry Torokhov
2015-10-19 21:48 ` [PATCH 6/9] clk: keystone: " Stephen Boyd
2015-10-23 23:27 ` [PATCH 4/9] dma: " Linus Walleij
2015-10-24 22:47 ` Vinod Koul [this message]
2015-10-19 15:45 ` [PATCH 1/9] drm: fix trivial typos Alex Deucher
2015-10-19 15:45 ` Alex Deucher
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=20151024224746.GK27370@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geliangtang@163.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.