From: Denis Vlasenko <vda.linux@googlemail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: gregkh@suse.de, jeff@garzik.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [RFC,PATCHSET] Managed device resources
Date: Sat, 30 Dec 2006 22:31:48 +0100 [thread overview]
Message-ID: <200612302231.48510.vda.linux@googlemail.com> (raw)
In-Reply-To: <1167146313307-git-send-email-htejun@gmail.com>
On Tuesday 26 December 2006 16:18, Tejun Heo wrote:
> Hello, all.
>
> This patchset implements managed device resources, in short, devres.
I was working on a Linux device driver. Indeed, those error paths
are notoriously prone to bugs.
Patchset looks like good idea to me.
--
vda
next prev parent reply other threads:[~2006-12-30 21:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 15:18 [RFC,PATCHSET] Managed device resources Tejun Heo
2006-12-26 15:18 ` [PATCH 1/12] devres: device resource management core Tejun Heo
2006-12-26 15:18 ` [PATCH 2/12] devres: implement managed IO region interface Tejun Heo
2006-12-26 15:18 ` [PATCH 5/12] devres: implement managed PCI interface Tejun Heo
2006-12-26 15:18 ` [PATCH 8/12] libata: update libata core layer to use devres Tejun Heo
2006-12-26 15:18 ` [PATCH 3/12] devres: implement managed IRQ interface Tejun Heo
2006-12-26 15:18 ` [PATCH 7/12] libata: handle pci_enable_device() failure while resuming Tejun Heo
2006-12-26 15:18 ` [PATCH 4/12] devres: implement managed DMA interface Tejun Heo
2006-12-26 15:18 ` [PATCH 6/12] devres: implement managed iomap interface Tejun Heo
2006-12-26 15:18 ` [PATCH 10/12] libata: remove unused functions Tejun Heo
2006-12-26 15:18 ` [PATCH 11/12] devres: implement pcim_iomap_regions() Tejun Heo
2006-12-26 15:18 ` [PATCH 9/12] libata: update SATA LLDs to use devres Tejun Heo
2006-12-30 21:31 ` Denis Vlasenko [this message]
2007-01-04 22:19 ` [RFC,PATCHSET] Managed device resources Greg KH
2007-01-04 22:26 ` Jeff Garzik
2007-01-04 22:32 ` Greg KH
2007-01-08 4:07 ` Tejun Heo
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=200612302231.48510.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).