From: Keith Owens <kaos@ocs.com.au>
To: Patrick van de Lageweg <patrick@bitwizard.nl>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Rogier Wolff <wolff@bitwizard.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] generic_serial's block_til_ready (fwd)
Date: Sat, 28 Oct 2000 13:21:32 +1100 [thread overview]
Message-ID: <5150.972699692@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 27 Oct 2000 15:27:04 +0200." <Pine.LNX.4.21.0010271523290.16091-100000@panoramix.bitwizard.nl>
On Fri, 27 Oct 2000 15:27:04 +0200 (CEST),
Patrick van de Lageweg <patrick@bitwizard.nl> wrote:
>This patch renames the block_til_ready of generic serial to
>gs_block_til_ready. This patch also exports the symbols needed by other
>modules with generic_serial compiled into the kernel.
>
>(it also helps when other modules have a "static block_til_ready"
>defined. This IMHO is a bug in the module-utils, but I'm told it
>cannot be fixed becuase of backwards compatibility.... Grrr. -- REW)
modutils for kernel 2.5 will break that backwards compatibility, it
goes all the way back to 2.0 kernels. But if I broke backwards
compatibility just before 2.4 kernel release, there would be a lynch
mob headed my way. In any case, block_til_ready is too generic a name
for an exported symbol.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-10-28 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 13:27 [PATCH] generic_serial's block_til_ready (fwd) Patrick van de Lageweg
2000-10-28 2:21 ` Keith Owens [this message]
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=5150.972699692@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@bitwizard.nl \
--cc=torvalds@transmeta.com \
--cc=wolff@bitwizard.nl \
/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