From: Keith Owens <kaos@ocs.com.au>
To: Dave Jones <davej@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: merge in progress.
Date: Mon, 31 Dec 2001 14:53:34 +1100 [thread overview]
Message-ID: <29543.1009770814@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 31 Dec 2001 03:15:06 -0000." <20011231031506.A1537@suse.de>
On Mon, 31 Dec 2001 03:15:06 +0000,
Dave Jones <davej@suse.de> wrote:
>Ok, pre5 gets us in sync with most of the important and easy
>to merge bits. Here's a list of whats left between the trees.
>
>Pending:
>o Bunch of __devexit changes
>o Keith's text.lock -> .subsection changes
> Better to merge this first and see whats left broken before merging
> the __devexit changes, in case there are any more bogus ones.
The __devexit_p changes are required in addition to .text.lock ->
.subsection, they are fixing different parts of the same problem. Most
of the devexit_p changes were in my patch against 2.4.17-pre6, all of
those changes are needed. The only devexit changes from 2.4.17-pre6 to
2.4.17 are :-
drivers/char/synclink.c
Spurious, there is no point in specifying __init, __exit etc. on the
declaration, those attributes only affect the function body. The
change has no effect. Anybody want to go through and remove spurious
__init, __exit etc. on forward function declarations?
drivers/pcmcia/i82092.c
Mine, valid AFAICT.
drivers/isdn/hisax/hisax_fcpcipnp.c
Don't know who changed it but it is valid. hisax_fcpcipnp was added
after my first patch against 2.4.16 and I missed the new driver when
I redid the devexit_p patch for 2.4.17.
I would add all the devexit_p changes through 2.4.17 at least, in
addition to the .text.lock changes.
next prev parent reply other threads:[~2001-12-31 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 3:15 Dave Jones
2001-12-31 3:53 ` Keith Owens [this message]
2001-12-31 12:19 ` Kai Germaschewski
2001-12-31 13:02 ` Dave Jones
2001-12-31 13:12 ` Alan Cox
2001-12-31 13:04 ` Jens Axboe
2001-12-31 13:21 ` Alan Cox
2001-12-31 13:17 ` Jens Axboe
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=29543.1009770814@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
Powered by JetHome