mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcache: use default_groups in kobj_type
Date: Mon, 10 Jan 2022 23:53:10 +0800	[thread overview]
Message-ID: <97e5c59a-ac8e-ffee-b5d5-55883932b8df@suse.de> (raw)
In-Reply-To: <YdlL4YAScYp9XxkI@kroah.com>

On 1/8/22 4:31 PM, Greg Kroah-Hartman wrote:
> On Sat, Jan 08, 2022 at 02:16:28PM +0800, Coly Li wrote:
>> On 1/6/22 6:00 PM, Greg Kroah-Hartman wrote:
>>> There are currently 2 ways to create a set of sysfs files for a
>>> kobj_type, through the default_attrs field, and the default_groups
>>> field.  Move the bcache sysfs code to use default_groups field which has
>>> been the preferred way since aa30f47cf666 ("kobject: Add support for
>>> default attribute groups to kobj_type") so that we can soon get rid of
>>> the obsolete default_attrs field.
>>>
>>> Cc: Coly Li <colyli@suse.de>
>>> Cc: Kent Overstreet <kent.overstreet@gmail.com>
>>> Cc: linux-bcache@vger.kernel.org
>>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> It looks good to me.
>>
>> Acked-by: Coly Li <colyli@suse.de>
>>
>> I assume you may take this patch directly in your maintenance path, but if
>> you want me to take this, just let me know. Thanks.
> I can take it myself, or you can, which ever is easiest for you, just
> let me know which you prefer.  Thanks for the review!

It will be faster for this patch goes into mainline in your path, I am 
on vacation now and will have a latency...

Thank you.

Coly Li

      reply	other threads:[~2022-01-10 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 10:00 Greg Kroah-Hartman
2022-01-08  6:16 ` Coly Li
2022-01-08  8:31   ` Greg Kroah-Hartman
2022-01-10 15:53     ` Coly Li [this message]

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=97e5c59a-ac8e-ffee-b5d5-55883932b8df@suse.de \
    --to=colyli@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®