[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZedOldNSTdKWCgVD@smile.fi.intel.com>
Date: Tue, 5 Mar 2024 18:55:49 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Mateusz Jończyk <mat.jonczyk@...pl>,
Mario Limonciello <mario.limonciello@....com>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v1 1/1] x86/rtc: Remove unused intel-mid.h
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
Powered by blists - more mailing lists