public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Frank Seidel <fseidel@suse.de>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	jirislaby@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nozomi: constify driver
Date: Fri, 1 Feb 2008 08:28:15 +0100	[thread overview]
Message-ID: <20080201072815.GA5345@uranus.ravnborg.org> (raw)
In-Reply-To: <200802010725.05421.fseidel@suse.de>

On Fri, Feb 01, 2008 at 07:25:05AM +0100, Frank Seidel wrote:
> On Thursday 31 January 2008 22:39, Jan Engelhardt wrote:
> > On Jan 31 2008 22:10, Frank Seidel wrote:
> > >(Re: [PATCH 012/196 ver2] nozomi driver) and is a rework
> > >of the nozomi constify patch from Jan Engelhardt.
> > 
> > It's hard to find what you actually reworked...
> 
> No, just use interdiff and its easy :-) .. and btw
> I didn't say i did a full rewrite ;-)
> 
> > >-static struct pci_device_id nozomi_pci_tbl[] = {
> > >+static const struct pci_device_id nozomi_pci_tbl[] __devinitdata = {
> > 
> > This is bogus.
> 
> In what way? First i tested this patch well (compiling and
> usage doesn't break a single thing) and second this (static
> const struct pci_device_id .. __devinitdata) can be found in many
> drivers.
> So, please explain why you think so.

__devinitdata is for non-const data.
__devinitconst is for const data.

You cannot mix const and non-const data in the same section,
if you do so gcc will complain.
It may build for you if all uses of __devinitdata in the
same source file is either const or non-const but when you
mix it then it breaks.

So please use the correct annotation.


> P.S.: btw this is the interdiff. Yes, its not big, but even
> then why not combine it with yours ;-)

We do small incremental steps whenever we can. The challenge is
often to split up patches and not to combine them.

Where we combine two patches this is when the second patch fix
a bug in the first patch.

	Sam

  reply	other threads:[~2008-02-01  7:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 21:10 [PATCH] nozomi: constify driver Frank Seidel
2008-01-31 21:39 ` Jan Engelhardt
2008-02-01  6:25   ` Frank Seidel
2008-02-01  7:28     ` Sam Ravnborg [this message]
2008-02-01  7:59       ` Frank Seidel
2008-02-01  8:09         ` [PATCH v2 0/3] nozomi: driver updates to current git tree Frank Seidel
2008-02-01  8:13           ` [PATCH v2 1/3] nozomi: minor cleanups (already in gregkh-2.6) Frank Seidel
2008-02-01  8:13           ` [PATCH v2 2/3] nozomi: constify driver Frank Seidel
2008-02-01  8:14           ` [PATCH v2 3/3] nozomi: finish constification Frank Seidel

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=20080201072815.GA5345@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=fseidel@suse.de \
    --cc=gregkh@suse.de \
    --cc=jengelh@computergmbh.de \
    --cc=jirislaby@gmail.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