mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Tee <justintee8345@gmail.com>
To: "Ewan D. Milne" <emilne@redhat.com>, linux-kernel@vger.kernel.org
Cc: "paul.ely@broadcom.com" <paul.ely@broadcom.com>
Subject: Re: [PATCH] drivers: base: Remove statistics group if encryption group not created
Date: Mon, 8 Jun 2026 14:11:09 -0700	[thread overview]
Message-ID: <85cb68a6-7bfe-468d-b19a-5e9ff573501b@gmail.com> (raw)
In-Reply-To: <20260519191840.1030912-1-emilne@redhat.com>

Hi Ewan,

Thanks for bringing this to attention.  So, I have two comments:

1.) In the err_del_statistics label, should we check for if 
(tcont->statistics) and only then sysfs_remove_group(&classdev->kobj, 
tcont->statistics) could be called?

err_del_statistics:
         if (tcont->statistics)
                 sysfs_remove_group(&classdev->kobj, tcont->statistics);

2.) In general, if the tcont->encryption sysfs group couldn’t be 
created, why would we remove the tcont->statistics sysfs group? The 
tcont->statistics and tcont->encryption are independent of each other.  
Just because the tcont->encryption sysfs group couldn’t be created 
shouldn’t mean that we need to remove the tcont->statistics sysfs group 
too.  And, clean up of the tcont->statistics sysfs group is not lost.  
When transport_remove_classdev is called, the tcont->statistics sysfs 
group is cleaned up at that time.

Regards,
Justin

  reply	other threads:[~2026-06-08 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 19:18 Ewan D. Milne
2026-06-08 21:11 ` Justin Tee [this message]
2026-06-09 17:33   ` Ewan Milne
2026-06-10 23:40     ` Justin Tee

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=85cb68a6-7bfe-468d-b19a-5e9ff573501b@gmail.com \
    --to=justintee8345@gmail.com \
    --cc=emilne@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.ely@broadcom.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

all inboxes | Powered by JetHome®