From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, yinghai@kernel.org,
bhutchings@solarflare.com, socketcan@hartkopp.net,
bhelgaas@google.com, linux@dominikbrodowski.net
Subject: Re: [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions
Date: Mon, 4 Jul 2011 11:55:23 +0800 [thread overview]
Message-ID: <20110704035519.GA2162@gmail.com> (raw)
In-Reply-To: <CA+55aFwo-48yKu+raRF3B9n1mqd1qV35eDq56Yi+erPygkuTvA@mail.gmail.com>
On Sun, Jul 03, 2011 at 02:30:00PM -0700, Linus Torvalds wrote:
> And some of the cleanup stuff I could merge for 3.0 just to make things easier.
Hi linus,
IMO, codingstyle is so important for us. It turns our codes readable and
easy. What you said in the Documentation/CodingStyle file is always useful. We
should allow the rules in it, which is helpful for maintainers to manage their branches.
I will devote myself to fixing some cleanup for us. I think that would be so exciting for me.
Cheers
Thanks
Harry Wei
next prev parent reply other threads:[~2011-07-04 3:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 23:47 [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions Ram Pai
2011-06-30 23:47 ` [PATCH 1/5 v2] PCI: honor child buses optional size in hot plug configuration Ram Pai
2011-06-30 23:47 ` [PATCH 2/5 v2] PCI : ability to relocate assigned pci-resources Ram Pai
2011-06-30 23:47 ` [PATCH 3/5 v2] PCI: make SRIOV resources optional Ram Pai
2011-07-01 6:01 ` Oliver Hartkopp
2011-07-06 17:48 ` Jesse Barnes
2011-07-07 15:34 ` Oliver Hartkopp
2011-06-30 23:47 ` [PATCH 4/5 v2] PCI: make cardbus-bridge " Ram Pai
2011-06-30 23:47 ` [PATCH 5/5 v2] PCI: code and terminology cleanup Ram Pai
2011-07-01 23:07 ` [PATCH 0/5 v2] PCI: fix cardbus and sriov regressions Ben Hutchings
2011-07-02 13:04 ` Ram Pai
2011-07-04 23:35 ` Ben Hutchings
2011-07-03 21:30 ` Linus Torvalds
2011-07-04 3:55 ` Harry Wei [this message]
2011-07-06 8:53 ` Ram Pai
2011-07-06 17:46 ` Jesse Barnes
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=20110704035519.GA2162@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=bhelgaas@google.com \
--cc=bhutchings@solarflare.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=socketcan@hartkopp.net \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/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