LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hoang-Nam Nguyen <HNGUYEN@de.ibm.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: hch@infradead.org, Christoph Raisch <raisch@de.ibm.com>,
Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
linuxppc-dev-bounces+hnguyen=de.ibm.com@ozlabs.org,
openfabrics-ewg@openib.org, openib-general@openib.org
Subject: Re: [PATCH/RFC 2.6.21] ehca: ehca_uverbs.c: refactor ehca_mmap() for better readability
Date: Thu, 18 Jan 2007 14:57:54 -0500 [thread overview]
Message-ID: <OF2AD534B2.A4948D9F-ONC1257267.006D39E5-85257267.006DAB06@de.ibm.com> (raw)
In-Reply-To: <adavej4b1vi.fsf@cisco.com>
No problem. Will resend the full patch set for 2.6.21.
Thanks
Nam
linuxppc-dev-bounces+hnguyen=de.ibm.com@ozlabs.org wrote on 18.01.2007
13:56:01:
> I've kind of lost the plot here. How does this patch fit in with the
> previous series of patches you posted? Does it replace them or go on
> top of them?
>
> Can please you resend me the full series of patch that remove the use
> of do_mmap(), with all cleanups and bug fixes included? And please
> roll up the fixes, I don't want one patch that adds a yield() inside a
> spinlock and then a later patch to fix it -- there's no sense in
> adding landmines for people potentially doing git bisect in the
> future.
>
> And also please try to split the patches so that they don't mix
> together two things -- please try to make the "remove obsolete
> prototypes" patch separate from the mmap fixes.
>
> Thanks...
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-01-18 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 22:12 Hoang-Nam Nguyen
2007-01-18 18:56 ` Roland Dreier
2007-01-18 19:57 ` Hoang-Nam Nguyen [this message]
2007-01-18 22:27 ` Christoph Hellwig
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=OF2AD534B2.A4948D9F-ONC1257267.006D39E5-85257267.006DAB06@de.ibm.com \
--to=hnguyen@de.ibm.com \
--cc=hch@infradead.org \
--cc=hnguyen@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev-bounces+hnguyen=de.ibm.com@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openfabrics-ewg@openib.org \
--cc=openib-general@openib.org \
--cc=raisch@de.ibm.com \
--cc=rdreier@cisco.com \
--subject='Re: [PATCH/RFC 2.6.21] ehca: ehca_uverbs.c: refactor ehca_mmap() for better readability' \
/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
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).