All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Daniel J Blueman <daniel@numascale-asia.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Multiple patch authors
Date: Thu, 25 Oct 2012 17:23:28 +0200	[thread overview]
Message-ID: <20121025152328.GE308@x1.osrc.amd.com> (raw)
In-Reply-To: <50894F8E.9060706@zytor.com>

On Thu, Oct 25, 2012 at 07:41:18AM -0700, H. Peter Anvin wrote:
> Not necessarily. It is actually better to have more specific tags for
> different situations.

Do you have any concrete in mind? I mean, we can hash them out now and
put them in the documentation and be done with it.

> There is a reason why tip-bot accepts any tag ending in -by: ...

Fair enough.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2012-10-25 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  8:32 [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains Daniel J Blueman
2012-10-25 11:03 ` Borislav Petkov
2012-10-25 11:56   ` Ingo Molnar
2012-10-25 13:59     ` Multiple patch authors (was: Re: [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains) Borislav Petkov
2012-10-25 14:32       ` Multiple patch authors H. Peter Anvin
2012-10-25 14:36         ` Borislav Petkov
2012-10-25 14:41           ` H. Peter Anvin
2012-10-25 15:23             ` Borislav Petkov [this message]
2012-10-29  6:17   ` [PATCH v3] Add support for AMD64 EDAC on multiple PCI domains Daniel J Blueman
2012-10-29  8:54     ` Daniel J Blueman
2012-10-29 10:32       ` Borislav Petkov
2012-10-31  5:23         ` Daniel J Blueman

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=20121025152328.GE308@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@numascale-asia.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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 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.