From: Ingo Molnar <mingo@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux PCI <linux-pci@vger.kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
Jean Delvare <jdelvare@suse.de>
Subject: Re: [PATCH v2 0/4] x86, dmi: introduce and use dmi_get_bios_year()
Date: Mon, 12 Mar 2018 09:52:40 +0100 [thread overview]
Message-ID: <20180312085240.7y6ycvzo6ns7hjzc@gmail.com> (raw)
In-Reply-To: <CAJZ5v0hZwz3fv2fBiXXTqO0E2AasphBYgX6tzUE8R-YK+wgmUw@mail.gmail.com>
* Rafael J. Wysocki <rafael@kernel.org> wrote:
> >> I can apply this or if you want to route it differently,
> >
> > I don't know how to proceed here, Ingo applied v1 and there might be
> > options like remove old and reapply new, or do a series of fixups.
> >
> > Ingo, can you suggest how to do this in the best way?
>
> AFAICS the tip workflow is that things are not rebased in there, only
> reverted if need be, and if the previous version was taken to tip,
> reverting it is not worth the hassle IMO.
>
> I'd just wait for it to be integrated and post an update on top of it
> or even on top of linux-next.
Yeah, indeed, we rebase in -tip only if absolutely necessary - and there were no
real problems with the v1 version, right?
So it would be nice to have v2 as a delta against what is already in -tip.
Thanks,
Ingo
prev parent reply other threads:[~2018-03-12 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 18:02 [PATCH v2 0/4] x86, dmi: introduce and use dmi_get_bios_year() Andy Shevchenko
2018-03-01 18:02 ` [PATCH v2 1/4] firmware: dmi_scan: Introduce the dmi_get_bios_year() helper Andy Shevchenko
2018-03-02 14:05 ` Lukas Wunner
2018-03-02 14:21 ` Andy Shevchenko
2018-03-13 10:33 ` Jean Delvare
2018-03-01 18:02 ` [PATCH v2 2/4] x86/PCI: Simplify code by using the new " Andy Shevchenko
2018-03-13 10:45 ` Jean Delvare
2018-03-01 18:02 ` [PATCH v2 3/4] ACPI / sleep: " Andy Shevchenko
2018-03-01 18:02 ` [PATCH v2 4/4] PCI: " Andy Shevchenko
2018-03-02 11:10 ` [PATCH v2 0/4] x86, dmi: introduce and use dmi_get_bios_year() Rafael J. Wysocki
2018-03-05 13:24 ` Andy Shevchenko
2018-03-06 15:12 ` Rafael J. Wysocki
2018-03-12 8:52 ` Ingo Molnar [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=20180312085240.7y6ycvzo6ns7hjzc@gmail.com \
--to=mingo@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--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 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).