All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Goode <emilgoode@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] NVMe: Fix incompatible pointer type warnings
Date: Fri, 17 May 2013 15:22:20 +0000	[thread overview]
Message-ID: <20130517152220.GA2807@debian> (raw)
In-Reply-To: <20130517144526.GV6057@linux.intel.com>

I see, I will resend and include Andrew Morton.

Thanks,

Emil

On Fri, May 17, 2013 at 10:45:26AM -0400, Matthew Wilcox wrote:
> On Fri, May 17, 2013 at 04:09:40PM +0200, Emil Goode wrote:
> > Commit 6a4d55146334 ("block: prep work for batch completion")
> > added a struct batch_complete * as a third argument to bi_end_io.
> > This patch adds the missing third argument to the nvme_bio_pair_endio
> > function.
> 
> That patch isn't in Linus' tree yet, so we can't apply this patch.  It needs
> to go to linux-next.

WARNING: multiple messages have this Message-ID (diff)
From: emilgoode@gmail.com (Emil Goode)
Subject: [PATCH] NVMe: Fix incompatible pointer type warnings
Date: Fri, 17 May 2013 17:22:20 +0200	[thread overview]
Message-ID: <20130517152220.GA2807@debian> (raw)
In-Reply-To: <20130517144526.GV6057@linux.intel.com>

I see, I will resend and include Andrew Morton.

Thanks,

Emil

On Fri, May 17, 2013@10:45:26AM -0400, Matthew Wilcox wrote:
> On Fri, May 17, 2013@04:09:40PM +0200, Emil Goode wrote:
> > Commit 6a4d55146334 ("block: prep work for batch completion")
> > added a struct batch_complete * as a third argument to bi_end_io.
> > This patch adds the missing third argument to the nvme_bio_pair_endio
> > function.
> 
> That patch isn't in Linus' tree yet, so we can't apply this patch.  It needs
> to go to linux-next.

WARNING: multiple messages have this Message-ID (diff)
From: Emil Goode <emilgoode@gmail.com>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: keith.busch@intel.com, vishal.l.verma@intel.com,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] NVMe: Fix incompatible pointer type warnings
Date: Fri, 17 May 2013 17:22:20 +0200	[thread overview]
Message-ID: <20130517152220.GA2807@debian> (raw)
In-Reply-To: <20130517144526.GV6057@linux.intel.com>

I see, I will resend and include Andrew Morton.

Thanks,

Emil

On Fri, May 17, 2013 at 10:45:26AM -0400, Matthew Wilcox wrote:
> On Fri, May 17, 2013 at 04:09:40PM +0200, Emil Goode wrote:
> > Commit 6a4d55146334 ("block: prep work for batch completion")
> > added a struct batch_complete * as a third argument to bi_end_io.
> > This patch adds the missing third argument to the nvme_bio_pair_endio
> > function.
> 
> That patch isn't in Linus' tree yet, so we can't apply this patch.  It needs
> to go to linux-next.

  parent reply	other threads:[~2013-05-17 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 14:09 [PATCH] NVMe: Fix incompatible pointer type warnings Emil Goode
2013-05-17 14:09 ` Emil Goode
2013-05-17 14:09 ` Emil Goode
2013-05-17 14:45 ` Matthew Wilcox
2013-05-17 14:45   ` Matthew Wilcox
2013-05-17 14:45   ` Matthew Wilcox
2013-05-17 15:08   ` Dan Carpenter
2013-05-17 15:08     ` Dan Carpenter
2013-05-17 15:08     ` Dan Carpenter
2013-05-17 15:22   ` Emil Goode [this message]
2013-05-17 15:22     ` Emil Goode
2013-05-17 15:22     ` Emil Goode

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=20130517152220.GA2807@debian \
    --to=emilgoode@gmail.com \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.