From: Greg KH <greg@kroah.com>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Andrew Morton <akpm@digeo.com>,
Patrick Mochel <mochel@digitalimplant.org>,
Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Suspend2 Merge: Driver model patches 2/2
Date: Thu, 16 Sep 2004 16:07:13 -0700 [thread overview]
Message-ID: <20040916230713.GA16403@kroah.com> (raw)
In-Reply-To: <1095374947.6537.34.camel@laptop.cunninghams>
On Fri, Sep 17, 2004 at 08:49:07AM +1000, Nigel Cunningham wrote:
> Hi.
>
> On Fri, 2004-09-17 at 08:35, Greg KH wrote:
> > > > Ick, no. I've been over this before with the fb people, and am not going
> > > > to accept this patch (nevermind that it's broken...) See the lkml
> > > > archives for more info on why I don't like this.
> > >
> > > Please excuse my ignorance but I don't see how it's broken
> >
> > This function, as written is very broken. I will not accept it. Not to
>
> What's broken? (I want to learn what I've done wrong that I'm not
> seeing).
- No locking when traversing the list.
- Reference count needs to be bumped before returning a pointer to the
object you found.
> > mention the fact that the functionality this function proposes to offer
> > is not needed either.
> >
> > > (their patch just fills in a field that was left blank previously),
> >
> > What patch?
>
> Attached. Sorry if I wrongly assumed this was the patch you're talking
> about.
Ah, no, I've never seen this one, thanks. But it looks sane, I don't
have a problem with it (sysfs will like it, it's not a suspend specific
patch at all.)
thanks,
greg k-h
next prev parent reply other threads:[~2004-09-16 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 10:58 Nigel Cunningham
2004-09-16 14:28 ` Greg KH
2004-09-16 22:18 ` Nigel Cunningham
2004-09-16 22:35 ` Greg KH
2004-09-16 22:49 ` Nigel Cunningham
2004-09-16 23:07 ` Greg KH [this message]
2004-09-16 23:19 ` Nigel Cunningham
2004-09-17 19:40 ` Pavel Machek
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=20040916230713.GA16403@kroah.com \
--to=greg@kroah.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
/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