From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [2.6 patch] make hdlc_setup() static again
Date: Sun, 26 Nov 2006 20:22:53 +0100 [thread overview]
Message-ID: <m3odqu812q.fsf@defiant.localdomain> (raw)
In-Reply-To: <20061125191653.GJ3702@stusta.de> (Adrian Bunk's message of "Sat, 25 Nov 2006 20:16:53 +0100")
Adrian Bunk <bunk@stusta.de> writes:
> It's still not used...
>
> So let's unexport it again until some driver that actually uses it shows up.
Fair enough.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-11-26 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 20:51 -git: Why is drivers/net/wan/hdlc_generic.c:hdlc_setup() exported? Adrian Bunk
2006-06-26 19:28 ` Krzysztof Halasa
2006-11-25 19:16 ` [2.6 patch] make hdlc_setup() static again Adrian Bunk
2006-11-26 19:22 ` Krzysztof Halasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 13:48 Adrian Bunk
2007-01-19 3:01 ` Jeff Garzik
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=m3odqu812q.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=bunk@stusta.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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 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).