public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Nilsson <Jesper.Nilsson@axis.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Claudio Scordino <claudio@evidence.eu.com>,
	Mikael Starvik <mikael.starvik@axis.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Hinko Kocevar <hinko.kocevar@cetrtapot.si>,
	Janez Cufer <janez.cufer@cetrtapot.si>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	dev-etrax <dev-etrax@axis.com>
Subject: Re: [PATCH] Fix broken compilation of Cris serial driver
Date: Wed, 8 Apr 2009 16:00:04 +0200	[thread overview]
Message-ID: <20090408140003.GK8115@axis.com> (raw)
In-Reply-To: <20090408125122.GA2814@x200.localdomain>

On Wed, Apr 08, 2009 at 02:51:22PM +0200, Alexey Dobriyan wrote:
> On Wed, Apr 08, 2009 at 12:57:01PM +0200, Jesper Nilsson wrote:
> > On Wed, Apr 08, 2009 at 12:07:16PM +0200, Claudio Scordino wrote:
> > >     compilation of cris serial driver on 2.6.30-rc1 is broken since 
> > > commit number 0f043a81ebe84be3576667f04fdda481609e3816 removed the 
> > > read_proc field from the tty_driver structure.
> > > 
> > > The patch in attachment may fix the problem. Please check it very 
> > > carefully: I don't have hardware to make any test.
> 
> > > -	.read_proc = rs_read_proc,
> > >  	.tiocmget = rs_tiocmget,
> > >  	.tiocmset = rs_tiocmset
> > >  };
> > > @@ -4490,6 +4490,7 @@ rs_init(void)
> > >  	if (tty_register_driver(driver))
> > >  		panic("Couldn't register serial driver\n");
> > >  	/* do some initializing for the separate ports */
> > > +	driver->proc_entry->read_proc = rs_read_proc;
> > 
> > Is this the recommended way to convert proc handling?
> 
> No.

Ok, that's what I thought.

> > I find no other serial driver that does it this way...
> 
> ->read_proc effectively went away.

...so what do we use as a replacement, is it .proc_fops
or anything else?

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@axis.com

  reply	other threads:[~2009-04-08 14:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 10:07 [PATCH] Fix broken compilation of Cris serial driver Claudio Scordino
2009-04-08 10:12 ` Mikael Starvik
2009-04-08 10:45   ` Claudio Scordino
2009-04-08 10:57 ` Jesper Nilsson
2009-04-08 12:51   ` Alexey Dobriyan
2009-04-08 14:00     ` Jesper Nilsson [this message]
2009-04-08 15:52       ` Jesper Nilsson

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=20090408140003.GK8115@axis.com \
    --to=jesper.nilsson@axis.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=claudio@evidence.eu.com \
    --cc=dev-etrax@axis.com \
    --cc=hinko.kocevar@cetrtapot.si \
    --cc=janez.cufer@cetrtapot.si \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    /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