mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alon Ziv <alon+git@nolaviz.org>
To: linux-usb@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, Johan Hovold <jhovold@gmail.com>,
	Alon Ziv <alon+git@nolaviz.org>
Subject: [PATCH v2 1/2] Export usb_serial_generic_write_room for use in modules
Date: Sat, 23 Oct 2010 20:43:28 +0200	[thread overview]
Message-ID: <1287859409-13810-2-git-send-email-alon-git@nolaviz.org> (raw)
In-Reply-To: <1287859409-13810-1-git-send-email-alon-git@nolaviz.org>

Any module using usb_serial_generic_write (which is already exported)
had better use usb_serial_generic_write_room as well, or be prepared
for failures.

Signed-off-by: Alon Ziv <alon-git@nolaviz.org>
---
 drivers/usb/serial/generic.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/serial/generic.c b/drivers/usb/serial/generic.c
index e6833e2..c663369 100644
--- a/drivers/usb/serial/generic.c
+++ b/drivers/usb/serial/generic.c
@@ -288,6 +288,7 @@ int usb_serial_generic_write_room(struct tty_struct *tty)
 	dbg("%s - returns %d", __func__, room);
 	return room;
 }
+EXPORT_SYMBOL_GPL(usb_serial_generic_write_room);
 
 int usb_serial_generic_chars_in_buffer(struct tty_struct *tty)
 {
-- 
1.7.0.4


  reply	other threads:[~2010-10-23 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-23 18:43 [PATCH v2 0/2] Further cleanups to opticon driver Alon Ziv
2010-10-23 18:43 ` Alon Ziv [this message]
2010-10-25 11:20   ` [PATCH v2 1/2] Export usb_serial_generic_write_room for use in modules Johan Hovold
2010-10-25 19:57     ` Alon Ziv
2010-10-25 22:40       ` Johan Hovold
2010-10-23 18:43 ` [PATCH v2 2/2] opticon: use generic code where possible Alon Ziv
2010-10-25 11:11   ` Johan Hovold
2010-10-25 19:48     ` Alon Ziv
2010-11-11 16:23       ` Johan Hovold
2010-11-11 13:43 ` [PATCH v2 0/2] Further cleanups to opticon driver 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=1287859409-13810-2-git-send-email-alon-git@nolaviz.org \
    --to=alon+git@nolaviz.org \
    --cc=gregkh@suse.de \
    --cc=jhovold@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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

all inboxes | Powered by JetHome®