From: Peter Huewe <PeterHuewe@gmx.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Matheos Worku <Matheos.Worku@sun.com>, Alan Cox <alan@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] char/vme_scc: adding __init macro to vme_scc.c
Date: Tue, 22 Dec 2009 07:10:38 +0000 [thread overview]
Message-ID: <200912220810.38336.PeterHuewe@gmx.de> (raw)
In-Reply-To: <alpine.LSU.2.00.0910091704010.19284@wotan.suse.de>
Am Freitag 09 Oktober 2009 17:04:22 schrieb Jiri Kosina:
> On Thu, 20 Aug 2009, Matheos Worku wrote:
> > > Alan or Geert, please have a look at the small patch and either pull it
> > > through your tree, or please ack' it so Jiri can pull it through the
> > > trivial tree.
> > >
> > > linux version 2.6.31-rc6 - linus git tree, Do 20. Aug 22:26:06 CEST
> > > 2009
> > >
> > > Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> > > ---
> > > diff --git a/drivers/char/vme_scc.c b/drivers/char/vme_scc.c
> > > index 994e1a5..8b24729 100644
> > > --- a/drivers/char/vme_scc.c
> > > +++ b/drivers/char/vme_scc.c
> > > @@ -136,7 +136,7 @@ static const struct tty_port_operations
> > > scc_port_ops = { * vme_scc_init() and support functions
> > >
> > > *----------------------------------------------------------------------
> > >-----*/ -static int scc_init_drivers(void)
> > > +static int __init scc_init_drivers(void)
> > > {
> > > int error;
> > > @@ -172,7 +172,7 @@ static int scc_init_drivers(void)
> > > /* ports[] array is indexed by line no (i.e. [0] for ttyS0, [1] for
> > > ttyS1). */
> > > -static void scc_init_portstructs(void)
> > > +static void __init scc_init_portstructs(void)
> > > {
> > > struct scc_port *port;
> > > int i;
> > > @@ -195,7 +195,7 @@ static void scc_init_portstructs(void)
> > > #ifdef CONFIG_MVME147_SCC
> > > -static int mvme147_scc_init(void)
> > > +static int __init mvme147_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -298,7 +298,7 @@ fail:
> > > #ifdef CONFIG_MVME162_SCC
> > > -static int mvme162_scc_init(void)
> > > +static int __init mvme162_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -404,7 +404,7 @@ fail:
> > > #ifdef CONFIG_BVME6000_SCC
> > > -static int bvme6000_scc_init(void)
> > > +static int __init bvme6000_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -503,7 +503,7 @@ fail_free_b_rx:
> > > #endif
> > > -static int vme_scc_init(void)
> > > +static int __init vme_scc_init(void)
> > > {
> > > int res = -ENODEV;
> >
> > Then there are issnvram.txt iss.conf etc ... I guess we need to change
> > these as well. How about error messages? I assume they would have ISS in
> > them.
>
> Confused ... how is this related to the patch?
>
Hi,
any updates on this one? This patch floats around for quite a while now
(2009/08/20)
@Matheos: Can you perhaps clearify your remark/objection?
Thanks,
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Huewe <PeterHuewe@gmx.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Matheos Worku <Matheos.Worku@sun.com>, Alan Cox <alan@redhat.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] char/vme_scc: adding __init macro to vme_scc.c
Date: Tue, 22 Dec 2009 08:10:38 +0100 [thread overview]
Message-ID: <200912220810.38336.PeterHuewe@gmx.de> (raw)
In-Reply-To: <alpine.LSU.2.00.0910091704010.19284@wotan.suse.de>
Am Freitag 09 Oktober 2009 17:04:22 schrieb Jiri Kosina:
> On Thu, 20 Aug 2009, Matheos Worku wrote:
> > > Alan or Geert, please have a look at the small patch and either pull it
> > > through your tree, or please ack' it so Jiri can pull it through the
> > > trivial tree.
> > >
> > > linux version 2.6.31-rc6 - linus git tree, Do 20. Aug 22:26:06 CEST
> > > 2009
> > >
> > > Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> > > ---
> > > diff --git a/drivers/char/vme_scc.c b/drivers/char/vme_scc.c
> > > index 994e1a5..8b24729 100644
> > > --- a/drivers/char/vme_scc.c
> > > +++ b/drivers/char/vme_scc.c
> > > @@ -136,7 +136,7 @@ static const struct tty_port_operations
> > > scc_port_ops = { * vme_scc_init() and support functions
> > >
> > > *----------------------------------------------------------------------
> > >-----*/ -static int scc_init_drivers(void)
> > > +static int __init scc_init_drivers(void)
> > > {
> > > int error;
> > > @@ -172,7 +172,7 @@ static int scc_init_drivers(void)
> > > /* ports[] array is indexed by line no (i.e. [0] for ttyS0, [1] for
> > > ttyS1). */
> > > -static void scc_init_portstructs(void)
> > > +static void __init scc_init_portstructs(void)
> > > {
> > > struct scc_port *port;
> > > int i;
> > > @@ -195,7 +195,7 @@ static void scc_init_portstructs(void)
> > > #ifdef CONFIG_MVME147_SCC
> > > -static int mvme147_scc_init(void)
> > > +static int __init mvme147_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -298,7 +298,7 @@ fail:
> > > #ifdef CONFIG_MVME162_SCC
> > > -static int mvme162_scc_init(void)
> > > +static int __init mvme162_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -404,7 +404,7 @@ fail:
> > > #ifdef CONFIG_BVME6000_SCC
> > > -static int bvme6000_scc_init(void)
> > > +static int __init bvme6000_scc_init(void)
> > > {
> > > struct scc_port *port;
> > > int error;
> > > @@ -503,7 +503,7 @@ fail_free_b_rx:
> > > #endif
> > > -static int vme_scc_init(void)
> > > +static int __init vme_scc_init(void)
> > > {
> > > int res = -ENODEV;
> >
> > Then there are issnvram.txt iss.conf etc ... I guess we need to change
> > these as well. How about error messages? I assume they would have ISS in
> > them.
>
> Confused ... how is this related to the patch?
>
Hi,
any updates on this one? This patch floats around for quite a while now
(2009/08/20)
@Matheos: Can you perhaps clearify your remark/objection?
Thanks,
Peter
next prev parent reply other threads:[~2009-12-22 7:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 20:42 [PATCH] char/vme_scc: adding __init macro to vme_scc.c Peter Huewe
2009-08-20 20:42 ` Peter Huewe
2009-08-20 20:51 ` Matheos Worku
2009-08-20 20:51 ` Matheos Worku
2009-10-09 15:04 ` Jiri Kosina
2009-10-09 15:04 ` Jiri Kosina
2009-12-22 7:10 ` Peter Huewe [this message]
2009-12-22 7:10 ` Peter Huewe
2009-08-20 21:01 ` Peter Huewe
2009-08-20 21:01 ` Peter Huewe
2009-09-29 12:26 ` Peter Hüwe
2009-09-29 12:26 ` Peter Hüwe
2009-12-23 18:38 ` Geert Uytterhoeven
2009-12-23 18:38 ` Geert Uytterhoeven
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=200912220810.38336.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=Matheos.Worku@sun.com \
--cc=alan@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.