linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd-l0cyMroinI0@public.gmane.org>
To: Sebastian Reichel <sre-GFxCN5SEZAc@public.gmane.org>
Cc: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
	<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 0/2] Remove .owner from spi_drivers
Date: Wed, 28 Oct 2015 12:51:17 -0500	[thread overview]
Message-ID: <56310B15.3000103@ti.com> (raw)
In-Reply-To: <20151023182911.GA14674@earth>

On 10/23/2015 01:29 PM, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Oct 23, 2015 at 08:59:09AM -0500, Andrew F. Davis wrote:
>> This series adds a helper macro to the SPI core that assigns the owner
>> in spi_drivers so individual drivers do not have to do this, this is
>> similar to other subsystems like platform_driver and i2c_driver that
>> have made this change.
>
> Probably it makes sense to also update the related coccinelle
> script: scripts/coccinelle/api/platform_no_drv_owner.cocci
>
> -- Sebastian
>

Makes sense, patch submitted.

Thanks,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-10-28 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 13:59 [PATCH 0/2] Remove .owner from spi_drivers Andrew F. Davis
2015-10-23 13:59 ` [PATCH 1/2] spi: Add THIS_MODULE to spi_driver in SPI core Andrew F. Davis
2015-10-23 13:59 ` [PATCH 2/2] Drop owner assignment from spi_drivers Andrew F. Davis
     [not found] ` <1445608751-8432-1-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-10-23 18:29   ` [PATCH 0/2] Remove .owner " Sebastian Reichel
2015-10-28 17:51     ` Andrew F. Davis [this message]
2015-10-25 10:57   ` Jonathan Cameron

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=56310B15.3000103@ti.com \
    --to=afd-l0cymroini0@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sre-GFxCN5SEZAc@public.gmane.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).