All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre de Villemereuil <flyos@mailoo.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Lukas Wunner <lukas@wunner.de>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Oliver Neukum <oneukum@suse.com>,
	USB list <linux-usb@vger.kernel.org>,
	linux-pci@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: USB hot-plug not working (ASUS TP301UA-C4028T)
Date: Sat, 15 Oct 2016 10:46:44 +1300	[thread overview]
Message-ID: <18007487.pN64mJfts8@flyosflip> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1610131709160.1822-100000@iolanthe.rowland.org>

Hi!

I've managed to build the patched kernel on OBS, install the package=20
and boot! \o/

And I can confirm that the patch indeed fix the issue!

The kernel was booted without the usb.autosuspend=3D-1 option, of=20
course.

Thank you guys!

Cheers,
Pierre.

Le jeudi 13 octobre 2016, 17:11:46 NZDT Alan Stern a =C3=A9crit :
> On Fri, 14 Oct 2016, Pierre de Villemereuil wrote:
> > Hi!
> >=20
> > I've branched the kernel package on the OpenSUSE Build Server,=20
I'll
> > try to apply the patch there (this ought to be cleanest method).
> >=20
> > Starting from the root of the kernel tarball, the patch should=20
be
> > applied to drivers/pci/pci.c, am I right?
>=20
> You just cd to the top directory of the kernel source, and do
>=20
> 	patch -p1 <filename
>=20
> where "filename" is the contents of the email message containing=20
the
> patch.  Or if you want, since the patch is so small, you can=20
simply
> edit the file by hand to add in the new lines.
>=20
> Alan Stern

  reply	other threads:[~2016-10-14 21:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57F4B9C5.60600@linux.intel.com>
2016-10-05 14:45 ` USB hot-plug not working (ASUS TP301UA-C4028T) Alan Stern
2016-10-05 18:54   ` Bjorn Helgaas
2016-10-05 20:41     ` Lukas Wunner
2016-10-06  7:24       ` Oliver Neukum
2016-10-06 14:42       ` Alan Stern
2016-10-08 10:31         ` Lukas Wunner
2016-10-10 21:06           ` Pierre de Villemereuil
2016-10-11 15:18           ` Alan Stern
2016-10-11 20:27             ` Pierre de Villemereuil
2016-10-12 18:23               ` Alan Stern
2016-10-13 20:58                 ` Pierre de Villemereuil
2016-10-13 21:11                   ` Alan Stern
2016-10-14 21:46                     ` Pierre de Villemereuil [this message]
2016-10-20 10:01             ` Lukas Wunner
2016-10-20 13:57               ` Alan Stern

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=18007487.pN64mJfts8@flyosflip \
    --to=flyos@mailoo.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mathias.nyman@linux.intel.com \
    --cc=oneukum@suse.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stern@rowland.harvard.edu \
    /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.