From: Michael J Gruber <git@drmicha.warpmail.net>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, "Éric Piel" <Eric.Piel@tremplin-utc.net>,
"Pavel Machek" <pavel@suse.cz>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] lis3lv02d: support both one- and two-byte sensors
Date: Wed, 11 Feb 2009 12:16:35 +0100 [thread overview]
Message-ID: <4992B393.8070808@drmicha.warpmail.net> (raw)
In-Reply-To: <1234310519-14230-1-git-send-email-giuseppe.bilotta@gmail.com>
Giuseppe,
you may prefer sending this to the kernel mailing list rather than the
git list. But we can tell you the patch is formatted as a proper git
patch ;)
Cheers,
Michael
next prev parent reply other threads:[~2009-02-11 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 0:01 [PATCH] lis3lv02d: support both one- and two-byte sensors Giuseppe Bilotta
2009-02-11 11:16 ` Michael J Gruber [this message]
2009-02-11 11:22 ` Giuseppe Bilotta
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 23:34 Giuseppe Bilotta
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=4992B393.8070808@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Eric.Piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=pavel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).