From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jgarzik@pobox.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, saw@saw.sw.com.sg
Subject: Re: [2.6.24 patch] the planned eepro100 removal
Date: Mon, 27 Aug 2007 14:58:05 -0700 [thread overview]
Message-ID: <46D348ED.9020003@intel.com> (raw)
In-Reply-To: <20070827212825.GY4121@stusta.de>
Adrian Bunk wrote:
> This patch contains the planned removal of the eepro100 driver.
>
> Signed-off-by: Adrian Bunk
you lost your e-mail address? :)
> ---
>
> This patch has been sent on:
> - 14 Aug 2007
> - 29 Jul 2007
currently we won't have e100 fixed up for ARM in 2.6.23, so removing this for
2.6.24 sounds a bit premature. Maybe 2.6.25. Can you reschedule/postpone this?
Auke
next prev parent reply other threads:[~2007-08-27 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 21:28 [2.6.24 patch] the planned eepro100 removal Adrian Bunk
2007-08-27 21:58 ` Kok, Auke [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 21:27 Adrian Bunk
2007-07-29 15:02 Adrian Bunk
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=46D348ED.9020003@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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).