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 12:00:56 +0000 [thread overview]
Message-ID: <20130726120056.GG5585@mwanda> (raw)
In-Reply-To: <201307242015.r6OKFcTp1000140@rivendell.pollux.laing>
Oh, one other thing. The subject should be:
Subject: [patch] staging: comedi: dt9812: Resolves sparse warnings regarding byte ordering.
Actually, that's too long.
But do a `git log --oneline drivers/staging/comedi/drivers/dt9812.c`
to see previous subjects.
regards,
dan carpenter
next prev parent reply other threads:[~2013-07-26 12:00 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
2013-07-26 12:00 ` Dan Carpenter [this message]
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=20130726120056.GG5585@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox