From: axboe@fb.com (Jens Axboe)
Subject: [PATCH v2] nvme: fix 32-bit build warning
Date: Mon, 12 Oct 2015 13:22:36 -0600 [thread overview]
Message-ID: <561C087C.1010900@fb.com> (raw)
In-Reply-To: <5683852.vTfiqtLZLZ@wuerfel>
On 10/12/2015 01:14 PM, Arnd Bergmann wrote:
> On Monday 12 October 2015 13:10:17 Jens Axboe wrote:
>> On 10/12/2015 01:03 PM, Christoph Hellwig wrote:
>>> Looks good,
>>>
>>> Reviewed-by: Christoph Hellwig <hch at lst.de>
>>>
>>> Note that we're moved the nvme driver to a new directory in the
>>> block tree, but I can rebase it for you if you want.
>>
>> I man handled it on both branches, so we should be good.
>
> Thanks! I already saw the move, and it caused another build error
> when CONFIG_BLOCK is disabled. Do you have this one?
I do, Keith sent that one in earlier today, it's in the 4.4 branch.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: axboe@fb.com (Jens Axboe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] nvme: fix 32-bit build warning
Date: Mon, 12 Oct 2015 13:22:36 -0600 [thread overview]
Message-ID: <561C087C.1010900@fb.com> (raw)
In-Reply-To: <5683852.vTfiqtLZLZ@wuerfel>
On 10/12/2015 01:14 PM, Arnd Bergmann wrote:
> On Monday 12 October 2015 13:10:17 Jens Axboe wrote:
>> On 10/12/2015 01:03 PM, Christoph Hellwig wrote:
>>> Looks good,
>>>
>>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>>
>>> Note that we're moved the nvme driver to a new directory in the
>>> block tree, but I can rebase it for you if you want.
>>
>> I man handled it on both branches, so we should be good.
>
> Thanks! I already saw the move, and it caused another build error
> when CONFIG_BLOCK is disabled. Do you have this one?
I do, Keith sent that one in earlier today, it's in the 4.4 branch.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Arnd Bergmann <arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@linux.intel.com>,
<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] nvme: fix 32-bit build warning
Date: Mon, 12 Oct 2015 13:22:36 -0600 [thread overview]
Message-ID: <561C087C.1010900@fb.com> (raw)
In-Reply-To: <5683852.vTfiqtLZLZ@wuerfel>
On 10/12/2015 01:14 PM, Arnd Bergmann wrote:
> On Monday 12 October 2015 13:10:17 Jens Axboe wrote:
>> On 10/12/2015 01:03 PM, Christoph Hellwig wrote:
>>> Looks good,
>>>
>>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>>>
>>> Note that we're moved the nvme driver to a new directory in the
>>> block tree, but I can rebase it for you if you want.
>>
>> I man handled it on both branches, so we should be good.
>
> Thanks! I already saw the move, and it caused another build error
> when CONFIG_BLOCK is disabled. Do you have this one?
I do, Keith sent that one in earlier today, it's in the 4.4 branch.
--
Jens Axboe
next prev parent reply other threads:[~2015-10-12 19:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 20:37 [PATCH] nvme: fix 32-bit build warning Arnd Bergmann
2015-10-06 20:37 ` Arnd Bergmann
2015-10-06 20:37 ` Arnd Bergmann
2015-10-09 14:42 ` Christoph Hellwig
2015-10-09 14:42 ` Christoph Hellwig
2015-10-09 14:42 ` Christoph Hellwig
2015-10-09 18:55 ` Arnd Bergmann
2015-10-09 18:55 ` Arnd Bergmann
2015-10-09 18:55 ` Arnd Bergmann
2015-10-09 18:58 ` [PATCH v2] " Arnd Bergmann
2015-10-09 18:58 ` Arnd Bergmann
2015-10-09 18:58 ` Arnd Bergmann
2015-10-12 19:03 ` Christoph Hellwig
2015-10-12 19:03 ` Christoph Hellwig
2015-10-12 19:03 ` Christoph Hellwig
2015-10-12 19:10 ` Jens Axboe
2015-10-12 19:10 ` Jens Axboe
2015-10-12 19:10 ` Jens Axboe
2015-10-12 19:14 ` Arnd Bergmann
2015-10-12 19:14 ` Arnd Bergmann
2015-10-12 19:14 ` Arnd Bergmann
2015-10-12 19:22 ` Jens Axboe [this message]
2015-10-12 19:22 ` Jens Axboe
2015-10-12 19:22 ` 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=561C087C.1010900@fb.com \
--to=axboe@fb.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 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.