public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Milan Broz <mbroz@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: dm: sysfs add empty release function to avoid debug warning
Date: Mon, 21 Dec 2009 21:31:55 -0800	[thread overview]
Message-ID: <20091222053155.GA16888@kroah.com> (raw)
In-Reply-To: <4B2A518B.1030800@redhat.com>

On Thu, Dec 17, 2009 at 04:43:07PM +0100, Milan Broz wrote:
> On 12/17/2009 01:30 AM, Greg KH wrote:
> > On Wed, Dec 16, 2009 at 07:40:27PM +0100, Milan Broz wrote:
> >> On 12/16/2009 06:46 PM, Greg KH wrote:
> >>> You will find that all of these are modules, right?  That's being worked
> >>> on still.
> >>
> >> probably. I see that this implementation is in kernel since import to git...
> > 
> > And you will also note that I didn't paper over the issue by trying to
> > provide an empty release function :)
> 
> Alasdair, can we request revert of that last patch for now
> (which introduced the empty release function)?

Ping?  Any word on the revert?

thanks,

greg k-h

  reply	other threads:[~2009-12-22  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200912151735.nBFHZ8XP018683@hera.kernel.org>
2009-12-16  0:47 ` dm: sysfs add empty release function to avoid debug warning Greg KH
2009-12-16  9:44   ` Milan Broz
2009-12-16 13:45     ` Greg KH
2009-12-16 16:32       ` [dm-devel] " Zdenek Kabelac
2009-12-16 17:46         ` Greg KH
2009-12-16 18:40           ` Milan Broz
2009-12-17  0:30             ` Greg KH
2009-12-17 15:43               ` Milan Broz
2009-12-22  5:31                 ` Greg KH [this message]
2009-12-16 23:25           ` Zdenek Kabelac

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=20091222053155.GA16888@kroah.com \
    --to=greg@kroah.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=zkabelac@redhat.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