public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Error building after merging upstream 3.7.7
Date: Sun, 17 Feb 2013 23:16:34 +1100	[thread overview]
Message-ID: <5120CA22.5010708@crc.id.au> (raw)
In-Reply-To: <kfgm5b$c8k$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

I would *really* love to see a single .patch that can be applied to 
3.7.x kernels. This would allow me to start producing some kernel RPMs 
for using bcache on EL6 systems.

I've tried producing something that works, but haven't had much success 
in patching bcache into the vanilla kernel. Having a single patch that 
can be easily refactored as newer 3.7.x releases are done would be heaven.

--
Steven Haigh

Email: netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

On 14/02/2013 5:30 AM, Aaron W. Hsu wrote:
> I have managed to use bcache rather successfully for a while now, and I
> wanted to try getting the latest changes to the bcache branch into my
> kernel. At the same time, I wanted to merge in the latest linux stable
> changes.
>
> I did a merge of linux-stable/linux-3.7.y into the HEAD of the bcache
> branch, which seems to have worked without issue, however, after I
> configured the kernel, attempting to build the kernel errors out with the
> following message:
>
>    LD      init/built-in.o
> kernel/built-in.o:(.data+0x8bc8): undefined reference to `bcache_subsys'
>
> Is there something I have totally missed here?
>


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4240 bytes --]

  reply	other threads:[~2013-02-17 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 18:30 Error building after merging upstream 3.7.7 Aaron W.  Hsu
2013-02-17 12:16 ` Steven Haigh [this message]
2013-03-06 16:00   ` Paul Klapperich

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=5120CA22.5010708@crc.id.au \
    --to=netwiz-ty1ak9q0ptwhxe+lvdladg@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