All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: cciss update [1 of 6]
Date: Thu, 5 Aug 2004 10:26:26 -0700	[thread overview]
Message-ID: <20040805102626.0bcd3199.akpm@osdl.org> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF107DBFBA7@cceexc23.americas.cpqcorp.net>

"Miller, Mike (OS Dev)" <mike.miller@hp.com> wrote:
>
> Sorry, I thought the descriptions in the patch were sufficient. 

The descriptions are fine - I was just mentioning the email's Subject:
line.

> Again, I wish viro would copy me on patches to cciss. Isn't that the normal protocol, include the maintainer in any updates?

It tends to depend on the importance of the patch, the activity level of
the maintainer, etc.  If the patches are dependent on other patches to
other parts of the kernel then it's best that they all go in as a single
lump.  A courtesy Cc: never hurts, althought it's sometime hard to hunt
down the right person.

I have suffered some pain from the depredations of the sparse changes. 
Hopefully it's mostly all done now.

  parent reply	other threads:[~2004-08-05 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 14:23 cciss update [1 of 6] Miller, Mike (OS Dev)
2004-08-05 15:02 ` Jens Axboe
2004-08-05 17:26 ` Andrew Morton [this message]
2004-08-05 18:26 ` viro
  -- strict thread matches above, loose matches on Subject: below --
2004-08-05 20:44 Miller, Mike (OS Dev)
2004-08-04 20:58 Miller, Mike (OS Dev)
2004-08-04 23:29 ` Andrew Morton

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=20040805102626.0bcd3199.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.miller@hp.com \
    /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.