All of lore.kernel.org
 help / color / mirror / Atom feed
* [ljones-mfd:for-mfd-next 56/66] drivers/mfd/mfd-core.c:216:11: error: implicit declaration of function 'mfd_match_of_node_to_dev'
@ 2020-07-17 21:22 kernel test robot
  2020-07-22 18:03 ` Adding branches for testing Lee Jones
  0 siblings, 1 reply; 14+ messages in thread
From: kernel test robot @ 2020-07-17 21:22 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 6435 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
head:   89e2fd3e750d33c697eff97a2c6804b735d1beb7
commit: 765f4122aee73587b62ad1c4e093d6d1d2468d75 [56/66] mfd: core: Make a best effort attempt to match devices with the correct of_nodes
config: x86_64-randconfig-a011-20200717 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ed6b578040a85977026c93bf4188f996148f3218)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install x86_64 cross compiling tool for clang build
        # apt-get install binutils-x86-64-linux-gnu
        git checkout 765f4122aee73587b62ad1c4e093d6d1d2468d75
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/mfd/mfd-core.c:216:11: error: implicit declaration of function 'mfd_match_of_node_to_dev' [-Werror,-Wimplicit-function-declaration]
                                   ret = mfd_match_of_node_to_dev(pdev, np, cell);
                                         ^
   1 error generated.

vim +/mfd_match_of_node_to_dev +216 drivers/mfd/mfd-core.c

   169	
   170	static int mfd_add_device(struct device *parent, int id,
   171				  const struct mfd_cell *cell,
   172				  struct resource *mem_base,
   173				  int irq_base, struct irq_domain *domain)
   174	{
   175		struct resource *res;
   176		struct platform_device *pdev;
   177		struct device_node *np = NULL;
   178		struct mfd_of_node_entry *of_entry, *tmp;
   179		int ret = -ENOMEM;
   180		int platform_id;
   181		int r;
   182	
   183		if (id == PLATFORM_DEVID_AUTO)
   184			platform_id = id;
   185		else
   186			platform_id = id + cell->id;
   187	
   188		pdev = platform_device_alloc(cell->name, platform_id);
   189		if (!pdev)
   190			goto fail_alloc;
   191	
   192		pdev->mfd_cell = kmemdup(cell, sizeof(*cell), GFP_KERNEL);
   193		if (!pdev->mfd_cell)
   194			goto fail_device;
   195	
   196		res = kcalloc(cell->num_resources, sizeof(*res), GFP_KERNEL);
   197		if (!res)
   198			goto fail_device;
   199	
   200		pdev->dev.parent = parent;
   201		pdev->dev.type = &mfd_dev_type;
   202		pdev->dev.dma_mask = parent->dma_mask;
   203		pdev->dev.dma_parms = parent->dma_parms;
   204		pdev->dev.coherent_dma_mask = parent->coherent_dma_mask;
   205	
   206		ret = regulator_bulk_register_supply_alias(
   207				&pdev->dev, cell->parent_supplies,
   208				parent, cell->parent_supplies,
   209				cell->num_parent_supplies);
   210		if (ret < 0)
   211			goto fail_res;
   212	
   213		if (IS_ENABLED(CONFIG_OF) && parent->of_node && cell->of_compatible) {
   214			for_each_child_of_node(parent->of_node, np) {
   215				if (of_device_is_compatible(np, cell->of_compatible)) {
 > 216					ret = mfd_match_of_node_to_dev(pdev, np, cell);
   217					if (ret == -EAGAIN)
   218						continue;
   219					if (ret)
   220						goto fail_alias;
   221	
   222					break;
   223				}
   224			}
   225	
   226			if (!pdev->dev.of_node)
   227				pr_warn("%s: Failed to locate of_node [id: %d]\n",
   228					cell->name, platform_id);
   229		}
   230	
   231		mfd_acpi_add_device(cell, pdev);
   232	
   233		if (cell->pdata_size) {
   234			ret = platform_device_add_data(pdev,
   235						cell->platform_data, cell->pdata_size);
   236			if (ret)
   237				goto fail_of_entry;
   238		}
   239	
   240		if (cell->properties) {
   241			ret = platform_device_add_properties(pdev, cell->properties);
   242			if (ret)
   243				goto fail_of_entry;
   244		}
   245	
   246		for (r = 0; r < cell->num_resources; r++) {
   247			res[r].name = cell->resources[r].name;
   248			res[r].flags = cell->resources[r].flags;
   249	
   250			/* Find out base to use */
   251			if ((cell->resources[r].flags & IORESOURCE_MEM) && mem_base) {
   252				res[r].parent = mem_base;
   253				res[r].start = mem_base->start +
   254					cell->resources[r].start;
   255				res[r].end = mem_base->start +
   256					cell->resources[r].end;
   257			} else if (cell->resources[r].flags & IORESOURCE_IRQ) {
   258				if (domain) {
   259					/* Unable to create mappings for IRQ ranges. */
   260					WARN_ON(cell->resources[r].start !=
   261						cell->resources[r].end);
   262					res[r].start = res[r].end = irq_create_mapping(
   263						domain, cell->resources[r].start);
   264				} else {
   265					res[r].start = irq_base +
   266						cell->resources[r].start;
   267					res[r].end   = irq_base +
   268						cell->resources[r].end;
   269				}
   270			} else {
   271				res[r].parent = cell->resources[r].parent;
   272				res[r].start = cell->resources[r].start;
   273				res[r].end   = cell->resources[r].end;
   274			}
   275	
   276			if (!cell->ignore_resource_conflicts) {
   277				if (has_acpi_companion(&pdev->dev)) {
   278					ret = acpi_check_resource_conflict(&res[r]);
   279					if (ret)
   280						goto fail_of_entry;
   281				}
   282			}
   283		}
   284	
   285		ret = platform_device_add_resources(pdev, res, cell->num_resources);
   286		if (ret)
   287			goto fail_of_entry;
   288	
   289		ret = platform_device_add(pdev);
   290		if (ret)
   291			goto fail_of_entry;
   292	
   293		if (cell->pm_runtime_no_callbacks)
   294			pm_runtime_no_callbacks(&pdev->dev);
   295	
   296		kfree(res);
   297	
   298		return 0;
   299	
   300	fail_of_entry:
   301		list_for_each_entry_safe(of_entry, tmp, &mfd_of_node_list, list)
   302			if (of_entry->dev == &pdev->dev) {
   303				list_del(&of_entry->list);
   304				kfree(of_entry);
   305			}
   306	fail_alias:
   307		regulator_bulk_unregister_supply_alias(&pdev->dev,
   308						       cell->parent_supplies,
   309						       cell->num_parent_supplies);
   310	fail_res:
   311		kfree(res);
   312	fail_device:
   313		platform_device_put(pdev);
   314	fail_alloc:
   315		return ret;
   316	}
   317	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 26112 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Adding branches for testing
  2020-07-17 21:22 [ljones-mfd:for-mfd-next 56/66] drivers/mfd/mfd-core.c:216:11: error: implicit declaration of function 'mfd_match_of_node_to_dev' kernel test robot
@ 2020-07-22 18:03 ` Lee Jones
  0 siblings, 0 replies; 14+ messages in thread
From: Lee Jones @ 2020-07-22 18:03 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

Good evening,

Is it possible to obtain build-test results for successful builds?

If so, what is the process for adding branches to your system?

Thanks in advance.

Kind regards,
Lee

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
       [not found] <20200723035548.GA363815@ubuntu-n2-xlarge-x86>
@ 2020-07-23  6:32 ` Lee Jones
  2020-07-23  6:38   ` Rong Chen
  0 siblings, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-23  6:32 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On Wed, 22 Jul 2020, Nathan Chancellor wrote:

> Hi Lee,
> 
> On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > Good evening,
> > 
> > Is it possible to obtain build-test results for successful builds?
> > 
> > If so, what is the process for adding branches to your system?
> > 
> > Thanks in advance.
> > 
> > Kind regards,
> > Lee
> > 
> 
> I filed a pull request against their repository and I get email
> notifications whenever I push to a new branch on my repository:
> 
> https://github.com/intel/lkp-tests/pull/64

Of course it's on GitHub! :)

There was me thinking it was secret source.

> Looks like there are a lot of trees to look over in case you want to
> customize it in some way, I am not sure of any documentation over it
> though:

Docs:

  https://github.com/intel/lkp-tests
  https://github.com/intel/lkp-tests/wiki

> https://github.com/intel/lkp-tests/tree/master/repo/linux

