All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <rric@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Borislav Petkov <bp@suse.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Doug Thompson <dougthompson@xmission.com>,
	Johannes Thumshirn <johannes.thumshirn@men.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-edac@vger.kernel.org,
	Aristeu Rozanski Filho <arozansk@redhat.com>
Subject: Re: [GIT PULL] mpc85xx_edac changes for 3.13
Date: Thu, 14 Nov 2013 13:13:50 +0100	[thread overview]
Message-ID: <20131114121350.GT7429@rric.localhost> (raw)
In-Reply-To: <20131114112418.GH4960@pd.tnic>

On 14.11.13 12:24:18, Borislav Petkov wrote:
> On Thu, Nov 14, 2013 at 09:18:43AM -0200, Mauro Carvalho Chehab wrote:
> > So, in practice, Borislav was working as a maintainer for amd64 EDAC
> > patches, and I working mainly as Intel EDAC maintainer. The (few)
> > other arm EDAC patches were either coming via my tree or via Boris
> > tree, depending on who got them first.
> 
> Yeah, and I think this has worked pretty good in the past so if you want
> to, we can continue the same thing of sharing the load on EDAC patches
> and we both do interim maintainers until Doug steps in.
> 
> And since it won't change any workflow for Linus, he's probably fine
> with it too.
> 
> Yes, no? Comments?

There will be some upcomming arm/arm64 specific changes which might
effect also the core driver in the future. I would be willing to
collect and send these ones upstream in coordination with you.

Thanks,

-Robert

  reply	other threads:[~2013-11-14 12:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:19 [GIT PULL] mpc85xx_edac changes for 3.13 Johannes Thumshirn
2013-11-14  5:41 ` Linus Torvalds
2013-11-14  5:47   ` Greg Kroah-Hartman
2013-11-14  9:20     ` Borislav Petkov
2013-11-14 11:18       ` Mauro Carvalho Chehab
2013-11-14 11:24         ` Borislav Petkov
2013-11-14 12:13           ` Robert Richter [this message]
2013-11-14 14:21           ` Johannes Thumshirn
2013-11-14 17:08             ` Mauro Carvalho Chehab
2013-11-14 18:30             ` Borislav Petkov

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=20131114121350.GT7429@rric.localhost \
    --to=rric@kernel.org \
    --cc=arozansk@redhat.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dougthompson@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.thumshirn@men.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=torvalds@linux-foundation.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: link
Be 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.