All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] PCI: Move out pci reassigndev resource alignment out of quirk
Date: Fri, 24 Feb 2012 14:37:36 -0800	[thread overview]
Message-ID: <20120224143736.683b73e7@jbarnes-desktop> (raw)
In-Reply-To: <1329370832-2253-4-git-send-email-yinghai@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

On Wed, 15 Feb 2012 21:40:31 -0800
Yinghai Lu <yinghai@kernel.org> wrote:

> That looks like abusing quirk framework.
> 
> calling it directly in pci_add_device. or do we have good place for it?
> 
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>

Applied, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-24 22:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16  5:40 [PATCH 0/4] PCI: quirk related clean up Yinghai Lu
2012-02-16  5:40 ` [PATCH -v2 1/4] PCI: Add class support in quirk handling Yinghai Lu
2012-02-23 20:44   ` Jesse Barnes
2012-02-24  6:40     ` Yinghai Lu
2012-02-16  5:40 ` [PATCH 2/4] PCI: Specify class for quirk entry with PCI_ANY_ID Yinghai Lu
2012-02-16  5:40 ` [PATCH 3/4] PCI: Move out pci reassigndev resource alignment out of quirk Yinghai Lu
2012-02-24 22:37   ` Jesse Barnes [this message]
2012-02-16  5:40 ` [PATCH 4/4] PCI: quirk print dev name with duration Yinghai Lu
2012-02-24 22:39   ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2012-02-16  5:14 [PATCH 1/4] PCI: quirk related clean up Yinghai Lu
2012-02-16  5:14 ` [PATCH 3/4] PCI: Move out pci reassigndev resource alignment out of quirk Yinghai Lu

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=20120224143736.683b73e7@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.