Re: [GIT PULL] PCI changes for v4.9

On Fri, Oct 14, 2016 at 6:25 AM, Bjorn Helgaas wrote: > > I guess I've always been a little confused on what to put in the email > vs. what should be in the tag message itself. So I actually end up using either or *both* for my merge messages. A lot of people put a "short

Re: [GIT PULL] PCI changes for v4.9

On Fri, Oct 14, 2016 at 6:25 AM, Bjorn Helgaas wrote: > > I guess I've always been a little confused on what to put in the email > vs. what should be in the tag message itself. So I actually end up using either or *both* for my merge messages. A lot of people put a "short and concise bulleted

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 05:21:40PM -0700, Linus Torvalds wrote: > On Thu, Oct 13, 2016 at 4:48 PM, Linus Torvalds > wrote: > > > > Ugh: > > > > Your "summary" is actually less legible than the shortlog, and looks > > entirely auto-generated. > > > > That's against

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 05:21:40PM -0700, Linus Torvalds wrote: > On Thu, Oct 13, 2016 at 4:48 PM, Linus Torvalds > wrote: > > > > Ugh: > > > > Your "summary" is actually less legible than the shortlog, and looks > > entirely auto-generated. > > > > That's against the whole point of having a

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 4:48 PM, Linus Torvalds wrote: > > Ugh: > > Your "summary" is actually less legible than the shortlog, and looks > entirely auto-generated. > > That's against the whole point of having a summary for a pull request. > > Please tell me what

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 4:48 PM, Linus Torvalds wrote: > > Ugh: > > Your "summary" is actually less legible than the shortlog, and looks > entirely auto-generated. > > That's against the whole point of having a summary for a pull request. > > Please tell me what changed, don't auto-generate

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 7:07 AM, Bjorn Helgaas wrote: > > Here are some more changes I'd like to have in v4.9. There's one small > Tegra bug fix in the PHY poweroff path, which is only used in failure > paths. The rest is all strictly cleanup that should make host bridge >

Re: [GIT PULL] PCI changes for v4.9

On Thu, Oct 13, 2016 at 7:07 AM, Bjorn Helgaas wrote: > > Here are some more changes I'd like to have in v4.9. There's one small > Tegra bug fix in the PHY poweroff path, which is only used in failure > paths. The rest is all strictly cleanup that should make host bridge > drivers more

[GIT PULL] PCI changes for v4.9

Hi Linus, Here are some more changes I'd like to have in v4.9. There's one small Tegra bug fix in the PHY poweroff path, which is only used in failure paths. The rest is all strictly cleanup that should make host bridge drivers more readable, but shouldn't actually change any behavior. Bjorn

[GIT PULL] PCI changes for v4.9

Hi Linus, Here are some more changes I'd like to have in v4.9. There's one small Tegra bug fix in the PHY poweroff path, which is only used in failure paths. The rest is all strictly cleanup that should make host bridge drivers more readable, but shouldn't actually change any behavior. Bjorn

[GIT PULL] PCI changes for v4.9

Hi Linus, Here are the PCI changes I intend for v4.9. Bjorn The following changes since commit 4fe0d154880bb6eb833cbe84fa6f385f400f0b9c: PCI: Use positive flags in pci_alloc_irq_vectors() (2016-08-16 14:07:30 -0500) are available in the git repository at:

[GIT PULL] PCI changes for v4.9

Hi Linus, Here are the PCI changes I intend for v4.9. Bjorn The following changes since commit 4fe0d154880bb6eb833cbe84fa6f385f400f0b9c: PCI: Use positive flags in pci_alloc_irq_vectors() (2016-08-16 14:07:30 -0500) are available in the git repository at: