From: Mikkel Krautz <krautz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com, roms@lpg.ticalc.org, jb@technologeek.org
Subject: [PATCH 0/3] TIGLUSB Cleanups
Date: Wed, 26 Jan 2005 17:04:29 +0100 [thread overview]
Message-ID: <41F7BF8D.70205@gmail.com> (raw)
Hello!
The tiglusb-driver was removed in 2.6.11-rc1.
Since then, references to it in other files have been kept, namely the
following files:
Documentation/usb/silverlink.txt,
Documentation/kernel-parameters.txt
MAINTAINERS
This series of patches removes the silverlink.txt-documentation, and
tiglusb-references in MAINTAINERS and kernel-parameters.txt.
The patches are diffed against 2.6.11-rc2-bk4.
Thanks,
Mikkel Krautz
next reply other threads:[~2005-01-26 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 16:04 Mikkel Krautz [this message]
2005-01-26 16:27 ` [PATCH 0/3] TIGLUSB Cleanups Mikkel Krautz
2005-01-26 16:40 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 16:48 Mikkel Krautz
2005-01-26 16:57 ` Greg KH
2005-01-26 17:01 ` Mikkel Krautz
2005-01-26 17:17 ` Greg KH
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=41F7BF8D.70205@gmail.com \
--to=krautz@gmail.com \
--cc=greg@kroah.com \
--cc=jb@technologeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roms@lpg.ticalc.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