public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daouda LO <daouda@mandrakesoft.com>
To: Sourav Sen <sourav@csa.iisc.ernet.in>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: How to write patches
Date: 29 Dec 2000 19:48:41 +0000	[thread overview]
Message-ID: <m2wvcjc8km.fsf@touba.mandrakesoft.com> (raw)
In-Reply-To: <Pine.SOL.3.96.1001229234454.12681A-100000@kohinoor.csa.iisc.ernet.in>
In-Reply-To: Sourav Sen's message of "Fri, 29 Dec 2000 23:52:05 +0530 (IST)"

Sourav Sen <sourav@csa.iisc.ernet.in> writes:

> Hi,
> 
> This question may seem naive, but can anyone tell me if there is any
> structured way of writing patches? 
> 
> I mean suppose I want to implement some
> kernel mechanism, and I define my data structures etc. and made most of
> the code as loadable  module to start with, but still I am having to
> change some parts of the kernel code at the development time, and I
> want to make that change using patches, so that I do not have to browse
> thru the files to change the code as I debug. 
> 
> Is there any structured way of doing this?

have a look at:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0011.2/0151.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-29 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-29 18:22 How to write patches Sourav Sen
2000-12-29 19:48 ` Daouda LO [this message]
2000-12-30 17:30 ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2000-12-29 21:54 Pete Zaitcev

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=m2wvcjc8km.fsf@touba.mandrakesoft.com \
    --to=daouda@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sourav@csa.iisc.ernet.in \
    /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