LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Seth Jennings" <sjennings@variantweb.net>
To: sjennings@variantweb.net
Cc: Robert Jennings <rcj4747@gmail.com>,
	linuxppc-dev@lists.ozlabs.org, Dan Streetman <ddstreet@ieee.org>
Subject: Re: [PATCH] drivers/crypto/nx: prevent oops on module exit
Date: Fri, 17 Oct 2014 08:02:17 -0000	[thread overview]
Message-ID: <c5208e76ca917ccb0ca7c5fd5953cf21.squirrel@www.variantweb.net> (raw)
In-Reply-To: <f05dbb0844d1f0431532a186b56034f3.squirrel@www.variantweb.net>

>> On Fri, 2014-10-17 at 09:43 +1100, Michael Ellerman wrote:
>>> On Thu, 2014-10-16 at 15:30 -0400, Dan Streetman wrote:
>>> > Check old_devdata->dev in nx-842 driver before accessing it, as
>>> > on systems without any nx-842 hardware, the ->dev will never be
>>> > set.  Currently, the module will cause an oops during unload
>>> > since old_devdata->dev is null.
>>>
>>> Hi Dan,
>>>
>>> Patch looks reasonable. But I can't merge it, at least not without an
>>> ACK:
>>>
>>> $ ./scripts/get_maintainer.pl -f drivers/crypto/nx/
>>> Nathan Fontenot <nfont@linux.vnet.ibm.com> (supporter:IBM Power 842
>>> com...)
>>> Marcelo Henrique Cerri <mhcerri@linux.vnet.ibm.com> (supporter:IBM
>>> Power
>>> in-Nest...)
>>> Fionnuala Gunter <fin@linux.vnet.ibm.com> (supporter:IBM Power
>>> in-Nest...)
>>> Herbert Xu <herbert@gondor.apana.org.au> (maintainer:CRYPTO API)
>>> "David S. Miller" <davem@davemloft.net> (maintainer:CRYPTO API)
>>> linux-crypto@vger.kernel.org (open list:IBM Power in-Nest...)
>>> linux-kernel@vger.kernel.org (open list)
>>>
>>>
>>> If any of the above is out of date please send me a patch for
>>> MAINTAINERS.
>>
>> I think Dan now owns that driver, Dan, please confirm.
>
> I guess I'm not on the maintainer list anymore, as I shouldn't be
> since I don't work at IBM anymore.

Wow, I messed that up.  Repeating myself :-/  Sorry for the noise.

Seth

>
> So... yeah.  I was the original co-author of driver so I acked it
> but I'm not the maintainer anymore.  Which I shouldn't be, since
> I don't work at IBM anymore.
>
> Seth
>
>>
>> Cheers,
>> Ben.
>>
>>
>>
>
>

  reply	other threads:[~2014-10-17  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 19:30 [PATCH] drivers/crypto/nx: prevent oops on module exit Dan Streetman
2014-10-16 22:43 ` Michael Ellerman
2014-10-16 22:52   ` Benjamin Herrenschmidt
2014-10-17  7:59     ` Seth Jennings
2014-10-17  8:02       ` Seth Jennings [this message]
2014-10-17 22:05     ` Dan Streetman

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=c5208e76ca917ccb0ca7c5fd5953cf21.squirrel@www.variantweb.net \
    --to=sjennings@variantweb.net \
    --cc=ddstreet@ieee.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rcj4747@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox