All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Mateusz Jończyk" <mat.jonczyk@o2.pl>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	linux-kernel@vger.kernel.org,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v1 1/1] x86/rtc: Remove unused intel-mid.h
Date: Tue, 5 Mar 2024 18:55:49 +0200	[thread overview]
Message-ID: <ZedOldNSTdKWCgVD@smile.fi.intel.com> (raw)
In-Reply-To: <77d906e6-ff0c-489a-bc2b-5342196eb4b1@intel.com>

On Tue, Mar 05, 2024 at 08:43:47AM -0800, Dave Hansen wrote:
> On 3/5/24 08:36, Andy Shevchenko wrote:
> >> Ahh, thanks for the context.  Any chance you could share that up front
> >> next time? 😉
> > Hmm... I'm not sure how. If it's a cover letter, then it requires a series,
> > which seems an overkill, commenting on a single patch sounds a bit weird to
> > me.
> 
> I honestly don't care how you do it.  You could send all the patches in
> a series and ask the individual maintainers to pick them up
> individually.  Or send cc all the maintainers and ask _one_ of them to
> pick up all of the patches.  Or just mention in the changelog of the
> singleton patch that it's part of a (slightly) larger effort, then Link:
> over to the other related ones.

Got it.

> Seriously, the only way to go wrong is to just pretend that this patch
> *is* a singleton when it's not.

But technically speaking it is completely independent. TBH it is the _first_
time I ever got such a request from a maintainer. But okay, sending in a series
to be picked up separately sounds like in use: I have heard about such series
more than once.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-03-05 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 16:10 [PATCH v1 1/1] x86/rtc: Remove unused intel-mid.h Andy Shevchenko
2024-03-05 16:21 ` Dave Hansen
2024-03-05 16:31   ` Andy Shevchenko
2024-03-05 16:34     ` Dave Hansen
2024-03-05 16:36       ` Andy Shevchenko
2024-03-05 16:43         ` Dave Hansen
2024-03-05 16:55           ` Andy Shevchenko [this message]
2024-03-25 12:48         ` Andy Shevchenko

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=ZedOldNSTdKWCgVD@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mat.jonczyk@o2.pl \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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.