From: Okash Khawaja <okash.khawaja@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adm8211: fix the possible pci cache line sizes inside switch-case
Date: Tue, 5 May 2015 23:50:22 +0100 [thread overview]
Message-ID: <20150505225022.GA3877@bytefire-computer> (raw)
In-Reply-To: <1430863313.9365.49.camel@perches.com>
On Tue, May 05, 2015 at 03:01:53PM -0700, Joe Perches wrote:
> On Tue, 2015-05-05 at 22:48 +0100, Okash Khawaja wrote:
> > The PCI cache line size value, stored in cline variable, was being
> > compared against decimal values written as hex literals. This patch
> > changes those literals to correct hex values.
>
> This is fine.
>
> The grammar might be better as something like:
>
> The PCI cache line size value was being compared against
> decimal values prefixed with 0x.
>
> Fix the literals to use the correct hex values.
>
> > Please note that this patch is on top of
> > another code cleanup patch '[PATCH] adm8211: fix checkpatch errors for
> > indentation and new line around switch-case'.
>
> But this information doesn't belong here as
> it would also be in a git log when someone
> uses git am to apply it to a tree.
>
> It'd be better to send a patch series using
> "git format-email --cover-letter -2 -o <dir>"
> and use git send-email for the series.
>
>
This is my first time going throug the process of submitting patches, something you may have already noticed. I have created and submitted patch series.Thanks
prev parent reply other threads:[~2015-05-05 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 21:48 [PATCH] adm8211: fix the possible pci cache line sizes inside switch-case Okash Khawaja
2015-05-05 22:01 ` Joe Perches
2015-05-05 22:50 ` Okash Khawaja [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=20150505225022.GA3877@bytefire-computer \
--to=okash.khawaja@gmail.com \
--cc=joe@perches.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.