You've been a great help Nathan.  Thank you!

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  6:32 ` Lee Jones
@ 2020-07-23  6:38   ` Rong Chen
  2020-07-23  6:46     ` Lee Jones
  2020-07-23  7:27     ` Lee Jones
  0 siblings, 2 replies; 14+ messages in thread
From: Rong Chen @ 2020-07-23  6:38 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]



On 7/23/20 2:32 PM, Lee Jones wrote:
> On Wed, 22 Jul 2020, Nathan Chancellor wrote:
>
>> Hi Lee,
>>
>> On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
>>> Good evening,
>>>
>>> Is it possible to obtain build-test results for successful builds?
>>>
>>> If so, what is the process for adding branches to your system?
>>>
>>> Thanks in advance.
>>>
>>> Kind regards,
>>> Lee
>>>
>> I filed a pull request against their repository and I get email
>> notifications whenever I push to a new branch on my repository:
>>
>> https://github.com/intel/lkp-tests/pull/64
> Of course it's on GitHub! :)
>
> There was me thinking it was secret source.
>
>> Looks like there are a lot of trees to look over in case you want to
>> customize it in some way, I am not sure of any documentation over it
>> though:
> Docs:
>
>    https://github.com/intel/lkp-tests
>    https://github.com/intel/lkp-tests/wiki
>
>> https://github.com/intel/lkp-tests/tree/master/repo/linux
> You've been a great help Nathan.  Thank you!
>

Hi Lee, Nathan,

We have updated the config file for repo/linux/ljones-mfd: 
https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
and there is a introduce document for these items: 
https://github.com/intel/lkp-tests/wiki/Repo-Spec

Best Regards,
Rong Chen

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  6:38   ` Rong Chen
@ 2020-07-23  6:46     ` Lee Jones
  2020-07-23  7:58       ` Rong Chen
  2020-07-23  7:27     ` Lee Jones
  1 sibling, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-23  6:46 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

On Thu, 23 Jul 2020, Rong Chen wrote:

> 
> 
> On 7/23/20 2:32 PM, Lee Jones wrote:
> > On Wed, 22 Jul 2020, Nathan Chancellor wrote:
> > 
> > > Hi Lee,
> > > 
> > > On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > > > Good evening,
> > > > 
> > > > Is it possible to obtain build-test results for successful builds?
> > > > 
> > > > If so, what is the process for adding branches to your system?
> > > > 
> > > > Thanks in advance.
> > > > 
> > > > Kind regards,
> > > > Lee
> > > > 
> > > I filed a pull request against their repository and I get email
> > > notifications whenever I push to a new branch on my repository:
> > > 
> > > https://github.com/intel/lkp-tests/pull/64
> > Of course it's on GitHub! :)
> > 
> > There was me thinking it was secret source.
> > 
> > > Looks like there are a lot of trees to look over in case you want to
> > > customize it in some way, I am not sure of any documentation over it
> > > though:
> > Docs:
> > 
> >    https://github.com/intel/lkp-tests
> >    https://github.com/intel/lkp-tests/wiki
> > 
> > > https://github.com/intel/lkp-tests/tree/master/repo/linux
> > You've been a great help Nathan.  Thank you!
> > 
> 
> Hi Lee, Nathan,
> 
> We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0

