All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sam@ravnborg.org, jakub@redhat.com, jengelh@linux01.gwdg.de,
	daplas@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Section mismatches in drivers/video/console/promcon
Date: Tue, 05 Jun 2007 18:52:53 +0800	[thread overview]
Message-ID: <1181040773.5023.5.camel@daplas> (raw)
In-Reply-To: <20070604.235313.85409993.davem@davemloft.net>

On Mon, 2007-06-04 at 23:53 -0700, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Sat, 2 Jun 2007 21:16:46 +0200
> 
> > > 
> > > promcon_init() can be called again from visual_init() during
> > > vc_allocate().  So anything referenced by promcon_init() should not be
> > > marked __init.
> > > 
> > > Although, if you want to keep promfont_unitable and promfont_unicount
> > > __init, you can probably use con_copy_unimap() using the default vc as
> > > the source instead of doing a promcon_init_unimap() again.
> > 
> > Too involved for me to look into.
> > I cooked up following very minimal patch - if you agree can you then please
> > forward/take care of it.
> > 
> > 	Sam
> > 
> > Subject: video: fix section mismatch warning in promcon
> 
> I'll merge this fix in via the Sparc tree since this is a sparc
> console driver.
> 

I was about to send this patch to akpm, I'll leave this to you then.

Tony



      parent reply	other threads:[~2007-06-05 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 12:42 Section mismatches in drivers/video/console/promcon Sam Ravnborg
2007-06-02 12:58 ` Jan Engelhardt
2007-06-02 13:24 ` Antonino A. Daplas
2007-06-02 19:16   ` Sam Ravnborg
2007-06-05  6:53     ` David Miller
2007-06-05  8:05       ` Sam Ravnborg
2007-06-05 10:52       ` Antonino A. Daplas [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=1181040773.5023.5.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=daplas@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jakub@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.