From: Danny Kukawka <dkukawka@suse.de>
To: Michael E Brown <Michael_E_Brown@dell.com>
Cc: Frank Seidel <fseidel@suse.de>,
linux-kernel@vger.kernel.org, Matt Domsch <Matt_Domsch@dell.com>,
Doug Warzecha <Douglas_Warzecha@dell.com>
Subject: Re: [PATCH][RFC] drivers/firmware/dcdbas: rework to get uevents
Date: Tue, 20 Nov 2007 21:23:35 +0100 [thread overview]
Message-ID: <200711202123.36112.dkukawka@suse.de> (raw)
In-Reply-To: <20071120193515.GA16195@humbolt.us.dell.com>
On Dienstag, 20. November 2007, Michael E Brown wrote:
> On Fri, Nov 16, 2007 at 11:53:53AM +0100, Frank Seidel wrote:
> > On Mittwoch 14 November 2007 19:32:01, you (Frank Seidel) wrote:
> > > Hi,
> > >
> > > this is a small trivial rework of the dcdbas driver so
> > > HAL can get uevents when platform devices are added or removed.
> >
> > Sorry for the noise! In the meantime i realized (thanks to a nice
> > colleague) this isn't really necessary anymore since patch
> > 43cc71eed1250755986da4c0f9898f9a635cb3bf is in mainline.
> >
> > If you'd anyway to add this patch i gues this is a better version
> > of it.
>
> Frank, Danny,
>
> Can you possibly explain a bit why this patch is necessary? Danny, does
> this fix the module load problems that you had detailed in your earlier
> email?
>
> If this is still necessary, then either Doug or Matt can queue it up for
> next kernel release.
AFAIK the patch Frank posted isn't needed anymore since this is commited to
mainline: 43cc71eed1250755986da4c0f9898f9a635cb3bf
Danny
--
Danny Kukawka
dkukawka@suse.de
Mobile Devices
SUSE LINUX a Novell Business
Maxfeldstr. 5, D-90409 Nuernberg, Germany
SUSE LINUX Products GmbH, Nuernberg; GF: Markus Rex, HRB 16746 (AG Nuernberg)
prev parent reply other threads:[~2007-11-20 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 18:32 [PATCH][RFC] drivers/firmware/dcdbas: rework to get uevents Frank Seidel
2007-11-16 10:53 ` Frank Seidel
[not found] ` <20071120193515.GA16195@humbolt.us.dell.com>
2007-11-20 20:23 ` Danny Kukawka [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=200711202123.36112.dkukawka@suse.de \
--to=dkukawka@suse.de \
--cc=Douglas_Warzecha@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=Michael_E_Brown@dell.com \
--cc=fseidel@suse.de \
--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