netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: W_Armin@gmx.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2] Fix various coding-style issues and improve printk() usage
Date: Sun, 24 May 2020 19:33:17 -0700 (PDT)	[thread overview]
Message-ID: <20200524.193317.884228561320046464.davem@davemloft.net> (raw)
In-Reply-To: <20200524.181512.1222378110120420383.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Sun, 24 May 2020 18:15:12 -0700 (PDT)

> 
> Please repost this with a proper subsystem/driver prefix in your Subject line
> and the appropriate target GIT tree inside the [] brackets.
> 
> F.e. Subject: [PATCH v3 net] ne2k-pci: Fix various coding-style ...

Actually in this case "net-next" instead of "net" would be appropriate.

      reply	other threads:[~2020-05-25  2:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 22:27 [PATCH v2] Fix various coding-style issues and improve printk() usage Armin Wolf
2020-05-25  1:15 ` David Miller
2020-05-25  2:33   ` David Miller [this message]

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=20200524.193317.884228561320046464.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=W_Armin@gmx.de \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).