public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Julia Lawall <Julia.Lawall@lip6.fr>
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	devel@driverdev.osuosl.org, pmchba@pmcs.com
Subject: Re: [PATCH 0/7] fix typo
Date: Tue, 17 May 2016 15:07:37 +0000	[thread overview]
Message-ID: <874m9wpvt2.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1463495926-13728-1-git-send-email-Julia.Lawall@lip6.fr> (Julia Lawall's message of "Tue, 17 May 2016 16:38:39 +0200")

Julia Lawall <Julia.Lawall@lip6.fr> writes:

> firmare -> firmware
>
> ---
>
>  drivers/media/dvb-frontends/mn88473.c       |    2 +-
>  drivers/net/wireless/ath/ath6kl/core.h      |    2 +-
>  drivers/net/wireless/marvell/mwifiex/pcie.c |    2 +-

It would be good to know in advance what tree you are planning to submit
these for. For example, should I take ath6kl and mwifiex patches or
someone else?

-- 
Kalle Valo

  parent reply	other threads:[~2016-05-17 15:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 14:38 [PATCH 0/7] fix typo Julia Lawall
2016-05-17 14:38 ` [PATCH 1/7] snic: " Julia Lawall
2016-05-20  2:21   ` Martin K. Petersen
2016-05-17 14:38 ` [PATCH 2/7] [media] mn88473: " Julia Lawall
2016-05-17 14:38 ` [PATCH 3/7] [media] mn88472: " Julia Lawall
2016-05-17 14:38 ` [PATCH 4/7] staging: wilc1000: " Julia Lawall
2016-05-17 14:38 ` [PATCH 5/7] pm8001: " Julia Lawall
2016-05-17 14:55   ` Jinpu Wang
2016-05-17 14:38 ` [PATCH 6/7] ath6kl: " Julia Lawall
2016-05-28  8:22   ` [6/7] " Kalle Valo
2016-05-17 14:38 ` [PATCH 7/7] mwifiex: " Julia Lawall
2016-06-04 15:11   ` [7/7] " Kalle Valo
2016-05-17 15:07 ` Kalle Valo [this message]
2016-05-17 15:08   ` [PATCH 0/7] " Julia Lawall
2016-05-17 15:19     ` 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=874m9wpvt2.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=Julia.Lawall@lip6.fr \
    --cc=devel@driverdev.osuosl.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pmchba@pmcs.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