All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: "Ken D'Ambrosio" <ken@jots.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs/git question.
Date: Tue, 29 Nov 2011 10:22:06 -0500	[thread overview]
Message-ID: <20111129152206.GL24338@shiny> (raw)
In-Reply-To: <CAG1y0scuoKwH_MbQPGQKr5sYAXP_kB=j6FOMHgm2=EzPwAVL=Q@mail.gmail.com>

On Tue, Nov 29, 2011 at 09:33:37AM +0700, Fajar A. Nugraha wrote:
> On Tue, Nov 29, 2011 at 8:58 AM, Phillip Susi <psusi@cfl.rr.com> wrot=
e:
> > On 11/28/2011 12:53 PM, Ken D'Ambrosio wrote:
> >> Seems I've picked up a wireless regression, and randomly drop my W=
iFi
> >> connection with more recent kernels. =A0While I'd love to try to t=
rack down the
> >> issue, the sporadic nature makes it difficult. =A0But I don't want=
 to revert to a
> >> flat-out old kernel because of all the btrfs modifications. =A0Is =
it possible
> >> using git to add *just* btrfs patches to an older kernel?
> >
> > Sure: use git rebase to apply the patches to the older kernel.
>=20
> ... or use 3.1.2, and get ONLY fs/btrfs from Chris' for-linus tree,
> compile it out-of-tree, and use it to replace the original btrfs.ko.

If you're on a 3.1 kernel, you can pull my for-linus directly on top of
it with git pull.  I always keep a btrfs tree against the previous
kernel so that people can use the latest btrfs goodness without having
to use an rc kernel.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-11-29 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28 17:53 btrfs/git question Ken D'Ambrosio
2011-11-29  1:58 ` Phillip Susi
2011-11-29  2:33   ` Fajar A. Nugraha
2011-11-29 15:22     ` Chris Mason [this message]
2011-11-30  6:20       ` Fajar A. Nugraha

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=20111129152206.GL24338@shiny \
    --to=chris.mason@oracle.com \
    --cc=ken@jots.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    /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.