linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	kbuild test robot <lkp@intel.com>,
	Chuah Kim Tatt <kim.tatt.chuah@intel.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
	vinod.koul@intel.com, heikki.krogerus@linux.intel.com,
	mika.westerberg@linux.intel.com, linux-kernel@vger.kernel.org,
	jui.nee.tan@intel.com
Subject: Re: [PATCH 2/2] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV
Date: Tue, 17 May 2016 11:14:40 -0700	[thread overview]
Message-ID: <573B5F90.2060802@hurleysoftware.com> (raw)
In-Reply-To: <1463138864.17131.330.camel@linux.intel.com>

On 05/13/2016 04:27 AM, Andy Shevchenko wrote:
> On Fri, 2016-05-13 at 18:15 +0800, kbuild test robot wrote:
>> Hi,
>>
>> [auto build test ERROR on next-20160513]
>> [cannot apply to tty/tty-testing usb/usb-testing v4.6-rc7 v4.6-rc6
>> v4.6-rc5 v4.6-rc7]
>> [if your patch is applied to the wrong git tree, please drop us a note
>> to help improving the system]
>>
>> url:    https://github.com/0day-ci/linux/commits/Chuah-Kim-Tatt/Fix-DN
>> V-HSUART-RX-DMA-timeout-interrupt-issue/20160513-162046
>> config: i386-randconfig-s0-201619 (attached as .config)
>> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
>> reproduce:
>>         # save the attached .config to linux build tree
>>         make ARCH=i386 
>>
>> Note: the linux-review/Chuah-Kim-Tatt/Fix-DNV-HSUART-RX-DMA-timeout-
>> interrupt-issue/20160513-162046 HEAD
>> 0354112aa9821bec8d278ad06b3d543724f5291d builds fine.
>>       It only hurts bisectibility.
>>
>> All errors (new ones prefixed by >>):
> 
> Peter, what happened to your DMA series in the linux-next? Did I miss
> any discussion related?

Sorry, I don't understand. What is the problem?

And where is this patch coming from? I didn't see it on linux-serial.

Regards,
Peter Hurley


>>>>
>>>> ERROR: "serial8250_rx_dma_flush"
>>>> [drivers/tty/serial/8250/8250_mid.ko] undefined!
>> ---
>> 0-DAY kernel test infrastructure                Open Source Technology
>> Center
>> https://lists.01.org/pipermail/kbuild-all                   Intel
>> Corporation
> 

      parent reply	other threads:[~2016-05-17 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  8:15 [PATCH 0/2] Fix DNV HSUART RX DMA timeout interrupt issue Chuah Kim Tatt
2016-05-13  8:15 ` [PATCH 1/2] dmaengine: hsu: Export hsu_dma_get_status() Chuah Kim Tatt
2016-05-13 11:19   ` Andy Shevchenko
2016-05-13  8:15 ` [PATCH 2/2] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV Chuah Kim Tatt
2016-05-13 10:15   ` kbuild test robot
2016-05-13 11:27     ` Andy Shevchenko
2016-05-16  5:29       ` Chuah, Kim Tatt
2016-05-20 12:40         ` Andy Shevchenko
2016-05-17 18:14       ` Peter Hurley [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=573B5F90.2060802@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jui.nee.tan@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kim.tatt.chuah@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).