From: Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <rds-devel@oss.oracle.com>,
<akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<amwang@redhat.com>
Subject: Re: [PATCH 54/62] rds: remove the second argument of k[un]map_atomic()
Date: Mon, 28 Nov 2011 07:28:28 -0800 (PST) [thread overview]
Message-ID: <fa4c1eb1-a564-4984-8648-f754c83672da@default> (raw)
From: Cong Wang <amwang@redhat.com>
Date: Sun, 27 Nov 2011 13:27:34 +0800
> Signed-off-by: Cong Wang <amwang@redhat.com>
Acked-by: David S. Miller <davem@davemloft.net>
Acked-by: Venkat Venkatsubra <venkat.x.venkatsubra@oracle.com>
next reply other threads:[~2011-11-28 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 15:28 Venkat Venkatsubra [this message]
[not found] <1322371662-26166-1-git-send-email-amwang@redhat.com>
2011-11-27 5:27 ` [PATCH 54/62] rds: remove the second argument of k[un]map_atomic() Cong Wang
2011-11-27 6:13 ` David Miller
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=fa4c1eb1-a564-4984-8648-f754c83672da@default \
--to=venkat.x.venkatsubra@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.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