From: Jason Warr <jason-/cow75dQlsI@public.gmane.org>
To: Kent Overstreet
<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache & kernel branch that will build together
Date: Mon, 09 Jul 2012 16:48:43 -0500 [thread overview]
Message-ID: <4FFB51BB.7050905@warr.net> (raw)
In-Reply-To: <CAC7rs0vkasCKYwBTrvhWg8pzvHuix1ZaBJxTLBW+5AVG_31hEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Excellent. That builds fine for me against 3.5rc6.
Much appreciated.
Now to see if I can get the Fedora "patched" source to build and boot.
On 07/09/2012 03:16 PM, Kent Overstreet wrote:
> Ok, I think I got them all fixed - the code that's up now should build for you.
>
> On Mon, Jul 9, 2012 at 11:41 AM, Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
>> On Mon, Jul 09, 2012 at 01:07:16PM -0500, Jason Warr wrote:
>>> Dumb question coming from someone who is more of an admin than a
>>> developer. Although I did build and run a dev lab at Sun in the
>>> early days of Solaris Nevada.
>>>
>>> What kernel source version or branch will your current git tree patch to and compile with?
>>>
>>> I have tried everything from 3.5rc1 to Linus's current git tree. It
>>> breaks DRBD. Once I disable DRBD in the config it fails at
>>> target_core_iblock.c. So I never get a full build.
>>>
>>> So either I am doing something obviously wrong or ???
>>
>> Bah, sounds like I didn't test my code when I rebased to 3.5. Lazy me.
>>
>> For the moment, if you're not actually using drbd or iscsi you could
>> just disable both of those in the config. Assuming I didn't break dm and
>> md too. heh.
>>
>>>
>>> I'd love to test this out and help with debugging. I have plenty of
>>> hardware and interest in it working well. I can even provide you
>>> access to debug when I hit an issue.
>>
>> Cool!
>>
>>> What error output can I provide and can you point me to good trees?
>>
>> You could send me your .config in case it turns out to be something
>> specific to your specific config. Ought to be something simple, though.
>>
>>> I appreciate it and I am glad to see that someone is finally making
>>> the effort to get a real, working block cache object into the
>>> kernel. I will help in any way I can.
>>
>> Thanks :)
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-09 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 12:08 bcache-3.2 branch Joseph Glanville
[not found] ` <CAOzFzEh8pO37dVWoMoD+hFoUGrBoubSdktdu7SQS0UcXLcC66w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-09 15:57 ` Kent Overstreet
[not found] ` <20120709155734.GA23774-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-07-09 16:32 ` Joseph Glanville
[not found] ` <CAOzFzEjovYu4eE9E_asOBVyBhqFuvhgzJ7UFyESLY0XycAfkuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-09 17:07 ` Kent Overstreet
[not found] ` <20120709170742.GA26798-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-07-09 18:07 ` bcache & kernel branch that will build together Jason Warr
[not found] ` <4FFB1DD4.7030304-/cow75dQlsI@public.gmane.org>
2012-07-09 18:41 ` Kent Overstreet
[not found] ` <20120709184149.GA3234-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-07-09 20:16 ` Kent Overstreet
[not found] ` <CAC7rs0vkasCKYwBTrvhWg8pzvHuix1ZaBJxTLBW+5AVG_31hEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-09 21:48 ` Jason Warr [this message]
2012-07-10 18:52 ` bcache-3.2 branch Joseph Glanville
[not found] ` <CAOzFzEjUy9zakyBhE5CNhcP-Dv7+hQBz3uzhKsMy5kj5GxfGwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-13 9:01 ` Kent Overstreet
[not found] ` <CAH+dOxKJs5WmHk2hb+6fLCs=fCK_6mezPueaewaHwSn3jZ2m0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-13 21:10 ` Joseph Glanville
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=4FFB51BB.7050905@warr.net \
--to=jason-/cow75dqlsi@public.gmane.org \
--cc=kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).