From: maximilian attems <max@stro.at>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Al Viro <viro@ftp.linux.org.uk>, Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, Andres Salomon <dilinger@debian.org>,
Alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch] dgrs removal
Date: Thu, 6 Sep 2007 16:16:29 +0200 [thread overview]
Message-ID: <20070906141629.GK16317@baikonur.stro.at> (raw)
In-Reply-To: <20070906135023.GA16304@stro.at>
On Thu, Sep 06, 2007 at 03:50:23PM +0200, maximilian attems wrote:
> b/drivers/net/wireless/rtl8187_dev.c | 1
> 15 files changed, 1 insertion(+), 12846 deletions(-)
urrgs that was not meant to be there,
resending..
--
maks
next prev parent reply other threads:[~2007-09-06 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 12:55 dgrs: sparse warnings Stephen Hemminger
2007-09-06 13:30 ` maximilian attems
2007-09-06 13:50 ` [patch] dgrs removal maximilian attems
2007-09-06 14:16 ` maximilian attems [this message]
2007-09-06 14:24 ` maximilian attems
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=20070906141629.GK16317@baikonur.stro.at \
--to=max@stro.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dilinger@debian.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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).