From: Erwan Velu <erwanaliasr1@gmail.com>
To: David Miller <davem@davemloft.net>
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 21:27:45 +0200 [thread overview]
Message-ID: <4FA973B1.5080808@gmail.com> (raw)
In-Reply-To: <20120508.143951.1433269599287007774.davem@davemloft.net>
Le 08/05/2012 20:39, David Miller a écrit :
> 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.
It wasn't my aim to irritate anyone. I'm just brand new into committing
something here and surely lack of a good understanding on the complete
process.
I do understand you are very solicited and newbies like me can sometimes
irritate by asking questions & doing thing not properly.
Anyway, thanks for your help & patience.
Erwan
next prev parent reply other threads:[~2012-05-08 19:27 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
2012-05-08 19:27 ` Erwan Velu [this message]
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=4FA973B1.5080808@gmail.com \
--to=erwanaliasr1@gmail.com \
--cc=davem@davemloft.net \
--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