All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Michal Januszewski <spock@gentoo.org>,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: uvesafb: remove DRIVER_ATTR() usage
Date: Mon, 28 Aug 2017 14:41:49 +0000	[thread overview]
Message-ID: <20170828144149.GA28860@kroah.com> (raw)
In-Reply-To: <3613878.J9SAsAfrTp@amdc3058>

On Tue, Aug 01, 2017 at 03:36:01PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday, July 19, 2017 02:51:19 PM Greg KH wrote:
> > From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > It's better to be explicit and use the DRIVER_ATTR_RW() macro when
> > defining a driver's sysfs file.  Bonus is this fixes up a checkpatch.pl
> > warning.
> > 
> > This is part of a series to drop DRIVER_ATTR() from the tree entirely.
> > 
> > Cc: Michal Januszewski <spock@gentoo.org>
> > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> 
> I assume that this will go through your tree with other DRIVER_ATTR()
> removal patches (please ping me if you want me to merge this patch
> through fbdev tree).

I'll take it through mine, thanks.

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Michal Januszewski <spock@gentoo.org>,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fbdev: uvesafb: remove DRIVER_ATTR() usage
Date: Mon, 28 Aug 2017 16:41:49 +0200	[thread overview]
Message-ID: <20170828144149.GA28860@kroah.com> (raw)
In-Reply-To: <3613878.J9SAsAfrTp@amdc3058>

On Tue, Aug 01, 2017 at 03:36:01PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday, July 19, 2017 02:51:19 PM Greg KH wrote:
> > From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> > It's better to be explicit and use the DRIVER_ATTR_RW() macro when
> > defining a driver's sysfs file.  Bonus is this fixes up a checkpatch.pl
> > warning.
> > 
> > This is part of a series to drop DRIVER_ATTR() from the tree entirely.
> > 
> > Cc: Michal Januszewski <spock@gentoo.org>
> > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> 
> I assume that this will go through your tree with other DRIVER_ATTR()
> removal patches (please ping me if you want me to merge this patch
> through fbdev tree).

I'll take it through mine, thanks.

greg k-h

  reply	other threads:[~2017-08-28 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170719125131epcas5p4fed9dd550f3b19744e793831a9a2b1db@epcas5p4.samsung.com>
2017-07-19 12:51 ` [PATCH] fbdev: uvesafb: remove DRIVER_ATTR() usage Greg KH
2017-07-19 12:51   ` Greg KH
2017-08-01 13:36   ` Bartlomiej Zolnierkiewicz
2017-08-01 13:36     ` Bartlomiej Zolnierkiewicz
2017-08-28 14:41     ` Greg KH [this message]
2017-08-28 14:41       ` Greg KH

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=20170828144149.GA28860@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spock@gentoo.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 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.