All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Prashant Shah <pshah.mumbai@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	whiteheadm@acm.org, Ryan Mallon <rmallon@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	mwhitehe@redhat.com, kernel-mentors@selenic.com
Subject: Re: [PATCH] Change request_irq() to use struct net_device *dev->name
Date: Sat, 27 Jul 2013 19:13:30 +0400	[thread overview]
Message-ID: <51F3E39A.2060203@cogentembedded.com> (raw)
In-Reply-To: <CAD6i1fKra9Z8C=jm-KYuWPwxd=u-8HMo8b=XJJOo8aS+4SdmWg@mail.gmail.com>

On 27-07-2013 12:58, Prashant Shah wrote:

>>>     It's also called managed device API. In fact, I've never heard it
>>> named devres API.

> If I understood it correctly it has to just calls
> devm_request_region() with the struct device pointer and there are no
> deallocation functions to call ? It manages deallocation on it own.

    Yes.

> Regards.

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Prashant Shah <pshah.mumbai@gmail.com>
Cc: kernel-mentors@selenic.com, Ryan Mallon <rmallon@gmail.com>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	netdev <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	whiteheadm@acm.org
Subject: Re: [PATCH] Change request_irq() to use struct net_device *dev->name
Date: Sat, 27 Jul 2013 19:13:30 +0400	[thread overview]
Message-ID: <51F3E39A.2060203@cogentembedded.com> (raw)
In-Reply-To: <CAD6i1fKra9Z8C=jm-KYuWPwxd=u-8HMo8b=XJJOo8aS+4SdmWg@mail.gmail.com>

On 27-07-2013 12:58, Prashant Shah wrote:

>>>     It's also called managed device API. In fact, I've never heard it
>>> named devres API.

> If I understood it correctly it has to just calls
> devm_request_region() with the struct device pointer and there are no
> deallocation functions to call ? It manages deallocation on it own.

    Yes.

> Regards.

WBR, Sergei

  reply	other threads:[~2013-07-27 15:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  6:09 [PATCH] Change request_irq() to use struct net_device *dev->name Prashant Shah
2013-07-24  6:09 ` Prashant Shah
2013-07-25  0:42 ` Ryan Mallon
2013-07-25  5:19   ` Prashant Shah
2013-07-25  5:19     ` Prashant Shah
2013-07-25  5:38     ` Prashant Shah
2013-07-25  5:38       ` Prashant Shah
2013-07-25 12:16       ` Andy Shevchenko
2013-07-25 15:20         ` tedheadster
2013-07-25 18:31           ` Andy Shevchenko
2013-07-25 18:33             ` Sergei Shtylyov
2013-07-25 18:38               ` Aaro Koskinen
2013-07-27  8:58                 ` Prashant Shah
2013-07-27  8:58                   ` Prashant Shah
2013-07-27 15:13                   ` Sergei Shtylyov [this message]
2013-07-27 15:13                     ` Sergei Shtylyov

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=51F3E39A.2060203@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=andy.shevchenko@gmail.com \
    --cc=kernel-mentors@selenic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwhitehe@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshah.mumbai@gmail.com \
    --cc=rmallon@gmail.com \
    --cc=whiteheadm@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.