All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Linux 3.11-rc4 Writeback Cache Corruption
Date: Tue, 3 Sep 2013 21:38:38 +0000 (UTC)	[thread overview]
Message-ID: <l05ksu$cgc$1@ger.gmane.org> (raw)
In-Reply-To: 52265410.4010000@bahj.com

On Tue, 03 Sep 2013 17:26:40 -0400, Zachary Palmer wrote:
> So here's the question: how would I best go about testing this patch?  
> In looking through the git history, it doesn't seem as if the 
> bcache-for-3.11 branch has been synced against the Linux git since 
> 3.10-rc7 (on June 22nd).  I was thinking I could
> 
>      * Pull the Linux kernel source
>      * Add the bcache git as an origin
>      * Merge the bcache-for-3.11 branch into the Linux 3.11 mainline 
> branch myself and
>      * Assuming that this works, compile and boot the resulting kernel 
> using my Debian kernel .config
> 
> Does this sound reasonable?  Or is there a better way to do this? I'm 
> pretty happy with whatever gives me at least the behavior of my mainline 
> 3.10 kernel and I'm looking forward to getting bcache and laptop power 
> modes on the same machine.  :)

Yeah, it'll merge cleanly.  You can reuse the .config and build with
`make deb-pkg -j -l6`, which is slowly replacing make-kpkg functionality.

  reply	other threads:[~2013-09-03 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 21:26 Linux 3.11-rc4 Writeback Cache Corruption Zachary Palmer
2013-09-03 21:38 ` Gabriel de Perthuis [this message]
     [not found] ` <522656EC.8040002@gmail.com>
     [not found]   ` <5227F74F.5000305@bahj.com>
     [not found]     ` <5227F74F.5000305-J5qI5MFTcs8@public.gmane.org>
2013-09-05  3:16       ` Zachary Palmer
     [not found]         ` <5227F774.7010002-J5qI5MFTcs8@public.gmane.org>
2013-09-05  4:08           ` Josep Lladonosa

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='l05ksu$cgc$1@ger.gmane.org' \
    --to=g2p.code-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 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.