mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.3-rc1
Date: Sat, 7 Feb 2004 02:56:38 +0000	[thread overview]
Message-ID: <20040207025638.GW21151@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0402061823040.30672@home.osdl.org>

On Fri, Feb 06, 2004 at 06:28:13PM -0800, Linus Torvalds wrote:
> 
> Ok, this is another big merge of a number of pending patches, although to 
> some degree the patches have now moved "outwards" from the core, and most 
> of them are in driver land.
> 
> There's a lot of network driver updates (have been in -mm and Jeff's 
> testing trees for a while), and Al Viro has been fixing up not just 
> network drivers, but also cursing over parport interfaces ;)
> 
> Andrew's patches are all over, from fixing warnings with new versions of
> gcc to merging things like the ppc updates he had in his tree, and 
> everything in between.
> 
> On and a big ALSA update, along with SCSI updates (big qla update, for
> example).
> 
> So let's calm down and make sure all the updates are ok.

One note: please, please, let's put a moratorium on sysfs-related patches
that didn't go through review.  We are just getting netdev situation in
the main tree under control.  It took nearly half a year (if not more).
And now we've got *exact* *copy* of the change that had started that mess -
this time in fbdev.  Sure, there's fewer fbdev drivers, so it shouldn't
take that long.  But then it's not 2.5 anymore...

If you are doing any sysfs integration - *fix* *lifetime* *rules* *first*.
You can do that in a way that will avoid breakage or need to revisit the
drivers when kobjects get embedded - just have your my_subsystem_release()
defined as kfree() and on the last step replace its body with kobject_put(),
moving the actual freeing into ->release().

Even if you are sure that you can fix all drivers in one go, there's no
need to turn the entire series into "must merge at once" monster - if nothing
else, reordering it that way will make testing easier.  Sigh...

  reply	other threads:[~2004-02-07  2:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07  2:28 Linus Torvalds
2004-02-07  2:56 ` viro [this message]
2004-02-07 17:21   ` Kevin O'Connor
2004-02-07 19:20     ` Greg KH
2004-02-07  3:11 ` Måns Rullgård
2004-02-07  5:26   ` Greg KH
2004-02-07 10:24 ` Andre Tomt
2004-02-07 16:22   ` Bartlomiej Zolnierkiewicz
2004-02-08  6:02     ` Andre Tomt
2004-02-08  6:29       ` Andre Tomt
2004-02-08 21:34       ` Bartlomiej Zolnierkiewicz
2004-02-08 21:55         ` Andre Tomt
2004-02-08 22:51           ` Bartlomiej Zolnierkiewicz
2004-02-09  0:08             ` Andre Tomt
2004-02-09  1:34               ` Bartlomiej Zolnierkiewicz
2004-02-09  2:40                 ` Andre Tomt
2004-02-09 12:41                   ` Arkadiusz Miskiewicz
2004-02-09 14:41                     ` Bartlomiej Zolnierkiewicz
2004-02-09 13:01                   ` Bartlomiej Zolnierkiewicz
2004-02-09  1:53           ` Disassembling with gdb (Re: Linux 2.6.3-rc1) Matthew Reppert
2004-02-08 15:18 ` Linux 2.6.3-rc1 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=20040207025638.GW21151@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®