From: Jarek Poplawski <jarkao2@gmail.com>
To: Zimny Lech <napohybelskurwysynom2010@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Shreyas Bhatewara <sbhatewara@vmware.com>,
"VMware, Inc." <pv-drivers@vmware.com>,
netdev@vger.kernel.org
Subject: Re: linux-next: Tree for November 26
Date: Sat, 27 Nov 2010 20:02:39 +0100 [thread overview]
Message-ID: <4CF155CF.5090601@gmail.com> (raw)
In-Reply-To: <AANLkTinJUT=j_P9FSB=GWTLy4Bkr68iWmB2O=5Q3gcT-@mail.gmail.com>
Zimny Lech wrote:
...
> --
> Slawa!
> Zimny "Żyj i pozwól umrzeć" Lech z Wawelu
FYI:
http://www.kernel.org/pub/linux/docs/lkml/#s3-12
Jarek P.
next prev parent reply other threads:[~2010-11-27 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101126132823.7ef94f07.sfr@canb.auug.org.au>
2010-11-27 8:38 ` linux-next: Tree for November 26 Zimny Lech
2010-11-27 19:02 ` Jarek Poplawski [this message]
2010-11-27 20:55 ` Mariusz Kozlowski
2010-11-29 8:03 ` Shreyas Bhatewara
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=4CF155CF.5090601@gmail.com \
--to=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=sbhatewara@vmware.com \
--cc=sfr@canb.auug.org.au \
/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).