From: jitendra kumar khasdev <jkhasdev@gmail.com>
To: abbotti@mev.co.uk, hsweeten@visionengravers.com,
gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
pankaj.saraf@nektech.in,
jitendra kumar khasdev <jkhasdev@gmail.com>
Subject: [PATCH 0/5] *** SUBJECT HERE ***
Date: Sat, 3 Jan 2015 14:06:22 +0530 [thread overview]
Message-ID: <1420274187-6779-1-git-send-email-jkhasdev@gmail.com> (raw)
*** BLURB HERE ***
jitendra kumar khasdev (5):
Staging: comedi: fix line over 80 characters warning
Staging: comedi: fix line over 80 characters warning
Staging: comedi: fix line over 80 characters warning
Staging: comedi: fix line over 80 characters warning
Staging: comedi: fix line over 80 characters warning
drivers/staging/comedi/drivers/pcl812.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-03 8:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 8:36 jitendra kumar khasdev [this message]
2015-01-03 8:36 ` [PATCH 1/5] Staging: comedi: fix line over 80 characters warning jitendra kumar khasdev
2015-01-03 12:20 ` Sudip Mukherjee
2015-01-03 8:36 ` [PATCH 2/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 3/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 4/5] " jitendra kumar khasdev
2015-01-03 8:36 ` [PATCH 5/5] " jitendra kumar khasdev
2015-01-03 16:45 ` [PATCH 0/5] *** SUBJECT HERE *** Greg KH
2015-01-03 22:54 ` Paul Bolle
2015-01-04 1:41 ` Konrad Zapalowicz
2015-01-05 22:18 ` Paul Bolle
-- strict thread matches above, loose matches on Subject: below --
2019-03-23 12:53 Cristian Sicilia
2019-03-23 19:24 ` Matt Ranostay
2012-01-26 20:11 Chase Maupin
2012-01-26 20:12 ` Maupin, Chase
2012-01-31 16:22 ` Maupin, Chase
2010-06-14 9:44 Nicholas A. Bellinger
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=1420274187-6779-1-git-send-email-jkhasdev@gmail.com \
--to=jkhasdev@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.saraf@nektech.in \
/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.