From: Greg KH <gregkh@linuxfoundation.org>
To: John Garry <john.garry@huawei.com>
Cc: James Bottomley <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"saravanak@google.com" <saravanak@google.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1] driver core: Use list_del_init to replace list_del at device_links_purge()
Date: Tue, 14 Jan 2020 16:28:06 +0100 [thread overview]
Message-ID: <20200114152806.GA2043229@kroah.com> (raw)
In-Reply-To: <6820e1c4-07ab-0748-0bf3-e1c25c524a40@huawei.com>
On Tue, Jan 14, 2020 at 03:20:12PM +0000, John Garry wrote:
> On 14/01/2020 15:07, Greg KH wrote:
> > On Wed, Jan 08, 2020 at 05:04:20PM -0800, James Bottomley wrote:
> > > On Wed, 2020-01-08 at 17:10 +0000, John Garry wrote:
> > > > On 08/01/2020 16:08, John Garry wrote:
> > > > > On 08/01/2020 16:01, James Bottomley wrote:
> > > > > > > > > cdev->dev = NULL;
> > > > > > > > > return device_add(&cdev->cdev);
> > > > > > > > > }
> > > > > > > > > }
> > > > > > > > > return -ENODEV;
> > > > > > > > > }
> > > > > > > >
> > > > > > > > The design of the code is simply to remove the link to the
> > > > > > > > inserted device which has been removed.
> > > > > > > >
> > > > > > > > I*think* this means the calls to device_del and device_add
> > > > > > > > are unnecessary and should go. enclosure_remove_links and
> > > > > > > > the put of the enclosed device should be sufficient.
> > > > > > >
> > > > > > > That would make more sense than trying to "reuse" the device
> > > > > > > structure here by tearing it down and adding it back.
> > > > > >
> > > > > > OK, let's try that. This should be the patch if someone can try
> > > > > > it (I've compile tested it, but the enclosure system is under a
> > > > > > heap of stuff in the garage).
> > > > >
> > > > > I can test it now.
> > > > >
> > > >
> > > > Yeah, that looks to have worked ok. SES disk locate was also fine
> > > > after losing and rediscovering the disk.
> > >
> > > OK, I'll spin up a patch with fixes/reported and tested tags.
> >
> > Did this get sent? I can't seem to find it :(
> >
>
> Yeah, but you were not cc'ed :(
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20200114&id=529244bd1afc102ab164429d338d310d5d65e60d
Hey, less work for me, that's fine! :)
thanks for the poitner.
greg k-h
prev parent reply other threads:[~2020-01-14 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 11:34 [PATCH v1] driver core: Use list_del_init to replace list_del at device_links_purge() Luo Jiaxing
2020-01-08 11:53 ` John Garry
2020-01-08 12:26 ` Greg KH
2020-01-08 14:50 ` John Garry
2020-01-08 15:44 ` Greg KH
2020-01-08 15:51 ` James Bottomley
2020-01-08 15:57 ` Greg KH
2020-01-08 16:01 ` James Bottomley
2020-01-08 16:08 ` John Garry
2020-01-08 17:10 ` John Garry
2020-01-09 1:04 ` James Bottomley
2020-01-14 15:07 ` Greg KH
2020-01-14 15:20 ` John Garry
2020-01-14 15:28 ` Greg KH [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=20200114152806.GA2043229@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=saravanak@google.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