From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: /drivers/staging/TODO doc and kernel tasks question
Date: Thu, 23 Oct 2014 11:18:16 +0800 [thread overview]
Message-ID: <20141023031816.GA14228@kroah.com> (raw)
In-Reply-To: <CAFGHVq01d15wBGcYjmARa9jhgrXmd7P-g4SvP-qEFBSrn-vOUw@mail.gmail.com>
On Wed, Oct 22, 2014 at 10:05:30PM -0500, Jaime Arrocha wrote:
> Good day,
>
> The TODO document has the addresses of where to send a patch, but if
> you run get_maintainer.pl it gives me a different person to address
> it, gregkh for example.
if you don't cc: me, the patch will not get merged, it's that simple :)
> I have sent a patch to the persons on the TODO list, should I still
> copy to the maintainer in charge too? CC maybe?
Yes, and the mailing list as well please. Trust get_maintainer.pl, it
works properly.
> Another question, apart from the /drivers/staging and bugtracker, is
> there some where else to look for bug info? The mailing list? I just
> want to get the complete picture.
bugzilla.kernel.org doesn't show much of anything for staging drivers,
what specifically are you looking for?
> Last question, I understand that if there is a bug, most of the time
> they tell you to try to reproduce it on the latest kernel. If it
> doesn't occur then everything is good and I should look for another
> one. But who is in charge of porting a bug fix like these to old
> kernels? How can I help? Or I, as a newbie, should focus more on the
> /drivers/staging and bugtracker?
Read Documentation/stable_kernel_rules.txt for how patches get
backported to older stable kernel releases.
thanks,
greg k-h
next prev parent reply other threads:[~2014-10-23 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 3:05 /drivers/staging/TODO doc and kernel tasks question Jaime Arrocha
2014-10-23 3:18 ` Greg KH [this message]
2014-10-23 20:18 ` Jaime Arrocha
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=20141023031816.GA14228@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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).