From: David Miller <davem@davemloft.net>
To: santosh.shilimkar@oracle.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next][PATCH 0/2] RDS: couple of fixes for 4.6
Date: Wed, 13 Apr 2016 23:36:37 -0400 (EDT) [thread overview]
Message-ID: <20160413.233637.2047659923049596108.davem@davemloft.net> (raw)
In-Reply-To: <1460154400-14546-1-git-send-email-santosh.shilimkar@oracle.com>
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Date: Fri, 8 Apr 2016 15:26:38 -0700
> Patches are also available at below git tree.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_4.6/net-next/rds-fixes
"Bug fixes for 4.6" do not get targetted at the net-next tree, that's
for 4.7 development.
next prev parent reply other threads:[~2016-04-14 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 22:26 [net-next][PATCH 0/2] RDS: couple of fixes for 4.6 Santosh Shilimkar
2016-04-08 22:26 ` [net-next][PATCH 1/2] RDS: fix endianness for dp_ack_seq Santosh Shilimkar
2016-04-08 22:26 ` [net-next][PATCH 2/2] RDS: Fix the atomicity for congestion map update Santosh Shilimkar
2016-04-14 3:36 ` David Miller [this message]
2016-04-14 17:44 ` [net-next][PATCH 0/2] RDS: couple of fixes for 4.6 santosh.shilimkar
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=20160413.233637.2047659923049596108.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).