From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vedang Patel <vedang.patel@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkp@01.org
Subject: Re: [lkp] [ASoC] 91c1832579: BUG: unable to handle kernel NULL pointer dereference
Date: Thu, 30 Jun 2016 20:55:16 +0800 [thread overview]
Message-ID: <20160630125516.GB8304@yexl-desktop> (raw)
In-Reply-To: <20160630122645.GZ6247@sirena.org.uk>
On Thu, Jun 30, 2016 at 01:26:45PM +0100, Mark Brown wrote:
>On Thu, Jun 30, 2016 at 09:57:39AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 91c1832579700891747820862633f9a8d0d81fa4 ("ASoC: Intel: Skylake: Increase loglevel of debug messages.")
>
>Please if you're sending mails like this send them to the patch authors
>as well.
Sorry, isn't Vedang Patel the patch author?
Thanks,
Xiaolong
next prev parent reply other threads:[~2016-06-30 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 1:57 kernel test robot
2016-06-30 12:26 ` Mark Brown
2016-06-30 12:55 ` Ye Xiaolong [this message]
2016-07-01 9:50 ` Mark Brown
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=20160630125516.GB8304@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
--cc=vedang.patel@intel.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
all inboxes | Powered by JetHome®