From: Andrew Morton <akpm@osdl.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: bunk@fs.tum.de, linux-kernel@vger.kernel.org,
James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org
Subject: Re: [patch] 2.6.9-rc1-mm1: megaraid_mbox.c compile error with gcc 3.4
Date: Mon, 30 Aug 2004 12:55:09 -0700 [thread overview]
Message-ID: <20040830125509.46ea399c.akpm@osdl.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC9C6@exa-atlanta>
"Mukker, Atul" <Atulm@lsil.com> wrote:
>
> 2. The guideline on the size of patches. Because of the new driver, the
> size of the patches for megaraid are relatively big (the small patches are
> always inlined). Should it be discretionary for submitter to either inline,
> attach, or (deprecated) send a link, based on size of the package.
Sending a URL to a big patch is a necessary evil for mailing lists, so the
best approach would be to also mail the patches directly to the guy(s) who
you wish to apply them.
An even better approach is to split the patches up so they are not so big ;)
Following the "once concept per patch rule" works well.
next prev parent reply other threads:[~2004-08-30 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 13:05 [patch] 2.6.9-rc1-mm1: megaraid_mbox.c compile error with gcc 3.4 Mukker, Atul
2004-08-30 19:55 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-28 16:29 Mukker, Atul
2004-08-28 20:04 ` Andrew Morton
2004-08-28 20:17 ` Lee Revell
2004-08-29 13:34 ` James Bottomley
[not found] <20040826014745.225d7a2c.akpm@osdl.org>
2004-08-28 9:06 ` Adrian Bunk
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=20040830125509.46ea399c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox