mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Jiri Kosina <jikos@kernel.org>, Even Xu <even.xu@intel.com>,
	Zhang Lixu <lixu.zhang@intel.com>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dell.Client.Kernel@dell.com
Subject: Re: hid-sensor-hub 001F:8087:0AC2.0002: timeout waiting for response from ISHTP device
Date: Wed, 18 May 2022 11:48:34 -0700	[thread overview]
Message-ID: <41e7d536f72accbcbd2c782f1a5f18d0546098fb.camel@linux.intel.com> (raw)
In-Reply-To: <82e9a41c-552a-07e2-7caa-a14913cd34f4@molgen.mpg.de>

Hi Paul,

On Wed, 2022-05-18 at 20:06 +0200, Paul Menzel wrote:
> Dear Srinivas,
> 
> 
> Am 18.05.22 um 17:39 schrieb srinivas pandruvada:
> 
> > Attached a diff. Please use git apply and build kernel. And attach
> > dmesg. I want to see where did it fail.
> 
> As written, the device is used in production by a user, so I am not 
> sure, if I can get the device to test self-built Linux kernel images
> to 
> debug this issue. It would really be better to get access to such a 
> device from Dell or in some Intel lab.
> 
Let me try to get one.
You described some firmware version. Where did you see that? Do you
mean BIOS version?

Thanks,
Srinivas


> 
> Kind regards,
> 
> Paul


  reply	other threads:[~2022-05-18 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 15:01 Paul Menzel
2022-05-12 23:07 ` srinivas pandruvada
2022-05-18  4:07   ` Paul Menzel
2022-05-18 15:39     ` srinivas pandruvada
2022-05-18 18:06       ` Paul Menzel
2022-05-18 18:48         ` srinivas pandruvada [this message]
2022-05-18 19:55         ` srinivas pandruvada
2022-06-09 16:43           ` Paul Menzel

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=41e7d536f72accbcbd2c782f1a5f18d0546098fb.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=even.xu@intel.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu.zhang@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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®