From: Darren Hart <dvhart@infradead.org>
To: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"Hart, Darren" <darren.hart@intel.com>,
"rkhan@redhat.com" <rkhan@redhat.com>,
"alexander.h.duyck@redhat.com" <alexander.h.duyck@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/7][RFC] FUJITSU Extended Socket network device driver
Date: Wed, 20 May 2015 16:47:11 +0200 [thread overview]
Message-ID: <20150520144711.GE22037@vmdeb7> (raw)
In-Reply-To: <E86EADE93E2D054CBCD4E708C38D364A5422D803@G01JPEXMBYT01>
On Wed, May 20, 2015 at 08:04:07AM +0000, Izumi, Taku wrote:
> Hi All,
>
> This patchsets add support for FUJITSU Extended Socket network
> device. Extended Socket network device is a shared memory
> based high-speed network interface between Extended Partitions of
> PRIMEQUEST 2000 E2 series.
Hi Taku,
A few things to keep in mind.
1) Always Cc the maintainer using the email address in the MAINTAINERS file,
in this case, dvhart at infradead.org.
2) See Documentation/email-clients.txt regarding charset (you sent ISO-2022,JP):
Email clients should not modify the character set encoding of the text.
Emailed patches should be in ASCII or UTF-8 encoding only.
If you configure your email client to send emails with UTF-8 encoding,
you avoid some possible charset problems.
3) A new driver should be functional at each patch point, so committing a
skeleton that does nothing is not what we're looking for by "small functional
changes".
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-05-20 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 8:04 [PATCH 0/7][RFC] FUJITSU Extended Socket network device driver Izumi, Taku
2015-05-20 14:47 ` Darren Hart [this message]
2015-05-21 3:16 ` Izumi, Taku
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=20150520144711.GE22037@vmdeb7 \
--to=dvhart@infradead.org \
--cc=alexander.h.duyck@redhat.com \
--cc=darren.hart@intel.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rkhan@redhat.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;
as well as URLs for NNTP newsgroup(s).