public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Cashin <ecashin@coraid.com>
To: jens.axboe@oracle.com, ecashin@coraid.com,
	alan@lxorguk.ukuu.org.uk, akpm@linux-foundation.org,
	apw@canonical.com, bonbons@linux-vserver.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aoe: end barrier bios with EOPNOTSUPP
Date: Thu, 10 Sep 2009 16:20:34 -0400	[thread overview]
Message-ID: <178912f8877bbbbbd5aa5cd4a082f8a9@coraid.com> (raw)
In-Reply-To: <20090910200735.GX18599@kernel.dk>

On Thu Sep 10 16:07:37 EDT 2009, jens.axboe@oracle.com wrote:
> On Thu, Sep 10 2009, Ed Cashin wrote:
...
> > So, yes, if you don't mind pushing the patch to the appropriate place,
> > that would be great.
> 
> Did you repost a non-whitespace damaged version?

Yes.  I'll post it again as a response to this email.

> > Now I have to figure out why the other patch in aoe's quilt tree for
> > linux-next never made it to 2.6.31.
> 
> Things don't go from -next to mainstream automatically, -next is just a
> testing base. You have to submit it explicitly, eg send it to me.

Ah.  Thanks.

-- 
  Ed

  reply	other threads:[~2009-09-10 20:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909021955.n82JtkrI032267@imap1.linux-foundation.org>
     [not found] ` <20090903063539.GH12579@kernel.dk>
     [not found]   ` <2339aa04a4e8fb440a52624273728352@coraid.com>
     [not found]     ` <20090904183525.GB18599@kernel.dk>
     [not found]       ` <f48e25c99e41e375f2ddd85989cd39e1@coraid.com>
     [not found]         ` <20090905051735.GH18599@kernel.dk>
     [not found]           ` <366469f19c41e0150028b886f6859019@coraid.com>
     [not found]             ` <20090908193540.GB18599@kernel.dk>
2009-09-09 16:45               ` [PATCH] aoe: end barrier bios with EOPNOTSUPP Ed Cashin
2009-09-09 16:50                 ` Ed Cashin
2009-09-09 19:03                   ` Ed Cashin
2009-09-09 16:51                 ` Daniel Walker
2009-09-09 17:08                 ` Alan Cox
2009-09-09 18:00                   ` Ed Cashin
2009-09-09 20:58                     ` Jens Axboe
2009-09-09 21:23                       ` Ed Cashin
2009-09-10  7:48                         ` Jens Axboe
2009-09-10 15:16                           ` Ed Cashin
2009-09-10 19:50                             ` Jens Axboe
2009-09-10 20:03                               ` Ed Cashin
2009-09-10 20:07                                 ` Jens Axboe
2009-09-10 20:20                                   ` Ed Cashin [this message]
2009-09-10 20:27                                     ` Ed Cashin
2009-09-10 20:29                                       ` Jens Axboe

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=178912f8877bbbbbd5aa5cd4a082f8a9@coraid.com \
    --to=ecashin@coraid.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=apw@canonical.com \
    --cc=bonbons@linux-vserver.org \
    --cc=jens.axboe@oracle.com \
    --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