From: Joel Stanley <joel@jms.id.au> To: Greg KH <gregkh@linuxfoundation.org> Cc: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>, Andrew Jeffery <andrew@aj.id.au>, Arnd Bergmann <arnd@arndb.de>, Jean Delvare <jdelvare@suse.com>, Guenter Roeck <linux@roeck-us.net>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org, devicetree <devicetree@vger.kernel.org>, linux-hwmon@vger.kernel.org, Linux ARM <linux-arm-kernel@lists.infradead.org>, OpenBMC Maillist <openbmc@lists.ozlabs.org>, Jae Hyun Yoo <jae.hyun.yoo@intel.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Jeremy Kerr <jk@ozlabs.org> Subject: Re: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Date: Thu, 11 Jan 2018 00:28:48 -0800 [thread overview] Message-ID: <CACPK8Xe9Jti8S2px=QOcSMA2v+TZ4eGDGQND4qmBUBXeBpsBZQ@mail.gmail.com> (raw) In-Reply-To: <20180111073038.GA3600@kroah.com> On Wed, Jan 10, 2018 at 11:30 PM, Greg KH <gregkh@linuxfoundation.org> wrote: > On Wed, Jan 10, 2018 at 01:46:34PM -0800, Jae Hyun Yoo wrote: >> Thanks for your pointing it out and I totally agree with you. Actually, we >> are preparing 4.13 update for now and an another update will be followed up. >> As I answered above, I'll rebase this patch set onto the latest kernel.org >> mainline. Sorry for my misunderstanding of upstream process. > > 4.13? Why that kernel? It too is obsolete and insecure and > unsupported. It contains support for our hardware that I have integrated from work in progress patches and upstream commits. The OpenBMC project, with myself as the kernel maintainer, have intentions to regularly move to upstream releases. This takes time and effort. This time and effort is balanced with submitting our drivers upstream. > What keeps you all from just always tracking the latest tree from Linus? Linus' tree does not contain all of the drivers required to boot systems. Many of them are still under review on lkml, and others still require rewrite from the vendor tree. > What is in your tree that is not upstream that requires you to have a > kernel tree at all? We have PECI, video compression, crypto, USB CDC, DRM (graphics), serial GPIO, LPC mailbox for the ASPEED SoC. Another silicon vendor has recently joined the project and that brings an entire SoC that is not upstream. We have patches on the ARM that are under review for this SoC, with more drivers undergoing cleanup in order to submit them to the relevant maintainers. > > And if you do have out-of-tree code, why not use a process that makes it > trivial to update the base kernel version so that you can keep up to > date very easily? (hint, just using 'git' is not a good way to do > this...) We have a process that we've been developing under for the past few years. I find git to be a great tool for managing Linux kernel trees. What would you recommend for managing kernel trees? Cheers, Joel
WARNING: multiple messages have this Message-ID (diff)
From: joel@jms.id.au (Joel Stanley) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Date: Thu, 11 Jan 2018 00:28:48 -0800 [thread overview] Message-ID: <CACPK8Xe9Jti8S2px=QOcSMA2v+TZ4eGDGQND4qmBUBXeBpsBZQ@mail.gmail.com> (raw) In-Reply-To: <20180111073038.GA3600@kroah.com> On Wed, Jan 10, 2018 at 11:30 PM, Greg KH <gregkh@linuxfoundation.org> wrote: > On Wed, Jan 10, 2018 at 01:46:34PM -0800, Jae Hyun Yoo wrote: >> Thanks for your pointing it out and I totally agree with you. Actually, we >> are preparing 4.13 update for now and an another update will be followed up. >> As I answered above, I'll rebase this patch set onto the latest kernel.org >> mainline. Sorry for my misunderstanding of upstream process. > > 4.13? Why that kernel? It too is obsolete and insecure and > unsupported. It contains support for our hardware that I have integrated from work in progress patches and upstream commits. The OpenBMC project, with myself as the kernel maintainer, have intentions to regularly move to upstream releases. This takes time and effort. This time and effort is balanced with submitting our drivers upstream. > What keeps you all from just always tracking the latest tree from Linus? Linus' tree does not contain all of the drivers required to boot systems. Many of them are still under review on lkml, and others still require rewrite from the vendor tree. > What is in your tree that is not upstream that requires you to have a > kernel tree at all? We have PECI, video compression, crypto, USB CDC, DRM (graphics), serial GPIO, LPC mailbox for the ASPEED SoC. Another silicon vendor has recently joined the project and that brings an entire SoC that is not upstream. We have patches on the ARM that are under review for this SoC, with more drivers undergoing cleanup in order to submit them to the relevant maintainers. > > And if you do have out-of-tree code, why not use a process that makes it > trivial to update the base kernel version so that you can keep up to > date very easily? (hint, just using 'git' is not a good way to do > this...) We have a process that we've been developing under for the past few years. I find git to be a great tool for managing Linux kernel trees. What would you recommend for managing kernel trees? Cheers, Joel
next prev parent reply other threads:[~2018-01-11 8:28 UTC|newest] Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-09 22:31 [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 1/6] Documentation: dt-bindings: Add Aspeed PECI Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 2/6] ARM: dts: aspeed: peci: " Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 3/6] drivers/misc: Add driver for Aspeed PECI and generic PECI headers Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-10 10:18 ` Greg KH 2018-01-10 10:18 ` Greg KH 2018-01-10 10:18 ` Greg KH 2018-01-10 19:32 ` Jae Hyun Yoo 2018-01-10 19:32 ` Jae Hyun Yoo 2018-01-11 9:02 ` Benjamin Herrenschmidt 2018-01-11 9:02 ` Benjamin Herrenschmidt 2018-01-11 9:02 ` Benjamin Herrenschmidt 2018-01-11 20:33 ` Jae Hyun Yoo 2018-01-11 20:33 ` Jae Hyun Yoo 2018-01-10 10:20 ` Greg KH 2018-01-10 10:20 ` Greg KH 2018-01-10 10:20 ` Greg KH 2018-01-10 19:34 ` Jae Hyun Yoo 2018-01-10 19:34 ` Jae Hyun Yoo 2018-01-10 11:55 ` Arnd Bergmann 2018-01-10 11:55 ` Arnd Bergmann 2018-01-10 11:55 ` Arnd Bergmann 2018-01-10 23:11 ` Jae Hyun Yoo 2018-01-10 23:11 ` Jae Hyun Yoo 2018-01-11 9:06 ` Benjamin Herrenschmidt 2018-01-11 9:06 ` Benjamin Herrenschmidt 2018-01-11 9:06 ` Benjamin Herrenschmidt 2018-01-11 20:42 ` Jae Hyun Yoo 2018-01-11 20:42 ` Jae Hyun Yoo 2018-01-11 20:42 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 4/6] Documentation: dt-bindings: Add a generic PECI hwmon Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-10 12:20 ` Arnd Bergmann 2018-01-10 12:20 ` Arnd Bergmann 2018-01-10 12:20 ` Arnd Bergmann 2018-01-10 23:20 ` Jae Hyun Yoo 2018-01-10 23:20 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 5/6] Documentation: hwmon: " Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-09 22:31 ` [PATCH linux dev-4.10 6/6] drivers/hwmon: Add a driver for " Jae Hyun Yoo 2018-01-09 22:31 ` Jae Hyun Yoo 2018-01-10 12:29 ` Arnd Bergmann 2018-01-10 12:29 ` Arnd Bergmann 2018-01-10 12:29 ` Arnd Bergmann 2018-01-10 23:45 ` Jae Hyun Yoo 2018-01-10 23:45 ` Jae Hyun Yoo 2018-01-11 13:22 ` Arnd Bergmann 2018-01-11 13:22 ` Arnd Bergmann 2018-01-11 13:22 ` Arnd Bergmann 2018-01-11 20:49 ` Jae Hyun Yoo 2018-01-11 20:49 ` Jae Hyun Yoo 2018-01-10 21:47 ` [linux, dev-4.10, " Guenter Roeck 2018-01-10 21:47 ` Guenter Roeck 2018-01-11 19:47 ` Jae Hyun Yoo 2018-01-11 19:47 ` Jae Hyun Yoo 2018-01-11 19:47 ` Jae Hyun Yoo 2018-01-11 21:40 ` Guenter Roeck 2018-01-11 21:40 ` Guenter Roeck 2018-01-11 22:18 ` Andrew Lunn 2018-01-11 22:18 ` Andrew Lunn 2018-01-11 22:18 ` Andrew Lunn 2018-01-11 23:14 ` Jae Hyun Yoo 2018-01-11 23:14 ` Jae Hyun Yoo 2018-01-11 23:53 ` Andrew Lunn 2018-01-11 23:53 ` Andrew Lunn 2018-01-12 0:26 ` Jae Hyun Yoo 2018-01-12 0:26 ` Jae Hyun Yoo 2018-01-11 23:03 ` Jae Hyun Yoo 2018-01-11 23:03 ` Jae Hyun Yoo 2018-01-11 23:03 ` Jae Hyun Yoo 2018-01-10 10:17 ` [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Greg KH 2018-01-10 10:17 ` Greg KH 2018-01-10 10:17 ` Greg KH 2018-01-10 19:14 ` Jae Hyun Yoo 2018-01-10 19:14 ` Jae Hyun Yoo 2018-01-10 19:17 ` Greg KH 2018-01-10 19:17 ` Greg KH 2018-01-10 19:17 ` Greg KH 2018-01-10 19:30 ` Jae Hyun Yoo 2018-01-10 19:30 ` Jae Hyun Yoo 2018-01-10 20:27 ` Greg KH 2018-01-10 20:27 ` Greg KH 2018-01-10 20:27 ` Greg KH 2018-01-10 21:46 ` Jae Hyun Yoo 2018-01-10 21:46 ` Jae Hyun Yoo 2018-01-10 21:46 ` Jae Hyun Yoo 2018-01-11 7:30 ` Greg KH 2018-01-11 7:30 ` Greg KH 2018-01-11 8:28 ` Joel Stanley [this message] 2018-01-11 8:28 ` Joel Stanley 2018-01-11 8:28 ` Joel Stanley 2018-01-11 8:41 ` Greg KH 2018-01-11 8:41 ` Greg KH 2018-01-11 8:41 ` Greg KH 2018-01-11 9:17 ` Arnd Bergmann 2018-01-11 9:17 ` Arnd Bergmann 2018-01-11 9:17 ` Arnd Bergmann 2018-01-11 9:17 ` Arnd Bergmann 2018-01-11 9:21 ` Benjamin Herrenschmidt 2018-01-11 9:21 ` Benjamin Herrenschmidt 2018-01-11 9:21 ` Benjamin Herrenschmidt 2018-01-11 8:56 ` Benjamin Herrenschmidt 2018-01-11 8:56 ` Benjamin Herrenschmidt 2018-01-11 9:59 ` Greg KH 2018-01-11 9:59 ` Greg KH 2018-01-11 9:59 ` Greg KH 2018-01-11 20:49 ` Benjamin Herrenschmidt 2018-01-11 20:49 ` Benjamin Herrenschmidt 2018-01-11 20:49 ` Benjamin Herrenschmidt 2018-01-11 19:54 ` Jae Hyun Yoo 2018-01-11 19:54 ` Jae Hyun Yoo
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='CACPK8Xe9Jti8S2px=QOcSMA2v+TZ4eGDGQND4qmBUBXeBpsBZQ@mail.gmail.com' \ --to=joel@jms.id.au \ --cc=andrew@aj.id.au \ --cc=arnd@arndb.de \ --cc=benh@kernel.crashing.org \ --cc=devicetree@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=jae.hyun.yoo@intel.com \ --cc=jae.hyun.yoo@linux.intel.com \ --cc=jdelvare@suse.com \ --cc=jk@ozlabs.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-hwmon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@roeck-us.net \ --cc=openbmc@lists.ozlabs.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.