From: Jean Delvare <khali@linux-fr.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Seth Heasley <seth.heasley@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 2.6.35.4] irq: irq and pci_ids patch for Intel Patsburg
Date: Sat, 16 Oct 2010 08:40:18 +0200 [thread overview]
Message-ID: <20101016084018.58671452@endymion.delvare> (raw)
In-Reply-To: <20101015125428.01120a8d@jbarnes-desktop>
On Fri, 15 Oct 2010 12:54:28 -0700, Jesse Barnes wrote:
> On Mon, 4 Oct 2010 13:27:14 -0700
> Seth Heasley <seth.heasley@intel.com> wrote:
> > This patch updates the defines for Intel devices in include/linux/pci_ids.h, referenced in arch/x86/pci/irq.c and drivers/i2c/busses/i2c-i801.c, reflecting approved legal branding, and using fuller code-names for products under development.
> >
> > Signed-off-by: Seth Heasley <seth.heasley@intel.com>
>
> Applied this update, thanks.
>
> Note that going forward I don't expect (or want!) patches to convert
> the development names into marketing names. We should just add new
> stuff with the development names (before the product ships) and leave
> them that way to avoid unnecessary churn.
Fine with me, as long as it is the actual names and not obscure
3-letter shortcuts.
--
Jean Delvare
prev parent reply other threads:[~2010-10-16 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 23:06 [PATCH 2.6.35.4] irq: irq and pci_ids patch for Intel Seth Heasley
[not found] ` <201009241606.11840.seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2010-09-25 11:30 ` Jean Delvare
[not found] ` <20100925133039.75e9ac71-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-09-25 15:13 ` Heasley, Seth
2010-10-04 20:27 ` [PATCH 2.6.35.4] irq: irq and pci_ids patch for Intel Patsburg Seth Heasley
2010-10-05 6:57 ` Jean Delvare
[not found] ` <201010041327.15170.seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2010-10-15 19:54 ` Jesse Barnes
2010-10-16 6:40 ` Jean Delvare [this message]
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=20101016084018.58671452@endymion.delvare \
--to=khali@linux-fr.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@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