From: "Pali Rohár" <pali@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Marek Behún" <marek.behun@nic.cz>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Assign PCI domain by ida_alloc()
Date: Thu, 18 Aug 2022 18:37:56 +0200 [thread overview]
Message-ID: <20220818163756.qmyopspdn5xywe5s@pali> (raw)
In-Reply-To: <Yv5T1dcIIOPy3KvB@lunn.ch>
On Thursday 18 August 2022 16:59:33 Andrew Lunn wrote:
> On Thu, Aug 18, 2022 at 03:50:09PM +0200, Pali Rohár wrote:
> > PING?
>
> Pretty much anything sent during the merge window, and just before the
> merge window gets thrown away. Please rebase onto the current pci tree
> and repost.
>
> Andrew
>
Please write it pretty clear that you are not interested in those
patches, and not hiding this info behind asking me after month of
waiting for another work of rebase with sending them at eight o'clock
during full moon. It is pretty ridiculous how to say "go away". Thanks.
next prev parent reply other threads:[~2022-08-18 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 20:47 [PATCH] PCI: Assign PCI domain by ida_alloc() Pali Rohár
2022-07-14 18:41 ` [PATCH v2] " Pali Rohár
2022-08-18 13:50 ` Pali Rohár
2022-08-18 14:59 ` Andrew Lunn
2022-08-18 16:37 ` Pali Rohár [this message]
2022-08-18 16:52 ` Bjorn Helgaas
2022-10-09 11:29 ` Pali Rohár
2022-10-09 13:39 ` Christophe JAILLET
2022-11-01 23:06 ` Pali Rohár
2022-10-09 13:36 ` Christophe JAILLET
2022-10-09 14:02 ` Pali Rohár
2022-11-07 23:05 ` Bjorn Helgaas
2023-03-20 20:26 ` Jon Hunter
2023-03-20 20:59 ` Pali Rohár
2023-03-21 18:44 ` Jon Hunter
2023-03-22 14:36 ` Jon Hunter
2023-03-22 17:21 ` Pali Rohár
2023-03-22 20:13 ` Jon Hunter
2023-03-28 13:31 ` Rob Herring
2023-03-28 17:02 ` Jon Hunter
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=20220818163756.qmyopspdn5xywe5s@pali \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=robh+dt@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).