mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
	clemens@ladisch.de, rob@landley.net, lm-sensors@lm-sensors.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	andre@andrep.de
Subject: Re: [PATCH] hwmon, k10temp: Add support for AMD F16 M30h processor
Date: Wed, 12 Mar 2014 10:25:11 +0100	[thread overview]
Message-ID: <20140312102511.77faa6ff@endymion.delvare> (raw)
In-Reply-To: <531FCF3D.8020409@roeck-us.net>

On Tue, 11 Mar 2014 20:06:37 -0700, Guenter Roeck wrote:
> On 03/11/2014 02:25 PM, Aravind Gopalakrishnan wrote:
> > Adding new PCI ID to support AMD F16 M30h processor (Mullins).
> > While at it, modify Kconfig and Doc files to reflect the
> > support for newer processors
> >
> > Note: PCI ID for this processor will make it into pci_ids.h
> > as part of this patch:
> > http://marc.info/?l=linux-kernel&m=139291362126057&w=2
> > which should be pulled into 3.15 when merge window opens
> > (It currently sits in 'for-next' branch of bp.git-
> > https://git.kernel.org/cgit/linux/kernel/git/bp/bp.git/log/?h=for-next)
> >
> > Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> 
> Looks good. We'll have to see how we can apply this; probably after 3.15-rc1
> comes out. I'll put it into my -staging branch for now and pull in the other
> patch as well to make sure it compiles.

I've updated the wiki accordingly, as well as sensors-detect.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2014-03-12  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 21:25 Aravind Gopalakrishnan
2014-03-12  3:06 ` Guenter Roeck
2014-03-12  9:25   ` Jean Delvare [this message]
2014-03-12 14:34     ` Aravind Gopalakrishnan

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=20140312102511.77faa6ff@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=andre@andrep.de \
    --cc=clemens@ladisch.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rob@landley.net \
    /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®