From: Jack Morgenstein <jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>
Cc: tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org,
dotanb-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Upgrading your "for-next" git to 3.4-RC5
Date: Tue, 8 May 2012 13:29:09 +0300 [thread overview]
Message-ID: <201205081329.10340.jackm@dev.mellanox.co.il> (raw)
In-Reply-To: <201205071105.43951.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Hi Roland,
Sorry to bother you, but the commits in your "ib-fixes" tag were taken by Linus into 3.4-rc5.
Therefore, I would appreciate it if you could rebase your "for-next" branch to 3.4-rc5 (at least)
-- I am in the middle of preparing a patch set for SRIOV-IB on top of your "for-next" branch,
so such a rebase would help.
Thanks!
-Jack
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2012-05-08 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201205071105.43951.jackm@dev.mellanox.co.il>
[not found] ` <201205071105.43951.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2012-05-08 10:29 ` Jack Morgenstein [this message]
[not found] ` <201205081329.10340.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2012-05-08 18:20 ` Upgrading your "for-next" git to 3.4-RC5 Roland Dreier
2012-05-09 5:54 ` Jack Morgenstein
[not found] ` <201205090854.25717.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2012-05-10 5:38 ` Roland Dreier
[not found] ` <CAL1RGDUyYa+m2=FeSb+ONrX5peXZvq777RwNvyup2ho5SZtzeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-10 6:21 ` Or Gerlitz
[not found] ` <4FAB5E66.7090009-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-05-10 7:52 ` 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=201205081329.10340.jackm@dev.mellanox.co.il \
--to=jackm-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=dotanb-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
--cc=tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.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