mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: "Heasley, Seth" <seth.heasley@intel.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Ralston, James D" <james.d.ralston@intel.com>
Subject: Re: [PATCH 1/1] i2c: iSMT SMBus patch for Intel Avoton DeviceIDs
Date: Tue, 26 Feb 2013 06:38:36 -0500	[thread overview]
Message-ID: <20130226113836.GA20780@hmsreliant.think-freely.org> (raw)
In-Reply-To: <DEC3922D1904474A8862C7BFF516EA9A7115EA33@ORSMSX101.amr.corp.intel.com>

On Tue, Feb 26, 2013 at 02:08:35AM +0000, Heasley, Seth wrote:
> >> The difference here is that the S1200 name is already publicly released,
> >whereas the naming for Avoton hasn't been announced.
> >>
> >Do you know when the announcement will be?  Is it sufficiently soon that we
> >can just wait for it?
> 
> I don't, and actually couldn't tell you if I did.  The codename usage is consistent with how we deal with all products since the patches have to go in well in advance of product launch.
> 
Meh, ok, I guess we cal always fix it up when the product has an actual name

Acked-by: Neil Horman <nhorman@tuxdriver.com>

> -Seth
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

  reply	other threads:[~2013-02-26 11:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 22:30 Seth Heasley
2013-02-21 21:37 ` Neil Horman
2013-02-21 22:19   ` Heasley, Seth
2013-02-21 23:26     ` Neil Horman
2013-02-26  2:08       ` Heasley, Seth
2013-02-26 11:38         ` Neil Horman [this message]
2013-03-22 10:15 ` Wolfram Sang

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=20130226113836.GA20780@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=james.d.ralston@intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seth.heasley@intel.com \
    --cc=wsa@the-dreams.de \
    /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®