I was just doing that.  Thank you, you've saved me some time.

Would you also be kind enough to do the same for 'backlight' please?

Or would you like me to do that myself?

> and there is a introduce document for these items:
> https://github.com/intel/lkp-tests/wiki/Repo-Spec

Thanks.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  6:38   ` Rong Chen
  2020-07-23  6:46     ` Lee Jones
@ 2020-07-23  7:27     ` Lee Jones
  2020-07-23  7:57       ` Rong Chen
  1 sibling, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-23  7:27 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]

On Thu, 23 Jul 2020, Rong Chen wrote:

> 
> 
> On 7/23/20 2:32 PM, Lee Jones wrote:
> > On Wed, 22 Jul 2020, Nathan Chancellor wrote:
> > 
> > > Hi Lee,
> > > 
> > > On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > > > Good evening,
> > > > 
> > > > Is it possible to obtain build-test results for successful builds?
> > > > 
> > > > If so, what is the process for adding branches to your system?
> > > > 
> > > > Thanks in advance.
> > > > 
> > > > Kind regards,
> > > > Lee
> > > > 
> > > I filed a pull request against their repository and I get email
> > > notifications whenever I push to a new branch on my repository:
> > > 
> > > https://github.com/intel/lkp-tests/pull/64
> > Of course it's on GitHub! :)
> > 
> > There was me thinking it was secret source.
> > 
> > > Looks like there are a lot of trees to look over in case you want to
> > > customize it in some way, I am not sure of any documentation over it
> > > though:
> > Docs:
> > 
> >    https://github.com/intel/lkp-tests
> >    https://github.com/intel/lkp-tests/wiki
> > 
> > > https://github.com/intel/lkp-tests/tree/master/repo/linux
> > You've been a great help Nathan.  Thank you!
> > 
> 
> Hi Lee, Nathan,
> 
> We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
> and there is a introduce document for these items:

> https://github.com/intel/lkp-tests/wiki/Repo-Spec

Would you be kind enough to expand on a couple of points for me
please?  The Repo-Spec seems to be lacking in a couple of areas.

What are 'integration_testing_branches'?  Will lkp-tests only operate
on those branches and exclude all others (except those mentioned in
'whitelist_branch' of course).

What are 'subsystems'?  If the MFD case, these do not appears to be
directories.  Do they pertain to something else, regex for instance?

