From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Nelson, Shannon" <shannon.nelson@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] I/OAT: Add support for DCA - Direct Cache Access
Date: Thu, 26 Jul 2007 15:17:51 -0700 [thread overview]
Message-ID: <46A91D8F.2000202@intel.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707261148140.3442@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Thu, 26 Jul 2007, Nelson, Shannon wrote:
>> In order to include support for DCA (Direct Cache Access) from IOAT,
>> please pull from my git tree at
>> git://lost.foo-projects.org/~sln/linux-2.6 dma-upstream
>
> No. It's after the merge window, and I'm not interested for 2.6.23.
>
> Why cannot people learn? If it didn't get into -rc1, it's not in. It
> really is that simple. I shouldn't have to shout at people.
I/OAT / dmaengine patch merge path has been a complete mystery and
unestablished. Dave Miller acked these patches during the merge window, so if
Shannon can only send these to you during that period, and you are 100% likely
to miss the Acks, this will never get merged.
Perhaps David should start merging I/OAT stuff instead? Someone else? Chris had
the same issues when he was maintaining this.
Auke
prev parent reply other threads:[~2007-07-26 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAE9DCEF64577A439B3A37F36F9B691C02C1F61B@orsmsx418.amr.corp.in tel.com>
2007-07-26 18:41 ` [GIT PATCH] I/OAT: Add support for DCA - Direct Cache Access Nelson, Shannon
2007-07-26 18:49 ` Linus Torvalds
2007-07-26 22:17 ` Kok, Auke [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=46A91D8F.2000202@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@intel.com \
--cc=torvalds@linux-foundation.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