From: Phillip Susi <psusi@cfl.rr.com>
To: Ken D'Ambrosio <ken@jots.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs/git question.
Date: Mon, 28 Nov 2011 20:58:08 -0500 [thread overview]
Message-ID: <4ED43C30.50502@cfl.rr.com> (raw)
In-Reply-To: <af6c5f5cb5a1778a8d811e8293dfdd73@www.jots.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/28/2011 12:53 PM, Ken D'Ambrosio wrote:
> Seems I've picked up a wireless regression, and randomly drop my WiFi
> connection with more recent kernels. While I'd love to try to track down the
> issue, the sporadic nature makes it difficult. But I don't want to revert to a
> flat-out old kernel because of all the btrfs modifications. Is 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7UPDAACgkQJ4UciIs+XuLauQCgi9iTXZGD5BVTyTQJoc3Mm1R4
Oi8AmwX0oqwdF4e3dOTtAoUgFeYbKnOt
=i3i2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-29 1:58 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 [this message]
2011-11-29 2:33 ` Fajar A. Nugraha
2011-11-29 15:22 ` Chris Mason
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=4ED43C30.50502@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=ken@jots.org \
--cc=linux-btrfs@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