linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Rong Chen <rong.a.chen@intel.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	<alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	<linux-kernel@vger.kernel.org>, Takashi Iwai <tiwai@suse.com>,
	Jaroslav Kysela <perex@perex.cz>, Mark Brown <broonie@kernel.org>,
	<kbuild-all@01.org>
Subject: Re: [kbuild-all] [PATCH] fix odd_ptr_err.cocci warnings
Date: Tue, 20 Aug 2019 13:54:41 +0300	[thread overview]
Message-ID: <c3779fa2-3aab-3ba2-518d-9675591787af@ti.com> (raw)
In-Reply-To: <297e44a8-e08d-ddf2-e5e8-b532965b4a8d@intel.com>

Hi Chen,

On 20/08/2019 11.41, Rong Chen wrote:
> Hi Peter,
> 
> We have updated to only send the reports to you, please see
> https://github.com/intel/lkp-tests/blob/master/repo/linux/omap-audio

Thank you very much!

> 
> Best Regards,
> Rong Chen
> 
> On 8/9/19 9:21 PM, Julia Lawall wrote:
>>
>> On Fri, 9 Aug 2019, Peter Ujfalusi wrote:
>>
>>>
>>> On 09/08/2019 15.31, Mark Brown wrote:
>>>> On Fri, Aug 09, 2019 at 12:30:46PM +0200, Julia Lawall wrote:
>>>>
>>>>> tree:   https://github.com/omap-audio/linux-audio
>>>>> peter/ti-linux-4.19.y/wip
>>>>> head:   62c9c1442c8f61ca93e62e1a9d8318be0abd9d9a
>>>>> commit: 62c9c1442c8f61ca93e62e1a9d8318be0abd9d9a [34/34] j721e new
>>>>> machine driver wip
>>>>> :::::: branch date: 20 hours ago
>>>>> :::::: commit date: 20 hours ago
>>>>>
>>>>>   j721e-evm.c |    4 ++--
>>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>
>>>>> --- a/sound/soc/ti/j721e-evm.c
>>>>> +++ b/sound/soc/ti/j721e-evm.c
>>>>> @@ -283,7 +283,7 @@ static int j721e_get_clocks(struct platf
>>>> This file isn't upstream, it's only in the TI BSP.
>>> Yes, it is not upstream, but the fix is valid.
>>>
>>> Julia: is it possible to direct these notifications only to me from
>>> https://github.com/omap-audio/linux-audio.git ?
>>>
>>> It mostly carries TI BSP stuff and my various for upstream branches
>>> nowdays.
>> Please discuss it with the kbuild people.  They should be able to set it
>> up as you want.
>>
>> You can try lkp@intel.com
>>
>> julia
>> _______________________________________________
>> kbuild-all mailing list
>> kbuild-all@lists.01.org
>> https://lists.01.org/mailman/listinfo/kbuild-all
> 

- Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

      reply	other threads:[~2019-08-20 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 10:30 [PATCH] fix odd_ptr_err.cocci warnings Julia Lawall
2019-08-09 12:31 ` Mark Brown
2019-08-09 13:14   ` Peter Ujfalusi
2019-08-09 13:21     ` Julia Lawall
2019-08-20  8:41       ` [kbuild-all] " Rong Chen
2019-08-20 10:54         ` Peter Ujfalusi [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=c3779fa2-3aab-3ba2-518d-9675591787af@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=julia.lawall@lip6.fr \
    --cc=kbuild-all@01.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rong.a.chen@intel.com \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).