Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"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: Wed, 2 Nov 2022 00:06:24 +0100	[thread overview]
Message-ID: <20221101230624.zsy22bxswl5o7d4k@pali> (raw)
In-Reply-To: <54096629-fef0-8952-6a84-c1a12e38a442@wanadoo.fr>

On Sunday 09 October 2022 15:39:11 Christophe JAILLET wrote:
> Le 09/10/2022 à 13:29, Pali Rohár a écrit :
> > On Thursday 18 August 2022 11:52:20 Bjorn Helgaas wrote:
> > > On Thu, Aug 18, 2022 at 06:37:56PM +0200, Pali Rohár wrote:
> > > > 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.
> > > > 
> > > > 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.
> > > 
> > > Nobody is saying "go away".  I apologize that I haven't had time to
> > > look at this yet.
> > > 
> > > It's still in patchwork [1], and if it still applies cleanly to
> > > v6.0-rc1, you don't need to do anything.  If it requires rebasing to
> > > apply cleanly, it will expedite things if you do that.
> > > 
> > > Bjorn
> > > 
> > > [1] https://patchwork.kernel.org/project/linux-pci/patch/20220714184130.5436-1-pali@kernel.org/
> > 
> > It applies cleanly on v6.0-rc1.
> > 
> 
> On linux-next, the diff applies, but with offsets on pci.c and pci.h.
> 
> CJ

This should not be an issue. Bjorn?

  reply	other threads:[~2022-11-01 23:09 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
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 [this message]
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=20221101230624.zsy22bxswl5o7d4k@pali \
    --to=pali@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=helgaas@kernel.org \
    --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