From: Ralf Baechle <ralf@linux-mips.org>
To: James E Wilson <wilson@specifix.com>
Cc: linux-mips@linux-mips.org
Subject: Re: bcm1480 doubled process accounting times
Date: Mon, 12 Jun 2006 22:23:17 +0100 [thread overview]
Message-ID: <20060612212317.GA6565@linux-mips.org> (raw)
In-Reply-To: <1150144825.9243.90.camel@aretha.corp.specifix.com>
On Mon, Jun 12, 2006 at 01:40:25PM -0700, James E Wilson wrote:
> I'd like some info about how to get patches into the linux kernel.
>
> I sent this patch in February.
> http://www.linux-mips.org/archives/linux-mips/2006-02/msg00404.html
> I've been using it since then without apparent problem. I didn't get
> any comments from my earlier message, and I see the patch hasn't made it
> into the tree on linux-mips yet.
>
> How can I get this patch into the linux kernel tree?
Blame me, things do get lost. Resending and yelling is the protocol.
Will apply in a minute.
Ralf
prev parent reply other threads:[~2006-06-12 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 23:04 bcm1480 doubled process accounting times James E Wilson
2006-06-12 20:40 ` James E Wilson
2006-06-12 21:23 ` Ralf Baechle [this message]
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=20060612212317.GA6565@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=wilson@specifix.com \
/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