From: srivatsa.bhat@linux.vnet.ibm.com (Srivatsa S. Bhat)
To: kernelnewbies@lists.kernelnewbies.org
Subject: reboot.c and X86-64 architectures
Date: Thu, 05 Apr 2012 18:58:15 +0530 [thread overview]
Message-ID: <4F7D9DEF.2050909@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F7D9700.3030801@meetinghouse.net>
On 04/05/2012 06:28 PM, Miles Fidelman wrote:
> Srivatsa,
>
> Thanks very much. Two follow-up questions, if I might...
>
Sure!
> Srivatsa S. Bhat wrote:
>> On 04/04/2012 07:18 PM, Miles Fidelman wrote:
>>>
>>> Perhaps someone here can help me understand the behavior of the
>>> kernel reboot code.
>>>
>>
>> I suggest you post this issue on lkml, with CC to the authors/maintainers
>> of the code, which would be the following list, as per get_maintainer.pl:
>>
>> Thomas Gleixner<tglx@linutronix.de>
>> Ingo Molnar<mingo@redhat.com>
>> "H. Peter Anvin"<hpa@zytor.com>
>> x86 at kernel.org
>> Peter Chubb<peter.chubb@nicta.com.au>
>> Michael D Labriola<michael.d.labriola@gmail.com>
>> Matthew Garrett<mjg@redhat.com>
>> linux-kernel at vger.kernel.org
>
> I posted this to linux-kernel a few days ago, and didn't receive any
> replies. Or is lkml a different list?
>
Possibly because the right people might not have noticed the issue.
Or maybe they are quite busy at the moment... It is reasonable to wait for
a week before trying again.
If you don't get any replies by a week, try reposting the issue with a more
appropriate subject. (After all, people skim emails by their subject lines ;-)).
Seriously speaking, you are facing a problem, so it would probably be better
to rewrite the subject like a bug/problem report than just a question.
Also add enough relevant info in the subject itself (without cluttering
it of course), to get interested people to read your email. (Look at some of
the other bug reports that float around lkml to see how to do it.)
> And... what is get_maintainer.pl? Or perhaps where does it run is a
> more accurate question, what it does is pretty obvious from the name :-)
>
get_maintainer.pl is a script in the scripts/ directory in the kernel source.
Usually, when submitting patches, we run this script from the root of the kernel
source tree. It gives the list of maintainers or kernel developers who have
contributed most to the code, who are relevant to the patch in question.
Then the patch is mailed to these people and the appropriate mailing lists.
Eg: $cd linux
$./scripts/get_maintainer.pl <patch_file>
To get the kernel developers associated with a particular file instead of a
patch, use the --file option.
$cd linux
$./scripts/get_maintainer.pl --file arch/x86/kernel/reboot*
[This is the output I posted in my previous mail :-)]
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2012-04-05 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F79E6BE.4030302@meetinghouse.net>
2012-04-04 3:22 ` reboot.c and X86-64 architectures Miles Fidelman
2012-04-04 13:34 ` Jim Cromie
2012-04-04 13:48 ` Miles Fidelman
2012-04-05 5:54 ` Srivatsa S. Bhat
2012-04-05 12:58 ` Miles Fidelman
2012-04-05 13:28 ` Srivatsa S. Bhat [this message]
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=4F7D9DEF.2050909@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.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).