From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Christoph Hellwig <hch@infradead.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Dave Young <dyoung@redhat.com>,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] drivers/base: introduce some help routines for reordering a group of dev
Date: Mon, 25 Jun 2018 14:41:10 +0800 [thread overview]
Message-ID: <20180625064110.GA4233@kroah.com> (raw)
In-Reply-To: <1529904187-18673-2-git-send-email-kernelfans@gmail.com>
On Mon, Jun 25, 2018 at 01:23:05PM +0800, Pingfan Liu wrote:
> This patch introduce some help routines used by next patch. It aims to
> ease reviewing, while the next patch will concentrate on algorithm.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Grygorii Strashko <grygorii.strashko@ti.com>
> Cc: Christoph Hellwig <hch@infradead.org>
> Cc: Bjorn Helgaas <helgaas@kernel.org>
> Cc: Dave Young <dyoung@redhat.com>
> Cc: linux-pci@vger.kernel.org
> Cc: linuxppc-dev@lists.ozlabs.org
> Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
> ---
> drivers/base/core.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/drivers/base/core.c b/drivers/base/core.c
> index 36622b5..8113d2c 100644
> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -123,6 +123,44 @@ static int device_is_dependent(struct device *dev, void *target)
> return ret;
> }
>
> +struct pos_info {
> + struct device *pos;
> + struct device *tail;
> +};
> +
> +/* caller takes the devices_kset->list_lock */
> +static int descendants_reorder_after_pos(struct device *dev,
> + void *data)
> +{
> + struct device *pos;
> + struct pos_info *p = data;
> +
> + pos = p->pos;
> + pr_debug("devices_kset: Moving %s after %s\n",
> + dev_name(dev), dev_name(pos));
> + device_for_each_child(dev, p, descendants_reorder_after_pos);
> + /* children at the tail */
> + list_move(&dev->kobj.entry, &pos->kobj.entry);
> + /* record the right boundary of the section */
> + if (p->tail == NULL)
> + p->tail = dev;
> + return 0;
> +}
> +
> +/* iterate over an open section */
> +#define list_opensect_for_each_reverse(cur, left, right) \
> + for (cur = right->prev; cur == left; cur = cur->prev)
> +
> +static bool is_consumer(struct device *query, struct device *supplier)
> +{
> + struct device_link *link;
> + /* todo, lock protection */
> + list_for_each_entry(link, &supplier->links.consumers, s_node)
> + if (link->consumer == query)
> + return true;
> + return false;
> +}
You are adding code that no one uses yet, making this impossible to
review as I don't know what to expect. I shouldn't have to read the
second patch and have to flip back and forth to try to figure it out :(
sorry, please break this series up in a better way to make it simpler to
review.
greg k-h
next prev parent reply other threads:[~2018-06-25 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 5:23 [PATCH 0/3] drivers/base: bugfix for supplier<-consumer ordering in device_kset Pingfan Liu
2018-06-25 5:23 ` [PATCH 1/3] drivers/base: introduce some help routines for reordering a group of dev Pingfan Liu
2018-06-25 6:41 ` Greg Kroah-Hartman [this message]
2018-06-25 7:08 ` Pingfan Liu
2018-06-25 5:23 ` [PATCH 2/3] drivers/base: reorder consumer and its children behind suppliers Pingfan Liu
2018-06-26 7:44 ` Dan Carpenter
2018-06-27 2:34 ` Pingfan Liu
2018-06-27 8:34 ` Dan Carpenter
2018-06-28 13:47 ` Pingfan Liu
2018-06-25 5:23 ` [PATCH 3/3] drivers/base: only reordering consumer device when probing Pingfan Liu
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=20180625064110.GA4233@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dyoung@redhat.com \
--cc=grygorii.strashko@ti.com \
--cc=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.