On Thu, Feb 21, 2013 at 02:30:43PM -0800, Seth Heasley wrote:
> This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton SOC.
>
> Signed-off-by: Seth Heasley
Applied to for-current, thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Tue, Feb 26, 2013 at 02:08:35AM +, 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 f
>> 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 u
On Thu, Feb 21, 2013 at 10:19:48PM +, Heasley, Seth wrote:
> Hi Neil,
>
> >> This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton
> >SOC.
> >>
> >> Signed-off-by: Seth Heasley
> >Is there a part number (I.e. S1200) that we can use in the name, rather than
> >the project co
Hi Neil,
>> This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton
>SOC.
>>
>> Signed-off-by: Seth Heasley
>Is there a part number (I.e. S1200) that we can use in the name, rather than
>the project code name? That would seem to be more in keeping with the
>previous naming schee
On Thu, Feb 21, 2013 at 02:30:43PM -0800, Seth Heasley wrote:
> This patch adds the iSMT SMBus Controller DeviceIDs for the Intel Avoton SOC.
>
> Signed-off-by: Seth Heasley
Is there a part number (I.e. S1200) that we can use in the name, rather than the
project code name? That would seem to be
6 matches
Mail list logo