add211056115e47bcd5f3f831904b6bf375ec5bb — Bryan Brattlof 3 years ago 8f05fb6
task 10: add task readme
2 files changed, 38 insertions(+), 0 deletions(-)

M readme.rst
A tasks/10/readme
M readme.rst => readme.rst +2 -0
@@ 30,3 30,5 @@ Here are the links to each task's readme:
8. Working with debugfs: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/08/readme>`__

9. Working with sysfs: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/09/readme>`__

10. Submit a Patch: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/10/readme>`__

A tasks/10/readme => tasks/10/readme +36 -0
@@ 0,0 1,36 @@
Task 10

Yeah, you conquered the sysfs monster, great job!

Now you know to never want to mess with a kobject again, right?  Trust
me, there are easier ways to create sysfs files, and we will get into
that for a future task, but for now, let's make it a bit more simple
after all of that coding.

For this task, go back to the linux-next tree you used for task 07.
Update it, and then do the following:

  - Create a patch that fixes one coding style problem in any of the
    files in drivers/staging/

  - Make sure the patch is correct by running it through

  - Submit the code to the maintainer of the driver/subsystem, finding
    the proper name and mailing lists to send it to by running the tool,
    scripts/get_maintainer.pl on your patch.

  - Send a web link back to me of your patch on the public mailing list
    archive (don't cc: me on the patch, that will only confuse me and
    everyone in the kernel development community.)

  - If you want to mention the Eudyptula Challenge as the reason for
    writing the patch, feel free to do so in the body of the patch, but
    it's not necessary at all.

Hopefully this patch will be accepted into the kernel tree, and all of a
sudden, you are an "official" kernel developer!

Don't worry, there's plenty more tasks coming, but a little breather
every now and again for something simple is always nice to have.