linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "hch@infradead.org" <hch@infradead.org>
To: James Bottomley <jbottomley@parallels.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"MinhDuc.Tran@Emulex.Com" <MinhDuc.Tran@Emulex.Com>,
	"jayamohank@gmail.com" <jayamohank@gmail.com>,
	"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
	"Sony.John-N@Emulex.Com" <Sony.John-N@Emulex.Com>,
	"Jayamohan.Kallickal@Emulex.Com" <Jayamohan.Kallickal@Emulex.Com>
Subject: Re: [PATCH 7/8] be2iscsi: Fix processing cqe for cxn whose endpoint is freed
Date: Mon, 2 Jun 2014 12:33:49 -0700	[thread overview]
Message-ID: <20140602193349.GA11555@infradead.org> (raw)
In-Reply-To: <1401736926.12939.13.camel@dabdike.int.hansenpartnership.com>

On Mon, Jun 02, 2014 at 07:22:07PM +0000, James Bottomley wrote:
> Actually, can you really pull it out, not just revert it?  Reverts cause
> problems with bisection and are unnecessary before the tree goes to
> Linus.
> 
> If preserving history becomes a real goal, we'd have to move to a tip
> like model, but I'm happy coping with the rebase that dropping a patch
> from a monolithic tree causes.

Linus has been very unappy about rebasing close to or in the merge
window, and other subsystems generally revert patches that late in the
cycle as well.  I'd prefer to stick to that model, but if you and Linus
prefer the rebase now I can do it as well of course.

  reply	other threads:[~2014-06-02 19:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06  1:41 [PATCH 1/8] be2iscsi: Fix retrieving MCCQ_WRB in non-embedded Mbox path Jay Kallickal
2014-05-06  1:41 ` [PATCH 2/8] be2iscsi: Fix exposing Host in sysfs after adapter initialization is complete Jay Kallickal
2014-05-06  1:41 ` [PATCH 3/8] be2iscsi: Fix interrupt Coalescing mechanism Jay Kallickal
2014-05-06  1:41 ` [PATCH 4/8] be2iscsi: Fix TCP parameters while connection offloading Jay Kallickal
2014-05-06  1:41 ` [PATCH 5/8] be2iscsi: Fix memory corruption in MBX path Jay Kallickal
2014-05-06  1:41 ` [PATCH 6/8] be2iscsi: Fix destroy MCC-CQ before MCC-EQ is destroyed Jay Kallickal
2014-05-06  1:41 ` [PATCH 7/8] be2iscsi: Fix processing cqe for cxn whose endpoint is freed Jay Kallickal
2014-05-07 22:18   ` Mike Christie
2014-05-28 15:51     ` Christoph Hellwig
2014-06-02  5:52     ` Sony John-N
2014-06-02  6:46       ` Christoph Hellwig
2014-06-02 19:22         ` James Bottomley
2014-06-02 19:33           ` hch [this message]
2014-06-02 20:02             ` James Bottomley
2014-06-02 20:05             ` Linus Torvalds
2014-06-02 20:08               ` hch
2014-06-02 20:24                 ` Linus Torvalds
2014-06-02 20:32                   ` hch
2014-05-06  1:41 ` [PATCH 8/8] be2iscsi: Bump the driver version Jay Kallickal
2014-05-06  1:41 ` [PATCH 0/8] be2iscsi: update to 10.2.273.0 Jay Kallickal

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=20140602193349.GA11555@infradead.org \
    --to=hch@infradead.org \
    --cc=Jayamohan.Kallickal@Emulex.Com \
    --cc=MinhDuc.Tran@Emulex.Com \
    --cc=Sony.John-N@Emulex.Com \
    --cc=jayamohank@gmail.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --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;
as well as URLs for NNTP newsgroup(s).