From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: lkp@lists.01.org
Subject: Re: [auxdisplay] 4edd70c133f: BUG: unable to handle kernel
Date: Mon, 24 Aug 2015 22:37:24 +0530 [thread overview]
Message-ID: <20150824170724.GA31019@sudip-pc> (raw)
In-Reply-To: <87oai2ed2m.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Thu, Aug 20, 2015 at 01:36:17PM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 4edd70c133f3921c594883d8f9da31a7261f8b4f ("auxdisplay: ks0108: use new parport device model")
Sorry for the delay in replying. It has already been fixed by:
92f26189b181 ("auxdisplay: ks0108: initialize local parport variable")
regards
sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kernel test robot <ying.huang@intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [lkp] [auxdisplay] 4edd70c133f: BUG: unable to handle kernel
Date: Mon, 24 Aug 2015 22:37:24 +0530 [thread overview]
Message-ID: <20150824170724.GA31019@sudip-pc> (raw)
In-Reply-To: <87oai2ed2m.fsf@yhuang-dev.intel.com>
On Thu, Aug 20, 2015 at 01:36:17PM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 4edd70c133f3921c594883d8f9da31a7261f8b4f ("auxdisplay: ks0108: use new parport device model")
Sorry for the delay in replying. It has already been fixed by:
92f26189b181 ("auxdisplay: ks0108: initialize local parport variable")
regards
sudip
next prev parent reply other threads:[~2015-08-24 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 5:36 [auxdisplay] 4edd70c133f: BUG: unable to handle kernel kernel test robot
2015-08-20 5:36 ` [lkp] " kernel test robot
2015-08-24 17:07 ` Sudip Mukherjee [this message]
2015-08-24 17:07 ` Sudip Mukherjee
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=20150824170724.GA31019@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=lkp@lists.01.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.