public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: santosh shilimkar <santosh.shilimkar@oracle•com>
To: David Miller <davem@davemloft•net>
Cc: netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [net-next][PATCH v2 00/13] RDS: Major clean-up with couple of new features for 4.6
Date: Tue, 1 Mar 2016 15:09:40 -0800	[thread overview]
Message-ID: <56D62134.3000804@oracle.com> (raw)
In-Reply-To: <20160301.173308.391621325255066441.davem@davemloft.net>

On 3/1/2016 2:33 PM, David Miller wrote:
>
> When I try to apply this series, it (strangely) fails on the first patch with:
>
Strange indeed since patches and the tree is against net-next.

> Applying: RDS: Drop stale iWARP RDMA transport
> error: removal patch leaves file contents
This patch has file removals and looks like git am/apply won't
work when patch is formatted with "-D". Its good
for review but didn't realize it will create problem for
apply. Sorry for that but I didn't know this issue.

git merge or pull seems to work though when tried from branch
directly.

>
> Please sort this out and respin, thanks.
>
OK. Will send the same series again just with first
patch generated without -D option. Thanks !!

Regards,
Santosh

      reply	other threads:[~2016-03-01 23:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28  2:19 [net-next][PATCH v2 00/13] RDS: Major clean-up with couple of new features for 4.6 Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 01/13] RDS: Drop stale iWARP RDMA transport Santosh Shilimkar
2016-02-28  9:05   ` Christoph Hellwig
2016-02-28 10:11     ` santosh.shilimkar
2016-02-28 19:51   ` Or Gerlitz
2016-02-29  0:26     ` santosh.shilimkar
2016-03-02 10:54       ` Or Gerlitz
2016-02-28  2:19 ` [net-next][PATCH v2 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 03/13] MAINTAINERS: update RDS entry Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 05/13] RDS: IB: Re-organise ibmr code Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 06/13] RDS: IB: create struct rds_ib_fmr Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 07/13] RDS: IB: move FMR code to its own file Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 08/13] RDS: IB: add connection info to ibmr Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 09/13] RDS: IB: handle the RDMA CM time wait event Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 10/13] RDS: IB: add mr reused stats Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 11/13] RDS: IB: add Fastreg MR (FRMR) detection support Santosh Shilimkar
2016-02-28  9:08   ` Christoph Hellwig
2016-02-28 10:26     ` santosh.shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 12/13] RDS: IB: allocate extra space on queues for FRMR support Santosh Shilimkar
2016-02-28  2:19 ` [net-next][PATCH v2 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode Santosh Shilimkar
2016-03-01 22:33 ` [net-next][PATCH v2 00/13] RDS: Major clean-up with couple of new features for 4.6 David Miller
2016-03-01 23:09   ` santosh shilimkar [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=56D62134.3000804@oracle.com \
    --to=santosh.shilimkar@oracle$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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