Message ID | CACPK8XfCpgjAwMeoyhcZqgqtXO=-wtpuB2kwsogvBnd1VzynDg@mail.gmail.com |
---|---|
State | Not Applicable, archived |
Headers | show |
Series | [GIT,PULL] FSI changes for 5.3 | expand |
On Wed, 2019-07-03 at 03:39 +0000, Joel Stanley wrote: > Hello Greg, > > We've not had a MAINAINERS entry for drivers/fsi, so this fixes that. It names > Jeremy and I as maintainers, so if it works for you we will send pull requests > to you each cycle. Ack. I no longer work for IBM and thus cannot handle that subsystem anymore. > I realise this one is a bit late, but please consider including so we have a > clear path for future submissions from 5.3 on. > > This pull request contains two code changes. One touches hwmon and has an ack > from Guenter as the hwmon maintainer. > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git tags/fsi-for-5.3 > > for you to fetch changes up to 371975b0b07520c85098652d561639837a60a905: > > fsi/core: Fix error paths on CFAM init (2019-07-03 10:42:53 +0930) > > ---------------------------------------------------------------- > FSI changes for 5.3 > > - Add MAINTAINERS entry. There is now a git tree and a mailing > list/patchwork for collecting FSI patches > > - Bug fix for error driver registration error paths > > - Correction for the OCC hwmon driver to meet the spec > > ---------------------------------------------------------------- > Eddie James (1): > OCC: FSI and hwmon: Add sequence numbering > > Jeremy Kerr (1): > fsi/core: Fix error paths on CFAM init > > Joel Stanley (1): > MAINTAINERS: Add FSI subsystem > > MAINTAINERS | 13 +++++++++++++ > drivers/fsi/fsi-core.c | 32 ++++++++++++++++++++------------ > drivers/fsi/fsi-occ.c | 15 ++++++++++++--- > drivers/hwmon/occ/common.c | 4 ++-- > drivers/hwmon/occ/common.h | 1 + > 5 files changed, 48 insertions(+), 17 deletions(-)
On Wed, Jul 03, 2019 at 03:39:17AM +0000, Joel Stanley wrote: > Hello Greg, > > We've not had a MAINAINERS entry for drivers/fsi, so this fixes that. It names > Jeremy and I as maintainers, so if it works for you we will send pull requests > to you each cycle. > > I realise this one is a bit late, but please consider including so we have a > clear path for future submissions from 5.3 on. > > This pull request contains two code changes. One touches hwmon and has an ack > from Guenter as the hwmon maintainer. > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git tags/fsi-for-5.3 Pulled and pushed out, thanks for doing this! greg k-h
On Wed, 3 Jul 2019 at 05:32, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > > On Wed, 2019-07-03 at 03:39 +0000, Joel Stanley wrote: > > Hello Greg, > > > > We've not had a MAINAINERS entry for drivers/fsi, so this fixes that. It names > > Jeremy and I as maintainers, so if it works for you we will send pull requests > > to you each cycle. > > Ack. I no longer work for IBM and thus cannot handle that subsystem > anymore. Stephen, can you swap out ben's fsi tree in linux-next for this one: git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git Branch is 'next'. Cheers, Joel
Hi Joel, On Thu, 4 Jul 2019 06:03:18 +0000 Joel Stanley <joel@jms.id.au> wrote: > > On Wed, 3 Jul 2019 at 05:32, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote: > > > > On Wed, 2019-07-03 at 03:39 +0000, Joel Stanley wrote: > > > > > > We've not had a MAINAINERS entry for drivers/fsi, so this fixes that. It names > > > Jeremy and I as maintainers, so if it works for you we will send pull requests > > > to you each cycle. > > > > Ack. I no longer work for IBM and thus cannot handle that subsystem > > anymore. > > Stephen, can you swap out ben's fsi tree in linux-next for this one: > > git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git > > Branch is 'next'. There is no "next" branch in that tree, so for now I have used the master branch. I have replaced Ben with you and Jeremy as contacts. Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgement of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.
On Thu, 4 Jul 2019 at 21:32, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > Hi Joel, > > On Thu, 4 Jul 2019 06:03:18 +0000 Joel Stanley <joel@jms.id.au> wrote: > > Stephen, can you swap out ben's fsi tree in linux-next for this one: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git > > > > Branch is 'next'. > > There is no "next" branch in that tree, so for now I have used the > master branch. I have replaced Ben with you and Jeremy as contacts. Thanks. There is a next branch now, please take that instead. Cheers, Joel
Hi Joel, On Mon, 8 Jul 2019 03:41:40 +0000 Joel Stanley <joel@jms.id.au> wrote: > > Thanks. There is a next branch now, please take that instead. Done from tomorrow.