linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h
Date: Mon, 31 Jul 2006 14:40:34 +0800	[thread overview]
Message-ID: <1154328033.27051.60.camel@ymzhang-perf.sh.intel.com> (raw)
In-Reply-To: <20060731050635.GA29058@kroah.com>

On Mon, 2006-07-31 at 13:06, Greg KH wrote:
> On Mon, Jul 31, 2006 at 12:38:18PM +0800, Zhang, Yanmin wrote:
> > On Mon, 2006-07-31 at 12:00, Greg KH wrote:
> > > On Mon, Jul 31, 2006 at 11:10:39AM +0800, Zhang, Yanmin wrote:
> > > > Although Greg already accepted the second patch into his testing tree,
> > > > I still resend it to keep the patch integrity.
> > > 
> > > Why?  This is already in 2.6.18-rc3.
> > I checked 2.6.18-rc3 and it doesn't include the patch of pci_regs.h.
> 
> I just looked, and it is there.  Look at git commit
> 6f0312fd7e0e6f96fd847b0b2e1e0d2d2e8ef89d to see it.
I downloaded 2.6.18-rc3 tarball from http://www.kernel.org directly.
Perhaps you mean the git tree, not 2.6.18-rc3?

> 
> > > Please redo the whole series against 2.6.18-rc3, not 2.6.17, otherwise
> > > it's a pain to forward port...
> > The patches could be applied to 2.6.18-rc3 cleanly. There is no any
> > confliction and I tested them under 2.6.18-rc3.
> 
> Based on the above statement, I'm not so sure I believe that :)
> 
> > Is it necessary to rebase to 2.6.18-rc3?
> 
> You should at least regenerate them, yes.
I couldn't get git tree, but I could rebase my patches against
2.6.18-rc3, and delete the pci_reg patch. Is it ok for you?

Thanks,
Yanmin

  reply	other threads:[~2006-07-31  6:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  3:00 [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-31  3:10 ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Zhang, Yanmin
2006-07-31  3:14   ` [PATCH 3/5] PCI-Express AER implemetation: export pcie_port_bus_type Zhang, Yanmin
2006-07-31  3:22     ` [PATCH 4/5] PCI-Express AER implemetation: AER core and aerdriver Zhang, Yanmin
2006-07-31  3:30       ` [PATCH 5/5] PCI-Express AER implemetation: pcie_portdrv error handler Zhang, Yanmin
2006-07-31  4:00   ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Greg KH
2006-07-31  4:38     ` Zhang, Yanmin
2006-07-31  5:06       ` Greg KH
2006-07-31  6:40         ` Zhang, Yanmin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-12  7:10 [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-12  7:16 ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Zhang, Yanmin
2006-07-14  5:25 ` [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-14  5:27   ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h 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=1154328033.27051.60.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;
as well as URLs for NNTP newsgroup(s).