From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC PATCH 1/2] drm: store connector name in connector struct
Date: Tue, 27 May 2014 09:18:21 +0300 [thread overview]
Message-ID: <87mwe3iw2a.fsf@intel.com> (raw)
In-Reply-To: <CAPM=9tx5ASc6vYttPZTNxm=cDuyRin8yi-+hGGsK-RtHJ=ZXbg@mail.gmail.com>
On Tue, 27 May 2014, Dave Airlie <airlied@gmail.com> wrote:
>> Reference: http://lkml.kernel.org/r/645ee6e22cad47d38a2b35c21c8d5fe3@DC1-MBX-01.ptsecurity.ru
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
>
>> @@ -834,9 +824,17 @@ int drm_connector_init(struct drm_device *dev,
>> ida_simple_get(connector_ida, 1, 0, GFP_KERNEL);
>> if (connector->connector_type_id < 0) {
>> ret = connector->connector_type_id;
>> - drm_mode_object_put(dev, &connector->base);
>> - goto out;
>> + goto out_out;
>
> ^^ one of these things is not like the other,
>
>
>> }
>> + connector->name =
>> + kasprintf(GFP_KERNEL, "%s-%d",
>> + drm_connector_enum_list[connector_type].name,
>> + connector->connector_type_id);
>> + if (!connector->name) {
>> + ret = -ENOMEM;
>> + goto out_put;
>
> ^^,
>
> I've merged this fixed into my tree, I'm sure Daniel won't mind :)
Thanks. I'll hide behind the "RFC PATCH" subject. ;)
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-27 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 13:58 [RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe Jani Nikula
2014-05-14 13:58 ` [RFC PATCH 1/2] drm: store connector name in connector struct Jani Nikula
2014-05-19 11:08 ` David Herrmann
2014-05-27 6:01 ` Dave Airlie
2014-05-27 6:18 ` Jani Nikula [this message]
2014-05-14 13:58 ` [RFC PATCH 2/2] drm: store encoder name in encoder struct Jani Nikula
2014-05-19 13:08 ` David Herrmann
2014-05-14 14:17 ` [RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe Chris Wilson
2014-05-14 15:59 ` Jani Nikula
2014-05-19 11:11 ` David Herrmann
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=87mwe3iw2a.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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