From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Martin Belanger <nitram_67@hotmail.com>,
linux-nvme@lists.infradead.org, kbusch@kernel.org, hare@suse.de,
axboe@fb.com, sagi@grimberg.me, rafael@kernel.org,
charles_rose@dell.com, stuart_hayes@dell.com,
Martin Belanger <martin.belanger@dell.com>
Subject: Re: driver core patch, was Re: [PATCHv2 2/3] nvme: Add device_update_groups()
Date: Fri, 4 Feb 2022 08:45:43 +0100 [thread overview]
Message-ID: <YfzZp5KeuMUve99Q@kroah.com> (raw)
In-Reply-To: <20220204070441.GA28558@lst.de>
On Fri, Feb 04, 2022 at 08:04:41AM +0100, Christoph Hellwig wrote:
> On Thu, Feb 03, 2022 at 04:17:47PM -0500, Martin Belanger wrote:
> > From: Martin Belanger <martin.belanger@dell.com>
> >
> > This is used to update the sysfs groups after device objects are fully
> > initialized.
> >
> > Signed-off-by: Martin Belanger <martin.belanger@dell.com>
>
> This isn't a nvme patch, but a driver model one. Adjusting the subject
> to bring it to Gregs attention.
Thanks for that, now NAKed :)
next prev parent reply other threads:[~2022-02-04 7:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220203211748.27542-1-nitram_67@hotmail.com>
2022-02-03 21:17 ` [PATCHv2 1/3] nvme: send uevent on connection up Martin Belanger
2022-02-03 21:17 ` [PATCHv2 2/3] nvme: Add device_update_groups() Martin Belanger
2022-02-04 2:22 ` Chaitanya Kulkarni
2022-02-04 7:04 ` driver core patch, was " Christoph Hellwig
2022-02-04 7:45 ` Greg KH [this message]
2022-02-04 7:31 ` Hannes Reinecke
2022-02-04 7:42 ` Greg KH
2022-02-03 21:17 ` [PATCHv2 3/3] nvme: Expose cntrltype and dctype through sysfs Martin Belanger
2022-02-04 7:32 ` Hannes Reinecke
2022-02-04 7:43 ` Greg KH
2022-02-04 7:45 ` Greg KH
2022-02-04 13:51 ` Belanger, Martin
2022-02-04 14:05 ` Greg KH
2022-02-06 9:09 ` Sagi Grimberg
2022-02-06 12:02 ` Greg KH
2022-02-06 15:55 ` Sagi Grimberg
2022-02-06 8:54 ` Sagi Grimberg
2022-02-06 12:00 ` Greg KH
2022-02-06 13:08 ` Hannes Reinecke
2022-02-06 13:15 ` 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=YfzZp5KeuMUve99Q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@fb.com \
--cc=charles_rose@dell.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.belanger@dell.com \
--cc=nitram_67@hotmail.com \
--cc=rafael@kernel.org \
--cc=sagi@grimberg.me \
--cc=stuart_hayes@dell.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 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.