public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dean Jenkins <Dean_Jenkins@mentor.com>
To: linux-kernel@vger.kernel.org
Subject: SLIP: Is there a maintainer for drivers/net/slip/slip.c ?
Date: Mon, 24 Jun 2013 09:27:06 +0100	[thread overview]
Message-ID: <51C802DA.4080202@mentor.com> (raw)

Hi,

Using the Linux v3.9 tag, I note that

./scripts/get_maintainer.pl -f drivers/net/slip/slip.c
netdev@vger.kernel.org (open list:NETWORKING DRIVERS)
linux-kernel@vger.kernel.org (open list)

There seems to be no maintainer for drivers/net/slip/slip.c, is that true ?

I am asking because sl_encaps() and slip_write_wakeup() do not handle 
error codes from tty->ops->write() and a recursive stack overflow crash 
can occur if the tty->ops->write() fails to write all the characters. I 
have some patches to fix this but would like some feedback on an 
appropriate solution.

Thanks,

Dean Jenkins
Mentor Graphics

             reply	other threads:[~2013-06-24  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  8:27 Dean Jenkins [this message]
2013-06-24  8:49 ` SLIP: Is there a maintainer for drivers/net/slip/slip.c ? Geert Uytterhoeven
2013-06-24 13:53 ` Peter Hurley
2013-06-24 14:06   ` Dean Jenkins

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=51C802DA.4080202@mentor.com \
    --to=dean_jenkins@mentor.com \
    --cc=linux-kernel@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