From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Nyman, Mathias" <mathias.nyman@intel.com>
Subject: Re: Kernel Debugging Support
Date: Mon, 4 Aug 2014 17:12:37 -0700 [thread overview]
Message-ID: <20140805001237.GA29701@xanatos> (raw)
In-Reply-To: <CAPDOMVjy9DzNVMg__MP7-0VAXYojDuGr6v+SoNfj3hhBKyHMYA@mail.gmail.com>
On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote:
> On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
> <Paul.Zimmerman@synopsys.com> wrote:
> >> From: Nick Krause [mailto:xerofoify@gmail.com]
[snip]
> >> Paul ,
> >> My computer is rather old now as of Sandy Bridge days, so I probably
> >> can't test the patch
> >> on my own machine. However I will look at the code and see if I can
> >> forward port it
> >> against the usb git tree I have a current version of. In addition I
> >> would like the new xhci
> >> maintainers information in order to send out a patch with the
> >> Maintainer for xhci updated.
> >
> > Sarah already told you who the new maintainer is, and then CCed him
> > on this thread. Hint: There is a file name 'MAINTAINERS' in the root
> > of the kernel tree, which tells you who the maintainers are for all of
> > the subsystems. Please read Documentation/SubmittingPatches, it has a
> > lot of information like this that you need to know.
> >
> > --
> > Paul
> >
> Thanks I will read this file and thanks for the information. I known
> where the file is I will
> add the information then.
You may be looking at an older version of MAINTAINERS. Mathias has only
been marked as the maintainer since 3.15. Which kernel version are you
working on?
Sarah Sharp
next prev parent reply other threads:[~2014-08-05 0:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 4:47 Kernel Debugging Support Nick Krause
2014-08-02 13:48 ` Alan Stern
2014-08-03 1:40 ` Nick Krause
2014-08-04 11:37 ` Austin S Hemmelgarn
2014-08-04 14:21 ` Alan Stern
2014-08-04 14:29 ` Austin S Hemmelgarn
2014-08-04 14:45 ` Richard Weinberger
2014-08-04 16:46 ` Sarah Sharp
2014-08-04 19:07 ` Paul Zimmerman
2014-08-04 19:23 ` Valdis.Kletnieks
2014-08-04 19:40 ` Paul Zimmerman
2014-08-04 20:27 ` Valdis.Kletnieks
2014-08-04 21:55 ` Paul Zimmerman
2014-08-04 22:49 ` Nick Krause
2014-08-04 23:03 ` Paul Zimmerman
2014-08-04 23:11 ` Nick Krause
2014-08-05 0:12 ` Sarah Sharp [this message]
2014-08-05 1:33 ` Nick Krause
2014-08-05 3:18 ` Nick Krause
2014-08-05 5:32 ` Nick Krause
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=20140805001237.GA29701@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=xerofoify@gmail.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).