On Wed, 2024-06-12 at 15:42 -0500, Bjorn Helgaas wrote:
> On Wed, Jun 12, 2024 at 10:51:40AM +0200, Philipp Stanner wrote:
> > On Tue, 2024-06-11 at 16:44 -0500, Bjorn Helgaas wrote:
> > > I'm trying to merge these into pci/next, but I'm having a hard
> > > time
> > > writing the merge commit log.
On Wed, Jun 12, 2024 at 10:51:40AM +0200, Philipp Stanner wrote:
> On Tue, 2024-06-11 at 16:44 -0500, Bjorn Helgaas wrote:
> > I'm trying to merge these into pci/next, but I'm having a hard time
> > writing the merge commit log. I want a one-sentence description of
> > each patch that tells me wha
On Tue, 2024-06-11 at 16:44 -0500, Bjorn Helgaas wrote:
> I'm trying to merge these into pci/next, but I'm having a hard time
> writing the merge commit log. I want a one-sentence description of
> each patch that tells me what the benefit of the patch is. Usually
> the subject line is a good star
I'm trying to merge these into pci/next, but I'm having a hard time
writing the merge commit log. I want a one-sentence description of
each patch that tells me what the benefit of the patch is. Usually
the subject line is a good start.
"Reimplement plural devres functions" is kind of vague and d
When the original PCI devres API was implemented, priority was given to the
creation of a set of "plural functions" such as pcim_request_regions().
These functions have bit masks as parameters to specify which BARs shall
get mapped. Most users, however, only use those to map 1-3 BARs.
A complete s
