linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Further 2.6.23 merge plans...
Date: Thu, 12 Jul 2007 16:15:58 -0700	[thread overview]
Message-ID: <adahco943ip.fsf@cisco.com> (raw)
In-Reply-To: <adalkdl43w0.fsf@cisco.com> (Roland Dreier's message of "Thu, 12 Jul 2007 16:07:59 -0700")

As you can see, I just sent my first 2.6.23 pull request for Linus.
There are still a few more things I plan to do in before the merge
window closes (in ~10 days):

 - Write a patch to add P_Key handling to user_mad in the way we
   discussed (add an ioctl to enable P_Key mode without breaking old
   apps) -- I hope to do this tomorrow so we can get some review and
   testing before merging it.

 - Take a look at Sean's local SA caching patches.  I merged
   everything else from Sean's tree, but I'm still undecided about
   these.  I haven't read them carefully yet, but even aside from that
   I don't have a good feeling about whether there's consensus about
   this yet.  Any opinions about merging, for or against, would be
   appreciated here.

 - Merge up pending hardware driver changes, including the cxgb3 and
   ehca patches I have in my queue, plus Jack's catastrophic error
   patch for mlx4.

 - Try to get to resolution on the IPoIB "CM without SRQ" solution.

Also, if there's something I didn't list and didn't already include in
the tree I asked Linus to pull, please remind me.  I probably dropped it.

 - R.

  reply	other threads:[~2007-07-12 23:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 23:07 [GIT PULL] please pull infiniband.git Roland Dreier
2007-07-12 23:15 ` Roland Dreier [this message]
2007-07-13  0:17   ` [ofa-general] Further 2.6.23 merge plans Hal Rosenstock
2007-07-13  1:14   ` Sean Hefty
     [not found]     ` <15ddcffd0707172020j5b68fcb2v7d3ca77863998020@mail.gmail.com>
2007-07-18  3:23       ` Roland Dreier
2007-07-18  5:26         ` Sean Hefty
2007-07-18 17:05           ` Sean Hefty
2007-07-18 20:54             ` Sean Hefty
2007-07-13  5:47   ` Michael S. Tsirkin
2007-07-13 18:14     ` Roland Dreier
2007-07-13 18:50       ` [ofa-general] " Shirley Ma
2007-07-17 18:06         ` Roland Dreier
2007-07-14 17:54       ` Michael S. Tsirkin
     [not found]         ` <OF72F6B9D1.F60C4EEF-ON8725731A.00506757-8825731A.0024BD1C@us.ibm.com>
2007-07-16 14:55           ` [ofa-general] " Michael S. Tsirkin
2007-07-16 16:42         ` Roland Dreier
2007-07-16 20:05           ` Michael S. Tsirkin
2007-07-17 17:53             ` Roland Dreier
2007-07-13 18:56   ` [ofa-general] " Shirley Ma
2007-07-16 16:47     ` Roland Dreier
2007-07-15 12:26   ` Tziporet Koren
2007-07-16 16:42     ` Roland Dreier
2007-07-17 18:07   ` Roland Dreier
2007-07-17 20:43     ` Matt Leininger
2007-07-17 20:45       ` Roland Dreier
2007-07-18  6:36         ` Or Gerlitz
2007-07-17 21:44     ` Michael S. Tsirkin
2007-07-18  7:34       ` [ofa-general] " Tziporet Koren
2007-07-18  7:38         ` Michael S. Tsirkin
2007-07-18  8:48           ` Tziporet Koren
2007-07-18 16:16             ` Sean Hefty
2007-07-18 16:20               ` Roland Dreier

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=adahco943ip.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.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).