From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pci maillist <linux-pci@atrey.karlin.mff.cuni.cz>,
Tom Long Nguyen <tom.l.nguyen@intel.com>
Subject: Re: [PATCH 1/6] PCI-Express AER implemetation
Date: Wed, 12 Jul 2006 13:07:36 +0800 [thread overview]
Message-ID: <1152680856.28493.204.camel@ymzhang-perf.sh.intel.com> (raw)
In-Reply-To: <20060712041847.GA20793@kroah.com>
On Wed, 2006-07-12 at 12:18, Greg KH wrote:
> On Wed, Jul 12, 2006 at 09:36:40AM +0800, Zhang, Yanmin wrote:
> > I changed a little about the patches, so resend and cc to Greg.
> >
> > Greg,
> >
> > Could you consider for your testing tree?
>
> Two comments on this series:
Thanks for your kind comments!
> - the pci_regs.h change I can take right now, that's in the standard
> so it can't hurt to add it now, right? Is this ok?
It's ok.
>
> - the patches break the build if you try to build things without the
> whole series applied. That's not good for users running 'git
> bisect' on Linus's tree. Can you redo the series so this doesn't
> happen?
I will try to separate them more reasonably, but the new
patch might be too big to be sent to LKML.
next prev parent reply other threads:[~2006-07-12 5:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 1:36 Zhang, Yanmin
2006-07-12 1:41 ` [PATCH 2/6] " Zhang, Yanmin
2006-07-12 1:45 ` [PATCH 3/6] " Zhang, Yanmin
2006-07-12 1:53 ` [PATCH 4/6] " Zhang, Yanmin
2006-07-12 2:01 ` [PATCH 5/6] " Zhang, Yanmin
2006-07-12 2:08 ` [PATCH 6/6] " Zhang, Yanmin
2006-07-12 4:18 ` [PATCH 1/6] " Greg KH
2006-07-12 5:07 ` Zhang, Yanmin [this message]
2006-07-12 4:20 ` Greg KH
2006-07-12 5:08 ` Zhang, Yanmin
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 1:12 Zhang, Yanmin
2006-06-29 16:22 ` Grant Grundler
2006-06-30 1:28 ` Zhang, Yanmin
2006-06-30 7:52 ` Zhang, Yanmin
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=1152680856.28493.204.camel@ymzhang-perf.sh.intel.com \
--to=yanmin_zhang@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=tom.l.nguyen@intel.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
all inboxes | Powered by JetHome®