Linux wireless drivers development
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 1/2] MAINTAINERS: add ath10k
Date: Mon, 22 Jul 2013 10:04:41 -0700	[thread overview]
Message-ID: <1374512681.2061.53.camel@joe-AO722> (raw)
In-Reply-To: <87zjtewmzg.fsf@kamboji.qca.qualcomm.com>

On Mon, 2013-07-22 at 19:58 +0300, Kalle Valo wrote:
> Joe Perches <joe@perches.com> writes:
> 
> > On Mon, 2013-07-22 at 12:32 +0300, Kalle Valo wrote:
> >> I forgot to add an entry to MAINTAINERS when submitting the driver.
> > []
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> > []
> >> +QUALCOMM ATHEROS ATH10K WIRELESS DRIVER
> >
> > It's odd to not find ATH6KL next to ATH10K.
> 
> I was wondering the same, but decided to put the entries in alphabetical
> order still.
> 
> > Maybe it's time to rename all the ATH sections
> > to make them QUALCOMM?
> 
> Maybe, but does it really matter?

Only to those that actually read the MAINTAINERS
file instead of using tools to search it.

> Changing the MAINTAINERS file just
> creates unnecessary conficts for git merges.

Those are always trivially resolved if they
ever really occur.

It's not a big deal, just wanted to note it.



  reply	other threads:[~2013-07-22 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  9:32 [PATCH 0/2] MAINTAINERS: ath10k and ath6kl updates Kalle Valo
2013-07-22  9:32 ` [PATCH 1/2] MAINTAINERS: add ath10k Kalle Valo
2013-07-22 14:44   ` Joe Perches
2013-07-22 16:58     ` Kalle Valo
2013-07-22 17:04       ` Joe Perches [this message]
2013-07-22  9:32 ` [PATCH 2/2] MAINTAINERS: update ath6kl git location Kalle Valo
2013-07-23  9:26 ` [PATCH 0/2] MAINTAINERS: ath10k and ath6kl updates Kalle Valo

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=1374512681.2061.53.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox