From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/1] staging/comedi/drivers/dt9812.c: Resolves sparse warnings regarding byte ordering.
Date: Fri, 26 Jul 2013 11:57:56 +0000 [thread overview]
Message-ID: <20130726115756.GF5585@mwanda> (raw)
In-Reply-To: <201307242015.r6OKFcTp1000140@rivendell.pollux.laing>
On Wed, Jul 24, 2013 at 02:15:38PM -0600, Shaun Laing wrote:
> From: Shaun Laing <shaun-lk@xresource.ca>
This is not needed since you are the author. The email should
match the email address you are using to send patches.
The signed-off-by thing is intended to have a legal meaning, that
you didn't violate copyright or anything. You are using a different
email to send patches and to sign so it's a bit weird. Obviously,
we don't actually know that your real name is "Shaun Laing" either,
so it's not like it's a bullet proof system. But we generally say
that the email should match at least and if we know that it looks
like a fake name we won't accept that either.
> Signed-off-by: Shaun Laing <shaun-lk@xresource.ca>
Put the signed off by at the end of the patch.
>
> * Resolves sparse warnings of the form "warning: cast to restricted __le??"
> * Renames temp variables to include "le", to remind that the values are little endian
Don't put an "le" in the name. It looks ugly/doesn't match kernel
naming style and anyway sparse will remind you if you forget about
endianess.
Otherwise, the patch looks good. Resend it to the people in
./scripts/get_maintainer.pl. Always CC at least one mailing list.
There is a mailing list for staging code so you don't need to CC
linux-kernel (they will just ignore the patch anyway).
regards,
dan carpenter
next prev parent reply other threads:[~2013-07-26 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:15 [PATCH 1/1] staging/comedi/drivers/dt9812.c: Resolves sparse warnings regarding byte ordering Shaun Laing
2013-07-25 19:58 ` Shaun Laing
2013-07-26 11:57 ` Dan Carpenter [this message]
2013-07-26 12:00 ` Dan Carpenter
2013-07-26 13:09 ` Shaun Laing
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=20130726115756.GF5585@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@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.