From: Jens Axboe <axboe@fb.com>
To: Matias Bjorling <m@bjorling.me>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 1 (lightnvm)
Date: Mon, 2 Nov 2015 08:37:11 -0700 [thread overview]
Message-ID: <56378327.4020500@fb.com> (raw)
In-Reply-To: <56375A8B.9090006@bjorling.me>
On 11/02/2015 05:43 AM, Matias Bjorling wrote:
> On 11/02/2015 02:16 AM, Randy Dunlap wrote:
>> On 11/01/15 08:53, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> I start again a day early, and this is how you all repay me? ;-)
>>>
>>> Changes since 20151022:
>>>
>>
>> on i386:
>>
>> ../include/linux/lightnvm.h:143:4: error: width of 'resved' exceeds its type
>>
>> # CONFIG_LBDAF is not set
>>
>>
>
> Thanks Randy.
>
> Jens, how would you like to receive the patch? (I've currently attached
> it in this mail)
If it really needs to be 64-bit regardless of LBDAF, just make it a u64
instead of typedef'ing some new ppa_t that everybody would have to look up.
--
Jens Axboe
next prev parent reply other threads:[~2015-11-02 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 16:53 linux-next: Tree for Nov 1 Stephen Rothwell
2015-11-02 1:16 ` linux-next: Tree for Nov 1 (lightnvm) Randy Dunlap
2015-11-02 12:43 ` Matias Bjorling
2015-11-02 15:37 ` Jens Axboe [this message]
2015-11-02 22:34 ` Matias Bjorling
2015-11-03 16:53 ` Jens Axboe
2015-11-02 3:11 ` linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap
2015-11-02 13:39 ` Michal Marek
2015-11-02 13:51 ` Thiago Macieira
2015-11-02 16:44 ` Randy Dunlap
2015-11-02 16:58 ` Thiago Macieira
2015-11-02 18:48 ` Randy Dunlap
2015-11-02 19:23 ` Thiago Macieira
2015-11-02 20:42 ` Michal Marek
2015-11-02 16:01 ` Randy Dunlap
2015-11-02 8:04 ` linux-next: Tree for Nov 1 Geert Uytterhoeven
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=56378327.4020500@fb.com \
--to=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m@bjorling.me \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).