All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoon Soo <yoonsoo@web.de>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] introduction and first questions
Date: Wed, 26 May 2004 20:37:45 +0000	[thread overview]
Message-ID: <40B50019.7040607@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

Hi all,

I am new in this list and there are some points which are not very clear 
to me. But first of all, I read the todo list and worked on the point to 
get rid of the 'old-fashioned' way to access the driver_data field 
direct and replaced them with the proper dev_get/set_drvdata or 
pci_get/set_drvdata.

I created the patch like mentioned in the patchsubmitting-howto of the 
source documentation, and have tested it. What are now the further 
steps, just sending the patch as attachement to this list? Another 
question is, which original source code version should be taken..2.6.6 
(as I did) or the most actual from the cvs tree?

Very many thanks in advance for helping me making the first steps ;)

greets

ys

PS. As I have seen while working on my patch, tty->driver_data should 
also not accessed directly, and for the consistency tty_get_drvdata and 
tty_set_drvdata should be added too and called instead of the direct 
access. Is this the right list to discuss this matter? Or is it in work?

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

             reply	other threads:[~2004-05-26 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 20:37 Yoon Soo [this message]
2004-05-27 21:50 ` [Kernel-janitors] introduction and first questions maximilian attems

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=40B50019.7040607@web.de \
    --to=yoonsoo@web.de \
    --cc=kernel-janitors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.