linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: "Dmitry V. Krivenok" <krivenok.dmitry@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Nicolas Ferre <nicolas.ferre@atmel.com>,
	Wolfram Sang <wsa@the-dreams.de>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Grant Likely <grant.likely@linaro.org>,
	Bjorn Helgaas <bhelgaas@google.com>, Ray Jui <rjui@broadcom.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 1/5] dma: do not use 0x in front of %pad
Date: Sat, 5 Dec 2015 16:24:19 +0530	[thread overview]
Message-ID: <20151205105418.GD1854@localhost> (raw)
In-Reply-To: <1448916349-13564-2-git-send-email-krivenok.dmitry@gmail.com>

On Mon, Nov 30, 2015 at 11:45:45PM +0300, Dmitry V. Krivenok wrote:

Applied, after fixing susystem name

-- 
~Vinod

  parent reply	other threads:[~2015-12-05 10:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 20:45 [PATCH 0/5] Do not use 0x in front of %pa[pd] Dmitry V. Krivenok
2015-11-30 20:45 ` [PATCH 1/5] dma: do not use 0x in front of %pad Dmitry V. Krivenok
2015-12-01  9:01   ` Nicolas Ferre
2015-12-08 14:48     ` Thierry Reding
2015-12-08 16:46       ` Vinod Koul
2015-12-05 10:54   ` Vinod Koul [this message]
2015-11-30 20:45 ` [PATCH 2/5] i2c: do not use 0x in front of %pa Dmitry V. Krivenok
2015-12-01  1:02   ` Wolfram Sang
2015-11-30 20:45 ` [PATCH 3/5] nd: " Dmitry V. Krivenok
2015-11-30 20:50   ` Dan Williams
2015-11-30 20:45 ` [PATCH 4/5] of: " Dmitry V. Krivenok
2015-12-08 17:31   ` Rob Herring
2015-11-30 20:45 ` [PATCH 5/5] pci: do not use 0x in front of %pap Dmitry V. Krivenok
2015-11-30 20:50   ` Ray Jui
2015-12-01  1:49   ` Bjorn Helgaas

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=20151205105418.GD1854@localhost \
    --to=vinod.koul@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=frowand.list@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=krivenok.dmitry@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=ross.zwisler@linux.intel.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).