Any help would be gratefully received.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  7:27     ` Lee Jones
@ 2020-07-23  7:57       ` Rong Chen
  2020-07-23  8:09         ` Lee Jones
  0 siblings, 1 reply; 14+ messages in thread
From: Rong Chen @ 2020-07-23  7:57 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]



On 7/23/20 3:27 PM, Lee Jones wrote:
> On Thu, 23 Jul 2020, Rong Chen wrote:
>
>>
>> On 7/23/20 2:32 PM, Lee Jones wrote:
>>> On Wed, 22 Jul 2020, Nathan Chancellor wrote:
>>>
>>>> Hi Lee,
>>>>
>>>> On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
>>>>> Good evening,
>>>>>
>>>>> Is it possible to obtain build-test results for successful builds?
>>>>>
>>>>> If so, what is the process for adding branches to your system?
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Kind regards,
>>>>> Lee
>>>>>
>>>> I filed a pull request against their repository and I get email
>>>> notifications whenever I push to a new branch on my repository:
>>>>
>>>> https://github.com/intel/lkp-tests/pull/64
>>> Of course it's on GitHub! :)
>>>
>>> There was me thinking it was secret source.
>>>
>>>> Looks like there are a lot of trees to look over in case you want to
>>>> customize it in some way, I am not sure of any documentation over it
>>>> though:
>>> Docs:
>>>
>>>     https://github.com/intel/lkp-tests
>>>     https://github.com/intel/lkp-tests/wiki
>>>
>>>> https://github.com/intel/lkp-tests/tree/master/repo/linux
>>> You've been a great help Nathan.  Thank you!
>>>
>> Hi Lee, Nathan,
>>
>> We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
>> and there is a introduce document for these items:
>> https://github.com/intel/lkp-tests/wiki/Repo-Spec
> Would you be kind enough to expand on a couple of points for me
> please?  The Repo-Spec seems to be lacking in a couple of areas.
>
> What are 'integration_testing_branches'?  Will lkp-tests only operate
> on those branches and exclude all others (except those mentioned in
> 'whitelist_branch' of course).

Hi Lee,

the branches of integration_testing_branches are from linux-next tree,
'integration_testing_branches' means 0day will try to apply lkml patches 
to these branches to test.

$ git show linux-next/master:Next/Trees | grep lee/mfd
mfd-fixes       git 
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-fixes
mfd             git 
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-next

>
> What are 'subsystems'?  If the MFD case, these do not appears to be
> directories.  Do they pertain to something else, regex for instance?

'subsystems' is generated from linus/master:MAINTAINERS, 0day use it to compare with the patch subject from lkml,
and sort the branches that the patch may want to be applied to.

Best Regards,
Rong Chen


>
> Any help would be gratefully received.
>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  6:46     ` Lee Jones
@ 2020-07-23  7:58       ` Rong Chen
  2020-07-23  8:08         ` Lee Jones
  0 siblings, 1 reply; 14+ messages in thread
From: Rong Chen @ 2020-07-23  7:58 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]



On 7/23/20 2:46 PM, Lee Jones wrote:
> On Thu, 23 Jul 2020, Rong Chen wrote:
>
>>
>> On 7/23/20 2:32 PM, Lee Jones wrote:
>>> On Wed, 22 Jul 2020, Nathan Chancellor wrote:
>>>
>>>> Hi Lee,
>>>>
>>>> On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
>>>>> Good evening,
>>>>>
>>>>> Is it possible to obtain build-test results for successful builds?
>>>>>
>>>>> If so, what is the process for adding branches to your system?
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Kind regards,
>>>>> Lee
>>>>>
>>>> I filed a pull request against their repository and I get email
>>>> notifications whenever I push to a new branch on my repository:
>>>>
>>>> https://github.com/intel/lkp-tests/pull/64
>>> Of course it's on GitHub! :)
>>>
>>> There was me thinking it was secret source.
>>>
>>>> Looks like there are a lot of trees to look over in case you want to
>>>> customize it in some way, I am not sure of any documentation over it
>>>> though:
>>> Docs:
>>>
>>>     https://github.com/intel/lkp-tests
>>>     https://github.com/intel/lkp-tests/wiki
>>>
>>>> https://github.com/intel/lkp-tests/tree/master/repo/linux
>>> You've been a great help Nathan.  Thank you!
>>>
>> Hi Lee, Nathan,
>>
>> We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
> I was just doing that.  Thank you, you've saved me some time.
>
> Would you also be kind enough to do the same for 'backlight' please?

Hi Lee,

We have updated it: 
https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243

Best Regards,
Rong Chen


