From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>, <syrine.tl@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Null pointers linux3.8-rc6
Date: Thu, 7 Feb 2013 20:23:46 +0000 [thread overview]
Message-ID: <1360268626.3605.33.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <20130207.145147.2001556658631071207.davem@davemloft.net>
On Thu, 2013-02-07 at 14:51 -0500, David Miller wrote:
> From: syrine tlili <syrine.tl@gmail.com>
> Date: Thu, 7 Feb 2013 20:43:42 +0100
>
> > Patches for null pointer check
>
> You need to provide a more verbose commit message.
>
> You must provide a proper signoff as per Documentation/SubmittingPatches
...and send to more appropriate recipients as suggested by
scripts/get_maintainer.pl
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-02-07 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 19:32 Null pointers linux3.8-rc6 syrine tlili
2013-02-07 19:39 ` David Miller
2013-02-07 19:43 ` syrine tlili
2013-02-07 19:51 ` David Miller
2013-02-07 20:23 ` Ben Hutchings [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=1360268626.3605.33.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=syrine.tl@gmail.com \
/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