From: Sedat Dilek <sedat.dilek@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [3.8-rc1] Networking problems after pulling-in net.git#master
Date: Sun, 23 Dec 2012 15:36:59 +0100 [thread overview]
Message-ID: <CA+icZUXyBU301ZsKhhiHEsbpxX8gikhktRWFH4x_MSLc8M1eRA@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpU5VLGOAcZ=RfF8VqpRNTy7rueVpm=+U0Zy5SoAYk4THw@mail.gmail.com>
On Sun, Dec 23, 2012 at 3:25 PM, Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Sun, Dec 23, 2012 at 10:14 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>
>> [ CCing Eric ]
>>
>> YES, thie fixes my problem.
>> But your patch was somehow malformed, so I attached mine.
>>
>
> Thanks for testing!
>
> I knew it as I replied in wed Gmail. :) I will send a normal patch
> with your Reported-by and Tested-by.
/o\ for your quick reply and patch!
Just as a sidenote:
The mentioned MEI patch [1] did also fix the ugly locking on
soft-reboot (for people who are affected and know about GIYF) :-).
Good I am doing a (filesystem) sync before reboots.
I did not much testing, but for a -rc1 release this looks now fine to me.
- Sedat -
[1] http://marc.info/?l=linux-kernel&m=135612627527193&w=2
prev parent reply other threads:[~2012-12-23 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 3:14 [3.8-rc1] Networking problems after pulling-in net.git#master Sedat Dilek
2012-12-23 11:42 ` Borislav Petkov
2012-12-23 12:26 ` Sedat Dilek
2012-12-23 12:40 ` Sedat Dilek
2012-12-23 13:19 ` Sedat Dilek
2012-12-23 13:44 ` Cong Wang
2012-12-23 14:10 ` Julian Anastasov
2012-12-23 14:28 ` Cong Wang
2012-12-23 14:14 ` Sedat Dilek
2012-12-23 14:25 ` Cong Wang
2012-12-23 14:36 ` Sedat Dilek [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=CA+icZUXyBU301ZsKhhiHEsbpxX8gikhktRWFH4x_MSLc8M1eRA@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@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).