>
> Or would you like me to do that myself?
>
>> and there is a introduce document for these items:
>> https://github.com/intel/lkp-tests/wiki/Repo-Spec
> Thanks.
>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  7:58       ` Rong Chen
@ 2020-07-23  8:08         ` Lee Jones
  2020-07-28  9:25           ` Lee Jones
  0 siblings, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-23  8:08 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 2238 bytes --]

On Thu, 23 Jul 2020, Rong Chen wrote:

> 
> 
> On 7/23/20 2:46 PM, Lee Jones wrote:
> > On Thu, 23 Jul 2020, Rong Chen wrote:
> > 
> > > 
> > > On 7/23/20 2:32 PM, Lee Jones wrote:
> > > > On Wed, 22 Jul 2020, Nathan Chancellor wrote:
> > > > 
> > > > > Hi Lee,
> > > > > 
> > > > > On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > > > > > Good evening,
> > > > > > 
> > > > > > Is it possible to obtain build-test results for successful builds?
> > > > > > 
> > > > > > If so, what is the process for adding branches to your system?
> > > > > > 
> > > > > > Thanks in advance.
> > > > > > 
> > > > > > Kind regards,
> > > > > > Lee
> > > > > > 
> > > > > I filed a pull request against their repository and I get email
> > > > > notifications whenever I push to a new branch on my repository:
> > > > > 
> > > > > https://github.com/intel/lkp-tests/pull/64
> > > > Of course it's on GitHub! :)
> > > > 
> > > > There was me thinking it was secret source.
> > > > 
> > > > > Looks like there are a lot of trees to look over in case you want to
> > > > > customize it in some way, I am not sure of any documentation over it
> > > > > though:
> > > > Docs:
> > > > 
> > > >     https://github.com/intel/lkp-tests
> > > >     https://github.com/intel/lkp-tests/wiki
> > > > 
> > > > > https://github.com/intel/lkp-tests/tree/master/repo/linux
> > > > You've been a great help Nathan.  Thank you!
> > > > 
> > > Hi Lee, Nathan,
> > > 
> > > We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
> > I was just doing that.  Thank you, you've saved me some time.
> > 
> > Would you also be kind enough to do the same for 'backlight' please?
> 
> Hi Lee,
> 
> We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243

Excellent.  You are a star, thank you.

I have added one more repo:

  https://github.com/intel/lkp-tests/pull/73

Please see to it at your convenience.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  7:57       ` Rong Chen
@ 2020-07-23  8:09         ` Lee Jones
  0 siblings, 0 replies; 14+ messages in thread
From: Lee Jones @ 2020-07-23  8:09 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 3139 bytes --]

On Thu, 23 Jul 2020, Rong Chen wrote:

> 
> 
> On 7/23/20 3:27 PM, Lee Jones wrote:
> > On Thu, 23 Jul 2020, Rong Chen wrote:
> > 
> > > 
> > > On 7/23/20 2:32 PM, Lee Jones wrote:
> > > > On Wed, 22 Jul 2020, Nathan Chancellor wrote:
> > > > 
> > > > > Hi Lee,
> > > > > 
> > > > > On Wed, Jul 22, 2020 at 07:03:19PM +0100, Lee Jones wrote:
> > > > > > Good evening,
> > > > > > 
> > > > > > Is it possible to obtain build-test results for successful builds?
> > > > > > 
> > > > > > If so, what is the process for adding branches to your system?
> > > > > > 
> > > > > > Thanks in advance.
> > > > > > 
> > > > > > Kind regards,
> > > > > > Lee
> > > > > > 
> > > > > I filed a pull request against their repository and I get email
> > > > > notifications whenever I push to a new branch on my repository:
> > > > > 
> > > > > https://github.com/intel/lkp-tests/pull/64
> > > > Of course it's on GitHub! :)
> > > > 
> > > > There was me thinking it was secret source.
> > > > 
> > > > > Looks like there are a lot of trees to look over in case you want to
> > > > > customize it in some way, I am not sure of any documentation over it
> > > > > though:
> > > > Docs:
> > > > 
> > > >     https://github.com/intel/lkp-tests
> > > >     https://github.com/intel/lkp-tests/wiki
> > > > 
> > > > > https://github.com/intel/lkp-tests/tree/master/repo/linux
> > > > You've been a great help Nathan.  Thank you!
> > > > 
> > > Hi Lee, Nathan,
> > > 
> > > We have updated the config file for repo/linux/ljones-mfd: https://github.com/intel/lkp-tests/commit/deff2b285b141ac462b3a7091566ce2ea218c9f0
> > > and there is a introduce document for these items:
> > > https://github.com/intel/lkp-tests/wiki/Repo-Spec
> > Would you be kind enough to expand on a couple of points for me
> > please?  The Repo-Spec seems to be lacking in a couple of areas.
> > 
> > What are 'integration_testing_branches'?  Will lkp-tests only operate
> > on those branches and exclude all others (except those mentioned in
> > 'whitelist_branch' of course).
> 
> Hi Lee,
> 
> the branches of integration_testing_branches are from linux-next tree,
> 'integration_testing_branches' means 0day will try to apply lkml patches to
> these branches to test.
> 
> $ git show linux-next/master:Next/Trees | grep lee/mfd
> mfd-fixes       git
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-fixes
> mfd             git
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git#for-mfd-next
> 
> > 
> > What are 'subsystems'?  If the MFD case, these do not appears to be
> > directories.  Do they pertain to something else, regex for instance?
> 
> 'subsystems' is generated from linus/master:MAINTAINERS, 0day use it to compare with the patch subject from lkml,
> and sort the branches that the patch may want to be applied to.

Okay, that makes sense.

Thank you for taking the time to explain.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-23  8:08         ` Lee Jones
@ 2020-07-28  9:25           ` Lee Jones
  2020-07-29  9:09             ` Rong Chen
  0 siblings, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-28  9:25 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

