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: Fri, 14 Oct 2016 09:58:33 +1300 [thread overview]
Message-ID: <1492262.TFAeDeKh1k@flyosflip> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1610121420410.1376-100000@iolanthe.rowland.org>
Hi!
I've branched the kernel package on the OpenSUSE Build Server, I'll=20
try to apply the patch there (this ought to be cleanest method).
Starting from the root of the kernel tarball, the patch should be=20
applied to drivers/pci/pci.c, am I right?
Cheers,
Pierre.
Le mercredi 12 octobre 2016, 14:23:35 NZDT Alan Stern a =C3=A9crit :
> On Wed, 12 Oct 2016, Pierre de Villemereuil wrote:
> > Hi!
> >=20
> > I'm sorry, I'm not savvy enough to know what to do with this (I=20
know
> > basics on how to code and compile, but I'm no dev). Could=20
someone
> > guide me through it?
> >=20
> > I gather this patch needs to be applied to some kernel module=20
code
> > which needs to be compiled and reloaded into my current kernel,
> > right?
>=20
> More likely you'll have to rebuild an entire new kernel, not just=20
a
> single module.
>=20
> Search the support site for the distribution you are using. It=20
ought
> to contain reasonably thorough instructions on how to build and=20
install
> your own version of their kernel.
>=20
> Once you know how to do all that, I can tell you how the patch=20
should
> be applied -- that's the easy part.
>=20
> Alan Stern
next prev parent reply other threads:[~2016-10-13 20:58 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 [this message]
2016-10-13 21:11 ` Alan Stern
2016-10-14 21:46 ` Pierre de Villemereuil
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=1492262.TFAeDeKh1k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox