mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Darren Hart <dvhart@infradead.org>
Cc: hpa@zytor.com, vadimp@mellanox.com, linux-kernel@vger.kernel.org,
	mingo@kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/platform] x86/platform/mellanox: Introduce support for Mellanox systems platform
Date: Thu, 29 Sep 2016 09:29:09 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1609290925480.21836@nanos> (raw)
In-Reply-To: <20160928232512.GA7630@f23x64.localdomain>

On Wed, 28 Sep 2016, Darren Hart wrote:
> This through me as I was trying to reconcile this series with another mellanox
> platform driver from Vadim to the drivers/platform/x86 tree as this one also
> came to the platform-driver-x86 mailing list.
> 
> There are no other entries in MAINTAINERS that use this list without files under
> drivers/platform/x86.
> 
> Thomas, HPA, Ingo, do you also use the platform-driver-x86 mailing list for
> arch/x86/platform? I had assumed this was only for drivers/platform/x86.

No. This came in via LKML.
 
> I can definitely understand how contributors might get confused.... I think I
> may have confused myself actually :-)
> 
> My two cents too late, this driver seems like it would better placed in
> drivers/platform/x86 as it isn't architectural (or SoC specific) in the same way
> most of the others in arch/x86/platform are, but instead is more akin to the
> end-product laptop drivers and such in drivers/platform/x86 which build platform
> data from DMI strings, ACPI HIDs, etc.

We still can zap it from tip/x86/platform if you want to take it through
your tree, but OTOH the merge window is close so it might be better to move
it afterwards. Either way works for me.
 
> If this isn't the right distinction between the two similarly named trees ...
> how would you like to distinguish them? I'll volunteer to get that documented
> someplace convenient to make it easier to decide what goes where.

Yes please. Documentation is always a good thing ot have.

Thanks,

	tglx

  reply	other threads:[~2016-09-29 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 21:13 [patch v6] x86/platform/mellanox: introduce " vadimp
2016-09-22 20:18 ` [tip:x86/platform] x86/platform/mellanox: Introduce " tip-bot for Vadim Pasternak
2016-09-28 23:25   ` Darren Hart
2016-09-29 13:29     ` Thomas Gleixner [this message]
2016-09-30  0:06       ` Darren Hart

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=alpine.DEB.2.20.1609290925480.21836@nanos \
    --to=tglx@linutronix.de \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=vadimp@mellanox.com \
    /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®