From: Li Yang <leoli@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: zw@zh-kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] rapidio: add common mapping APIs for RapidIO memory access
Date: Thu, 30 Apr 2009 13:10:53 +0800 [thread overview]
Message-ID: <2a27d3730904292210q67e18274nf6676a054b780639@mail.gmail.com> (raw)
In-Reply-To: <20090428.043929.171852977.davem@davemloft.net>
On Tue, Apr 28, 2009 at 7:39 PM, David Miller <davem@davemloft.net> wrote:
>
> Please number your patches. :-/
>
> There is no way for anyone to be able to tell in what order
> your changes should be applied.
Sorry for that. I thought I have added -n when doing the
git-format-patch, but it turns out not the case. :( Will double check
next time.
- Leo
next prev parent reply other threads:[~2009-04-30 5:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 10:16 [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes Li Yang
2009-04-28 10:15 ` [PATCH] rapidio: add common mapping APIs for RapidIO memory access Li Yang
2009-04-28 10:15 ` [PATCH] powerpc/fsl_rio: use LAW address from device tree Li Yang
2009-04-28 10:15 ` [PATCH] powerpc: add memory map support to Freescale RapioIO block Li Yang
2009-04-28 10:15 ` [PATCH] rionet: add memory access to simulated Ethernet over rapidio Li Yang
2009-04-28 10:15 ` [PATCH] rio: warn_unused_result warnings fix Li Yang
2009-04-28 10:51 ` Michael Ellerman
2009-04-28 11:08 ` Li Yang
2009-04-28 11:38 ` David Miller
2009-04-28 11:39 ` [PATCH] rapidio: add common mapping APIs for RapidIO memory access David Miller
2009-04-30 5:10 ` Li Yang [this message]
2009-04-30 11:45 ` Kumar Gala
2009-04-28 12:06 ` [PATCH 0/5] rapidio: adding memory mapping IO support and misc fixes Kumar Gala
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=2a27d3730904292210q67e18274nf6676a054b780639@mail.gmail.com \
--to=leoli@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=zw@zh-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).