From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trapdoor6@gmail.com
Cc: trivial@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Small typo in kernel [current source from git] .config option
Date: Tue, 27 Jul 2010 09:45:50 -0700 [thread overview]
Message-ID: <4C4F0D3E.6030301@gmail.com> (raw)
In-Reply-To: <AANLkTin+a3V5Lydg__XGZwTDZbUKqeyHY4X57bBpc0CS@mail.gmail.com>
On 07/27/2010 09:35 AM, trapDoor wrote:
> On Tue, Jul 27, 2010 at 4:50 PM, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> On 07/27/2010 07:46 AM, trapDoor wrote:
>>>
>>> Hello,
>>> I've just got lucky and found this little typo under "Power management
>>> and ACPI options" ---> "ACPI (Advanced Configuration and Power
>>> Interface) Support":
>>> hArdware Error Device
>>>
>>> Here is my fix:
>>> Hardware Error Device
>>> :)
>>>
>>> BTW, first time I've used nconfig instead of menuconfig. And I like it.
>>>
>>
>> probably should create a patch, and send it to trivial@kernel.org
>>
>> Justin P. Mattock
>>
>
> Sure, but I don't know which script generates that part of config and
> ... how to do the patch :| (Sorry, I'm not even a greenhorn on the
> programming field).
> Just cc-eding trivial@kernel.org for now ..
>
That's alright.. I'm still a newbie over here...
read Documentation/SubmittingPatches
there the instructions on how to create a perfect patch is there.
then when done make sure you use scripts/checkpatch to check you patch
then when all good use scripts/getmaintainer.pl to find the appropriate
people to send it too.
and voila you'll be sending patches to the kernel like there's no
tomorrow...
Justin P. Mattock
next prev parent reply other threads:[~2010-07-27 16:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 14:46 Small typo in kernel [current source from git] .config option trapDoor
2010-07-27 15:50 ` Justin P. Mattock
2010-07-27 16:35 ` trapDoor
2010-07-27 16:45 ` Justin P. Mattock [this message]
2010-07-27 16:55 ` Sam Ravnborg
2010-07-27 17:12 ` trapDoor
2010-07-28 11:02 ` Michal Marek
2010-07-28 12:17 ` trapDoor
2010-07-28 15:41 ` Michal Marek
2010-07-28 18:55 ` Sam Ravnborg
2010-07-29 5:04 ` Nir Tzachar
2010-07-29 6:20 ` trapDoor
2010-07-29 8:05 ` Michal Marek
2010-07-29 10:33 ` Nir Tzachar
2010-07-29 14:19 ` Randy Dunlap
2010-07-29 19:50 ` Nir Tzachar
2010-08-01 7:20 ` [PATCH] nconfig: add search support nir.tzachar
2010-08-01 9:28 ` Sam Ravnborg
2010-08-01 10:21 ` Nir Tzachar
2010-08-01 11:49 ` Sam Ravnborg
2010-08-02 16:32 ` Randy Dunlap
2010-08-03 4:37 ` Nir Tzachar
2010-08-02 21:22 ` rdunlap
2010-08-03 4:41 ` Nir Tzachar
2010-08-03 12:28 ` nir.tzachar
2010-08-05 17:04 ` Randy Dunlap
2010-08-05 18:13 ` Nir Tzachar
2010-08-05 18:19 ` Randy Dunlap
2010-08-06 12:41 ` Nir Tzachar
2010-08-06 13:54 ` Sam Ravnborg
2010-08-06 19:22 ` Nir Tzachar
2010-08-06 14:09 ` Sam Ravnborg
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=4C4F0D3E.6030301@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trapdoor6@gmail.com \
--cc=trivial@kernel.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