> > We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243
> 
> Excellent.  You are a star, thank you.
> 
> I have added one more repo:
> 
>   https://github.com/intel/lkp-tests/pull/73
> 
> Please see to it at your convenience.

Any idea why I am not receiving results for the following please?

  https://github.com/intel/lkp-tests/blob/master/repo/linux/lee-linaro

As far as I'm aware, LKP should be testing all branches.

What am I missing?  Did I do something wrong in the config?

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-28  9:25           ` Lee Jones
@ 2020-07-29  9:09             ` Rong Chen
  2020-07-29 10:13               ` Lee Jones
  0 siblings, 1 reply; 14+ messages in thread
From: Rong Chen @ 2020-07-29  9:09 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]



On 7/28/20 5:25 PM, Lee Jones wrote:
>>> We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243
>> Excellent.  You are a star, thank you.
>>
>> I have added one more repo:
>>
>>    https://github.com/intel/lkp-tests/pull/73
>>
>> Please see to it at your convenience.
> Any idea why I am not receiving results for the following please?
>
>    https://github.com/intel/lkp-tests/blob/master/repo/linux/lee-linaro
>
> As far as I'm aware, LKP should be testing all branches.
>
> What am I missing?  Did I do something wrong in the config?
>

Hi Lee,

It's a network problem, the bot can't clone the repo successfully,
I'm downloading it but it still very slow.

$ git clone https://git.linaro.org/people/lee.jones/linux.git lee-linaro
Cloning into bare repository 'lee-linaro'...
remote: Enumerating objects: 884266, done.
remote: Counting objects: 100% (884266/884266), done.
remote: Compressing objects: 100% (14993/14993), done.
Receiving objects:   3% (99547/2967293), 42.67 MiB | 32.00 KiB/s

Best Regards,
Rong Chen

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-29  9:09             ` Rong Chen
@ 2020-07-29 10:13               ` Lee Jones
  2020-07-30  1:21                 ` Rong Chen
  0 siblings, 1 reply; 14+ messages in thread
From: Lee Jones @ 2020-07-29 10:13 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

On Wed, 29 Jul 2020, Rong Chen wrote:

