From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "axboe@fb.com" <axboe@fb.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: block for-next: zram build error
Date: Thu, 2 Feb 2017 23:40:54 +0000 [thread overview]
Message-ID: <1486078839.2816.24.camel@sandisk.com> (raw)
SGVsbG8gSmVucywNCg0KSSBub3RpY2VkIGFjY2lkZW50YWxseSB0aGF0IHdpdGggdGhlIGZvci1u
ZXh0IGJyYW5jaCBvZiB0aGUgYmxvY2sNCmdpdCByZXBvc2l0b3J5IHRoYXQgdGhlIHpyYW0gZHJp
dmVyIGRvZXNuJ3QgYnVpbGQgYW55bW9yZToNCg0KDQokIG1ha2UgTT1kcml2ZXJzL2Jsb2NrL3py
YW0NCsKgIExEwqDCoMKgwqDCoMKgZHJpdmVycy9ibG9jay96cmFtL2J1aWx0LWluLm8NCsKgIEND
IFtNXcKgwqBkcml2ZXJzL2Jsb2NrL3pyYW0vemNvbXAubw0KwqAgQ0MgW01dwqDCoGRyaXZlcnMv
YmxvY2svenJhbS96cmFtX2Rydi5vDQpkcml2ZXJzL2Jsb2NrL3pyYW0venJhbV9kcnYuYzogSW4g
ZnVuY3Rpb24g4oCYenJhbV9yZXZhbGlkYXRlX2Rpc2vigJk6DQpkcml2ZXJzL2Jsb2NrL3pyYW0v
enJhbV9kcnYuYzoxMjA6Mzc6IGVycm9yOiDigJh6cmFtLT5kaXNrLT5xdWV1ZS0+YmFja2luZ19k
ZXZfaW5mb+KAmSBpcyBhIHBvaW50ZXI7IGRpZCB5b3UgbWVhbiB0byB1c2Ug4oCYLT7igJk/DQrC
oCB6cmFtLT5kaXNrLT5xdWV1ZS0+YmFja2luZ19kZXZfaW5mby5jYXBhYmlsaXRpZXMgfD0NCsKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgXg0KwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAtPg0KbWFrZVsxXTogKioqIFtzY3Jp
cHRzL01ha2VmaWxlLmJ1aWxkOjI5NDogZHJpdmVycy9ibG9jay96cmFtL3pyYW1fZHJ2Lm9dIEVy
cm9yIDENCm1ha2U6ICoqKiBbTWFrZWZpbGU6MTQ5MDogX21vZHVsZV9kcml2ZXJzL2Jsb2NrL3py
YW1dIEVycm9yIDINCg0KQ29tcGlsYXRpb24gZXhpdGVkIGFibm9ybWFsbHkgd2l0aCBjb2RlIDIg
YXQgVGh1IEZlYsKgwqAyIDE1OjM3OjE5DQoNCg0KSSBoYXZlIG5vdCB5ZXQgdHJpZWQgdG8gZmln
dXJlIG91dCB3aGljaCBjb21taXQgYnJva2UgdGhlIGJ1aWxkLg0KDQpCYXJ0Lg==
next reply other threads:[~2017-02-02 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 23:40 Bart Van Assche [this message]
2017-02-02 23:56 ` block for-next: zram build error 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=1486078839.2816.24.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@fb.com \
--cc=linux-block@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