All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Pratyush Anand <panand@redhat.com>
Cc: wim@iguana.be, dyoung@redhat.com, dzickus@redhat.com,
	linux-watchdog@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V5 1/2] watchdog: Use static struct class watchdog_class in stead of pointer
Date: Sat, 19 Dec 2015 08:21:17 -0800	[thread overview]
Message-ID: <567583FD.5070303@roeck-us.net> (raw)
In-Reply-To: <20151219042208.GH29413@dhcppc13.redhat.com>

On 12/18/2015 08:22 PM, Pratyush Anand wrote:
> On 17/12/2015:06:56:27 AM, Guenter Roeck wrote:
>> On 12/17/2015 04:23 AM, Pratyush Anand wrote:
>>> We need few sysfs attributes to know different status of a watchdog device.
>>> To do that, we need to associate .dev_groups with watchdog_class. So
>>> convert it from pointer to static.
>>> Putting this static struct in watchdog_dev.c, so that static device
>>> attributes defined in that file can be attached to it.
>>>
>>> Signed-off-by: Pratyush Anand <panand@redhat.com>
>>> Suggested-by: Guenter Roeck <linux@roeck-us.net>
>>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>>
>> As things evolve, I'd by now prefer to move the call to device_create()
>> into watchdog_dev.c, but that can wait for a follow-up patch if Wim
>> is ok with this series.
>
> Thanks for your quick review.
>
> OK. I will wait for Wim's comment and then may be I will send another
> version with your comment for patch 1/1 incorporated.
>

I reworked my patch to call device_create() from watchdog_dev.c on top of
your patches and on top of Wim's watchdog-next branch. Hopefully we can get
that into v4.5.

Guenter


  reply	other threads:[~2015-12-19 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:23 [PATCH V5 0/2] watchdog: Sysfs status read support Pratyush Anand
2015-12-17 12:23 ` [PATCH V5 1/2] watchdog: Use static struct class watchdog_class in stead of pointer Pratyush Anand
2015-12-17 14:56   ` Guenter Roeck
2015-12-19  4:22     ` Pratyush Anand
2015-12-19 16:21       ` Guenter Roeck [this message]
2015-12-21 15:52       ` Guenter Roeck
2015-12-21 16:13         ` Pratyush Anand
2015-12-17 12:23 ` [PATCH V5 2/2] watchdog: Read device status through sysfs attributes Pratyush Anand
2015-12-17 12:23   ` Pratyush Anand
2015-12-17 14:53   ` Guenter Roeck
2015-12-27 16:57 ` [PATCH V5 0/2] watchdog: Sysfs status read support Wim Van Sebroeck
2015-12-28  4:14   ` Pratyush Anand

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=567583FD.5070303@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dyoung@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=panand@redhat.com \
    --cc=wim@iguana.be \
    /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.