From: David Miller <davem@davemloft.net>
To: erwanaliasr1@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
tshimizu818@gmail.com
Subject: Re: [PATCH] pch_gbe: Adding read memory barriers
Date: Tue, 08 May 2012 14:39:51 -0400 (EDT) [thread overview]
Message-ID: <20120508.143951.1433269599287007774.davem@davemloft.net> (raw)
In-Reply-To: <4FA96770.9070009@gmail.com>
From: Erwan Velu <erwanaliasr1@gmail.com>
Date: Tue, 08 May 2012 20:35:28 +0200
> Le 07/05/2012 21:30, Erwan Velu a écrit :
>> From bb1e271db0fa1a29df19bede69faf8004389132d Mon Sep 17 00:00:00 2001
>> From: Erwan Velu <erwan.velu@zodiacaerospace.com>
>> Date: Mon, 7 May 2012 19:15:29 +0000
>> Subject: [PATCH 1/1] pch_gbe: Adding read memory barriers
>
> Does my patch can be considered as acceptable or shall I rework
> something on it ?
You never need to ask questions like this.
Your patch is queued up to be reviewed in patchwork:
http://patchwork.ozlabs.org/project/netdev/list/
Therefore you only make more work for maintainers and irritate them by
asking this, and therefore it will take even longer for them to get to
your patch.
next prev parent reply other threads:[~2012-05-08 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 19:30 [PATCH] pch_gbe: Adding read memory barriers Erwan Velu
2012-05-08 18:35 ` Erwan Velu
2012-05-08 18:39 ` David Miller [this message]
2012-05-08 19:27 ` Erwan Velu
2012-05-09 10:47 ` David Laight
2012-05-09 13:18 ` Ben Hutchings
[not found] ` <CAL2JzuxirjAnmbcV+R=MJFAi1+ayrRnM6i0Dz5poqMuG7Cxwxg@mail.gmail.com>
2012-05-09 14:44 ` David Laight
[not found] ` <CAL2JzuxawnesC+=Fqyu71Hkwi5gnRughe_NYM4k1c=zqDoNGRg@mail.gmail.com>
2012-05-09 15:39 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2012-05-07 17:49 Erwan Velu
2012-05-07 17:57 ` David Miller
2012-05-07 17:39 Erwan Velu
2012-05-07 17:44 ` David Miller
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=20120508.143951.1433269599287007774.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=erwanaliasr1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tshimizu818@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;
as well as URLs for NNTP newsgroup(s).