> 
> 
> On 7/28/20 5:25 PM, Lee Jones wrote:
> > > > We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243
> > > Excellent.  You are a star, thank you.
> > > 
> > > I have added one more repo:
> > > 
> > >    https://github.com/intel/lkp-tests/pull/73
> > > 
> > > Please see to it at your convenience.
> > Any idea why I am not receiving results for the following please?
> > 
> >    https://github.com/intel/lkp-tests/blob/master/repo/linux/lee-linaro
> > 
> > As far as I'm aware, LKP should be testing all branches.
> > 
> > What am I missing?  Did I do something wrong in the config?
> > 
> 
> Hi Lee,
> 
> It's a network problem, the bot can't clone the repo successfully,
> I'm downloading it but it still very slow.
> 
> $ git clone https://git.linaro.org/people/lee.jones/linux.git lee-linaro
> Cloning into bare repository 'lee-linaro'...
> remote: Enumerating objects: 884266, done.
> remote: Counting objects: 100% (884266/884266), done.
> remote: Compressing objects: 100% (14993/14993), done.
> Receiving objects:   3% (99547/2967293), 42.67 MiB | 32.00 KiB/s

Thanks for looking into this.

I guess that this will only need to be done once, right?

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Adding branches for testing
  2020-07-29 10:13               ` Lee Jones
@ 2020-07-30  1:21                 ` Rong Chen
  0 siblings, 0 replies; 14+ messages in thread
From: Rong Chen @ 2020-07-30  1:21 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]



On 7/29/20 6:13 PM, Lee Jones wrote:
> On Wed, 29 Jul 2020, Rong Chen wrote:
>
>>
>> On 7/28/20 5:25 PM, Lee Jones wrote:
>>>>> We have updated it: https://github.com/intel/lkp-tests/commit/c0286b0f24d04bf11f83e253df7e237a49858243
>>>> Excellent.  You are a star, thank you.
>>>>
>>>> I have added one more repo:
>>>>
>>>>     https://github.com/intel/lkp-tests/pull/73
>>>>
>>>> Please see to it at your convenience.
>>> Any idea why I am not receiving results for the following please?
>>>
>>>     https://github.com/intel/lkp-tests/blob/master/repo/linux/lee-linaro
>>>
>>> As far as I'm aware, LKP should be testing all branches.
>>>
>>> What am I missing?  Did I do something wrong in the config?
>>>
>> Hi Lee,
>>
>> It's a network problem, the bot can't clone the repo successfully,
>> I'm downloading it but it still very slow.
>>
>> $ git clone https://git.linaro.org/people/lee.jones/linux.git lee-linaro
>> Cloning into bare repository 'lee-linaro'...
>> remote: Enumerating objects: 884266, done.
>> remote: Counting objects: 100% (884266/884266), done.
>> remote: Compressing objects: 100% (14993/14993), done.
>> Receiving objects:   3% (99547/2967293), 42.67 MiB | 32.00 KiB/s
> Thanks for looking into this.
>
> I guess that this will only need to be done once, right?
>

yes, and lee-linaro repo is ready, tests have been started.


Best Regards,
Rong Chen

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2020-07-30  1:21 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-17 21:22 [ljones-mfd:for-mfd-next 56/66] drivers/mfd/mfd-core.c:216:11: error: implicit declaration of function 'mfd_match_of_node_to_dev' kernel test robot
2020-07-22 18:03 ` Adding branches for testing Lee Jones
     [not found] <20200723035548.GA363815@ubuntu-n2-xlarge-x86>
2020-07-23  6:32 ` Lee Jones
2020-07-23  6:38   ` Rong Chen
2020-07-23  6:46     ` Lee Jones
2020-07-23  7:58       ` Rong Chen
2020-07-23  8:08         ` Lee Jones
2020-07-28  9:25           ` Lee Jones
2020-07-29  9:09             ` Rong Chen
2020-07-29 10:13               ` Lee Jones
2020-07-30  1:21                 ` Rong Chen
2020-07-23  7:27     ` Lee Jones
2020-07-23  7:57       ` Rong Chen
2020-07-23  8:09         ` Lee Jones

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.