From: Timur Tabi <timur@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ucc_geth: use correct UCCE macros
Date: Thu, 08 Jan 2009 13:20:17 -0600 [thread overview]
Message-ID: <496651F1.6050102@freescale.com> (raw)
In-Reply-To: <20090108.111833.163761985.davem@davemloft.net>
David Miller wrote:
> I think I'll wait for Kumar's stuff to hit Linus's tree, then
> apply this patch.
>
> The patch is safely stored in my inbox and patchwork so there
> is no need to fear it getting lost :-)
That's good enough for me. Thanks!
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, galak@kernel.crashing.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ucc_geth: use correct UCCE macros
Date: Thu, 08 Jan 2009 13:20:17 -0600 [thread overview]
Message-ID: <496651F1.6050102@freescale.com> (raw)
In-Reply-To: <20090108.111833.163761985.davem@davemloft.net>
David Miller wrote:
> I think I'll wait for Kumar's stuff to hit Linus's tree, then
> apply this patch.
>
> The patch is safely stored in my inbox and patchwork so there
> is no need to fear it getting lost :-)
That's good enough for me. Thanks!
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-01-08 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 20:12 [PATCH] ucc_geth: use correct UCCE macros Timur Tabi
2009-01-07 20:17 ` Timur Tabi
2009-01-08 19:18 ` David Miller
2009-01-08 19:18 ` David Miller
2009-01-08 19:20 ` Timur Tabi [this message]
2009-01-08 19:20 ` Timur Tabi
2009-01-11 8:25 ` David Miller
2009-01-11 8:25 ` David Miller
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=496651F1.6050102@freescale.com \
--to=timur@freescale.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--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 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.