From: Jeff Moyer <jmoyer@redhat.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>,
Suparna bhattacharya <suparna@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Leonid Ananiev <leonid.i.ananiev@intel.com>
Subject: Re: [PATCH 1/2] aio: create aio_ring_insert_entry() function
Date: Mon, 19 Feb 2007 17:41:04 -0500 [thread overview]
Message-ID: <x49649x6a9r.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20070219213830.4032.71308.sendpatchset@tetsuo.zabbo.net> (Zach Brown's message of "Mon, 19 Feb 2007 13:38:30 -0800 (PST)")
==> On Mon, 19 Feb 2007 13:38:30 -0800 (PST), Zach Brown <zach.brown@oracle.com> said:
Zach> This patch just hoists the process of inserting an entry into the completion
Zach> ring into its own function. No functionality is changed. This is in
Zach> preparation for calling ring insertion from another path with slightly
Zach> different mechanics.
Looks harmless.
Acked-by: Jeff Moyer <jmoyer@redhat.com>
prev parent reply other threads:[~2007-02-19 22:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:38 Zach Brown
2007-02-19 21:38 ` [PATCH 2/2] aio: propogate post-EIOCBQUEUED errors to completion event Zach Brown
2007-02-19 22:48 ` Jeff Moyer
2007-02-19 22:57 ` Zach Brown
2007-02-20 16:57 ` Ananiev, Leonid I
2007-02-20 17:03 ` Chris Mason
2007-02-20 17:17 ` Ananiev, Leonid I
2007-02-20 17:54 ` Chris Mason
2007-02-20 21:09 ` Ananiev, Leonid I
2007-02-21 8:35 ` Ken Chen
2007-02-21 8:44 ` Ananiev, Leonid I
2007-02-21 18:24 ` Zach Brown
2007-02-21 19:15 ` Ananiev, Leonid I
2007-02-20 17:33 ` Ananiev, Leonid I
2007-02-20 18:26 ` Zach Brown
2007-02-21 14:13 ` Suparna Bhattacharya
2007-02-21 18:34 ` Zach Brown
2007-02-19 22:41 ` Jeff Moyer [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=x49649x6a9r.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=leonid.i.ananiev@intel.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=zach.brown@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
all inboxes | Powered by JetHome®