public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: sakurai_hiro@soft.fujitsu.com, James.Bottomley@steeleye.com,
	akpm@osdl.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Patro,
	Sumant" <Sumant.Patro@engenio.com>,
	"Yang, Bo" <Bo.Yang@engenio.com>
Subject: Re: [PATCH 3/3] scsi : megaraid_{mm,mbox}: a fix on "kernel unaligned access address" issue
Date: Tue, 25 Jul 2006 17:05:25 +0200	[thread overview]
Message-ID: <200607251705.26361.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261932E2D1@NAMAIL3.ad.lsil.com>

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

Ju, Seokmann wrote:
> Hi,
>
> This is a third patch which follows prevous two patches ([PATCH 1/3] and
> [PATCH 2/3]).

Either use a [0/3] mail that describes the complete changeset or just send 
each patch as a reply to the previous one. This way they are grouped together 
in the mail programs. That keeps the inbox clean and the relationsship is 
clearer.

> Signed-Off By: Seokmann Ju <seokmann.ju@lsil.com>
> ---
> diff -Naur inqwithevpd/Documentation/scsi/ChangeLog.megaraid
> unaligned/Documentation/scsi/ChangeLog.megaraid
> --- inqwithevpd/Documentation/scsi/ChangeLog.megaraid	2006-07-24
> 15:35:02.000000000 -0400
> +++ unaligned/Documentation/scsi/ChangeLog.megaraid	2006-07-24
> 15:41:49.000000000 -0400
> @@ -66,6 +66,61 @@
>  	Fix: MegaRAID F/W has fixed the problem and being process of
> release,
>  	soon. Meanwhile, driver will filter out the request.
>
> +3.	One of member in the data structure of the driver leads unaligne
                                                                ^^^^^^^^
> +	issue on 64-bit platform.
> +	Customer reporeted "kernel unaligned access addrss" issue when
                                                   ^^^^^^

Typos.

> +	> -----Original Message-----
[...]

This is IMHO too much data for an in-kernel changelog. I would vote for 
including this in your commit comments, then it will be available as git 
comment and not inflate the kernel tree itself with text that's useless for 
most users. This is really only of interest if someone tries to find out 
something about the changes in this driver and then he's normally also 
interested in the diffs itself.

Eike

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-07-25 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 14:45 [PATCH 3/3] scsi : megaraid_{mm,mbox}: a fix on "kernel unaligned access address" issue Ju, Seokmann
2006-07-25 15:05 ` Rolf Eike Beer [this message]

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=200607251705.26361.eike-kernel@sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=Bo.Yang@engenio.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=Seokmann.Ju@lsil.com \
    --cc=Sumant.Patro@engenio.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sakurai_hiro@soft.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox