From: Greg KH <greg@kroah.com>
To: Bob Beers <bob.beers@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: wanPMC-CxT1E1
Date: Wed, 28 Oct 2009 11:11:32 -0700 [thread overview]
Message-ID: <20091028181132.GA3815@kroah.com> (raw)
In-Reply-To: <4f6ba3b0910271048n10ff37fek9af191b133892e1e@mail.gmail.com>
On Tue, Oct 27, 2009 at 01:48:53PM -0400, Bob Beers wrote:
> On Mon, Oct 26, 2009 at 4:41 PM, Greg KH <greg@kroah.com> wrote:
> > Getting it to build on 2.6.31 is more important than RHEL5, we can't do
> > anything with an old kernel like that.
>
> ok, so where do I start, I have a system ready to start
> git cloning, and creating patches. I googled for a while
> but didn't find a nice recipe for participating in the -staging
> process.
I'll try to get it to build in the kernel tree today and send you a copy
of the patch to try out.
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-28 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 20:22 wanPMC-CxT1E1 Bob Beers
2009-10-26 20:41 ` wanPMC-CxT1E1 Greg KH
2009-10-26 20:57 ` wanPMC-CxT1E1 Bob Beers
2009-10-26 21:20 ` wanPMC-CxT1E1 Greg KH
2009-10-27 17:48 ` wanPMC-CxT1E1 Bob Beers
2009-10-28 18:11 ` Greg KH [this message]
2009-10-29 1:05 ` wanPMC-CxT1E1 Greg KH
2009-10-29 1:43 ` wanPMC-CxT1E1 Bob Beers
2009-10-29 2:54 ` wanPMC-CxT1E1 Greg KH
2009-10-29 13:54 ` wanPMC-CxT1E1 Krzysztof Halasa
2009-10-30 1:52 ` wanPMC-CxT1E1 Krzysztof Halasa
2009-11-02 20:41 ` wanPMC-CxT1E1 Bob Beers
2009-11-02 20:59 ` wanPMC-CxT1E1 Greg KH
[not found] ` <4f6ba3b0911021316v16ff7431s4dfa939743541df6@mail.gmail.com>
2009-11-02 21:35 ` wanPMC-CxT1E1 Bob Beers
2009-11-02 21:39 ` wanPMC-CxT1E1 Bob Beers
2009-11-06 15:25 ` wanPMC-CxT1E1 Bob Beers
2009-11-06 22:05 ` wanPMC-CxT1E1 Greg KH
2009-11-19 22:25 ` wanPMC-CxT1E1 Greg KH
2009-12-02 14:57 ` wanPMC-CxT1E1 Bob Beers
[not found] ` <4f6ba3b1003040540v4619afa8v7f28ef5d75514c47@mail.gmail.com>
2010-03-04 15:47 ` wanPMC-CxT1E1 Greg KH
2010-03-04 16:06 ` wanPMC-CxT1E1 Bob Beers
2010-03-04 16:18 ` wanPMC-CxT1E1 Greg KH
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=20091028181132.GA3815@kroah.com \
--to=greg@kroah.com \
--cc=bob.beers@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).