All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: [PATCH 05/12] nvmem: set nvmem->owner to nvmem->dev->driver->owner if unset
Date: Fri, 20 Oct 2017 15:52:46 +0200	[thread overview]
Message-ID: <20171020135246.GA20327@kroah.com> (raw)
In-Reply-To: <af26f3ad-bbb4-686a-f9dd-258e8d163345@linaro.org>

On Fri, Oct 20, 2017 at 02:44:51PM +0100, Srinivas Kandagatla wrote:
> 
> 
> On 20/10/17 14:38, Greg KH wrote:
> > On Mon, Oct 09, 2017 at 03:26:34PM +0200, srinivas.kandagatla@linaro.org wrote:
> > > From: Masahiro Yamada <yamada.masahiro@socionext.com>
> > > 
> > > All nvmem drivers are supposed to set the owner field of struct
> > > nvmem_config, but this matches nvmem->dev->driver->owner.
> > > 
> > > As far as I see in drivers/nvmem/ directory, all the drivers are
> > > the case.  So, make nvmem_register() set the nvmem's owner to the
> > > associated driver's owner unless nvmem_config sets otherwise.
> > > 
> > > Remove .owner settings in the drivers that are now redundant.
> > > 
> > > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > > Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > 
> > Patch does not apply :(
> > 
> Hmm.. I did base it on char-misc last time when I sent it..
> 
> Will rebase it and resend it!

Probably because I didn't take the previous patches in this series...

  reply	other threads:[~2017-10-20 13:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 13:26 [PATCH 00/12] nvmem: patches set-1 for v4.15 srinivas.kandagatla
2017-10-09 13:26 ` [PATCH 01/12] nvmem: imx-iim: use stack for nvmem_config instead of malloc'ing it srinivas.kandagatla
2017-10-20 13:32   ` Greg KH
2017-10-20 13:47     ` Masahiro Yamada
2017-10-20 13:54       ` Greg KH
2017-10-20 14:26         ` Masahiro Yamada
2017-10-20 14:47           ` Greg KH
2017-10-20 16:18             ` Masahiro Yamada
2017-10-20 16:26               ` Greg KH
2017-10-30 15:55                 ` Masahiro Yamada
2017-10-09 13:26 ` [PATCH 02/12] nvmem: mtk-efuse: " srinivas.kandagatla
2017-10-20 13:34   ` Greg KH
2017-10-20 13:47     ` Masahiro Yamada
2017-10-20 13:54       ` Greg KH
2017-10-20 13:59         ` Masahiro Yamada
2017-10-20 14:48           ` Greg KH
2017-10-09 13:26 ` [PATCH 03/12] nvmem: mtk-efuse: fix different address space warnings of sparse srinivas.kandagatla
2017-10-20 13:34   ` Greg KH
2017-10-20 13:55     ` Masahiro Yamada
2017-10-20 14:49       ` Greg KH
2017-10-20 16:08         ` Masahiro Yamada
2017-10-09 13:26 ` [PATCH 04/12] nvmem: qfprom: " srinivas.kandagatla
2017-10-20 13:34   ` Greg KH
2017-10-09 13:26 ` [PATCH 05/12] nvmem: set nvmem->owner to nvmem->dev->driver->owner if unset srinivas.kandagatla
2017-10-20 13:38   ` Greg KH
2017-10-20 13:44     ` Srinivas Kandagatla
2017-10-20 13:52       ` Greg KH [this message]
2017-10-09 13:26 ` [PATCH 06/12] nvmem: sunxi-sid: add support for A64/H5's SID controller srinivas.kandagatla
2017-10-20 13:36   ` Greg KH
2017-10-09 13:26 ` [PATCH 07/12] dt-bindings: nvmem: add description for UniPhier eFuse srinivas.kandagatla
2017-10-20 13:36   ` Greg KH
2017-10-09 13:26 ` [PATCH 08/12] nvmem: uniphier: add UniPhier eFuse driver srinivas.kandagatla
2017-10-20 13:37   ` Greg KH
2017-10-09 13:26 ` [PATCH 09/12] nvmem: rockchip: add support for RK3368 srinivas.kandagatla
2017-10-09 13:26 ` [PATCH 10/12] dt-bindings: nvmem: Describe the Amlogic Meson6/Meson8/Meson8b efuse srinivas.kandagatla
2017-10-12 20:52   ` Martin Blumenstingl
2017-10-09 13:26 ` [PATCH 11/12] nvmem: meson-efuse: indicate that this driver is only for Meson GX SoCs srinivas.kandagatla
2017-10-12 20:51   ` Martin Blumenstingl
2017-10-09 13:26 ` [PATCH 12/12] nvmem: add a driver for the Amlogic Meson6/Meson8/Meson8b SoCs srinivas.kandagatla

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=20171020135246.GA20327@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=yamada.masahiro@socionext.com \
    /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.