* Greg KH <[email protected]> wrote: > How about you drop this one patch, and I'll keep it, as it goes along > with the other 2 patches in his series, and I'll make sure to check if > I have future pci quirk patches that affect the x86/ directory. > > Sound reasonable? sure enough - dropped. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [patch 0/3] use dev_printk in PCI quirks
- From: [email protected]
- [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: [email protected]
- Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: Ingo Molnar <[email protected]>
- Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: Andrew Morton <[email protected]>
- Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: Greg KH <[email protected]>
- Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: Ingo Molnar <[email protected]>
- Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- From: Greg KH <[email protected]>
- [patch 0/3] use dev_printk in PCI quirks
- Prev by Date: Re: [PATCH 18/19] move _set_gate and its users to a common location
- Next by Date: Re: Major regression on hackbench with SLUB (more numbers)
- Previous by thread: Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
- Next by thread: [PATCH 1/4] x86: fix jprobe_saved_sp handling
- Index(es):
 |