Re: [PATCH 1/3] staging: rtlwifi: Fix "Trafic"->"Traffic"

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Greg KH <gregkh@linuxfoundation.org>
To: Sabin Mihai Rapan <sabin.rapan@gmail.com>
Cc: Larry.Finger@lwfinger.net, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: rtlwifi: Fix "Trafic"->"Traffic"
Date: Fri, 01 Jun 2018 06:07:40 +0000	[thread overview]
Message-ID: <20180601060740.GA25648@kroah.com> (raw)
In-Reply-To: <438a4c2c-5bf8-8149-aaff-1f58493cdc79@gmail.com>

On Thu, May 31, 2018 at 09:48:23PM +0200, Sabin Mihai Rapan wrote:
> In the first patch series I forgot to CC linux-kernel@vger.kernel.org and
> assumed (wrongly) that the patch series will be ignored.
> In an attempt to fix that, I sent the second patch series with proper
> CC added. I should have sent it as a reply to the first one and version
> it.
> I will do as you said and resend the patch series.

linux-kernel does not care about staging patches :)

Please use scripts/get_maintainers.pl to determine who to cc: and the
proper mailing list to use.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)

From: Greg KH <gregkh@linuxfoundation.org>
To: Sabin Mihai Rapan <sabin.rapan@gmail.com>
Cc: Larry.Finger@lwfinger.net, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: rtlwifi: Fix "Trafic"->"Traffic"
Date: Fri, 1 Jun 2018 08:07:40 +0200	[thread overview]
Message-ID: <20180601060740.GA25648@kroah.com> (raw)
In-Reply-To: <438a4c2c-5bf8-8149-aaff-1f58493cdc79@gmail.com>

On Thu, May 31, 2018 at 09:48:23PM +0200, Sabin Mihai Rapan wrote:
> In the first patch series I forgot to CC linux-kernel@vger.kernel.org and
> assumed (wrongly) that the patch series will be ignored.
> In an attempt to fix that, I sent the second patch series with proper
> CC added. I should have sent it as a reply to the first one and version
> it.
> I will do as you said and resend the patch series.

linux-kernel does not care about staging patches :)

Please use scripts/get_maintainers.pl to determine who to cc: and the
proper mailing list to use.

thanks,

greg k-h

next prev parent reply	other threads:[~2018-06-01  6:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 11:03 [PATCH 1/3] staging: rtlwifi: Fix "Trafic"->"Traffic" Sabin Mihai Rapan
2018-05-31 11:03 ` Sabin Mihai Rapan
2018-05-31 11:03 ` [PATCH 2/3] staging: rtlwifi: Fix "writen"->"written" Sabin Mihai Rapan
2018-05-31 11:03   ` Sabin Mihai Rapan
2018-05-31 11:03 ` [PATCH 3/3] staging: rtlwifi: Fix "Alwyas"->"Always" Sabin Mihai Rapan
2018-05-31 11:03   ` Sabin Mihai Rapan
2018-05-31 16:57 ` [PATCH 1/3] staging: rtlwifi: Fix "Trafic"->"Traffic" Greg KH
2018-05-31 16:57   ` Greg KH
2018-05-31 19:48   ` Sabin Mihai Rapan
2018-05-31 19:48     ` Sabin Mihai Rapan
2018-06-01  6:07     ` Greg KH [this message]
2018-06-01  6:07       ` Greg KH
2018-06-02  9:04       ` [PATCH v2 " Sabin Mihai Rapan
2018-06-02  9:04         ` Sabin Mihai Rapan
2018-06-02  9:04         ` [PATCH v2 2/3] staging: rtlwifi: Fix "writen"->"written" Sabin Mihai Rapan
2018-06-02  9:04           ` Sabin Mihai Rapan
2018-06-02  9:04         ` [PATCH v2 3/3] staging: rtlwifi: Fix "Alwyas"->"Always" Sabin Mihai Rapan
2018-06-02  9:04           ` Sabin Mihai Rapan

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=20180601060740.GA25648@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sabin.rapan@gmail.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 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.