On Sat, 2010-10-30 at 17:17 -0400, Matt Turner wrote: > On Sat, Oct 30, 2010 at 5:08 PM, Joe Perches <joe@xxxxxxxxxxx> wrote: > > Coalesce long formats. > > Align arguments. > > Signed-off-by: Joe Perches <joe@xxxxxxxxxxx> > > arch/alpha/kernel/pci-sysfs.c | 14 ++++++-------- > > 1 files changed, 6 insertions(+), 8 deletions(-) > > diff --git a/arch/alpha/kernel/pci-sysfs.c b/arch/alpha/kernel/pci-sysfs.c > > @@ -44,10 +44,9 @@ static int __pci_mmap_fits(struct pci_dev *pdev, int num, > > - WARN(1, "process \"%s\" tried to map%s 0x%08lx-0x%08lx on %s BAR %d " > > - "(size 0x%08lx)\n", > > - current->comm, sparse ? " sparse" : "", start, start + nr, > > - pci_name(pdev), num, size); > > + WARN(1, "process \"%s\" tried to map%s 0x%08lx-0x%08lx on %s BAR %d (size 0x%08lx)\n", > > + current->comm, sparse ? " sparse" : "", start, start + nr, > > + pci_name(pdev), num, size); > > @@ -261,10 +260,9 @@ static int __legacy_mmap_fits(struct pci_controller *hose, > > - WARN(1, "process \"%s\" tried to map%s 0x%08lx-0x%08lx on hose %d " > > - "(size 0x%08lx)\n", > > - current->comm, sparse ? " sparse" : "", start, start + nr, > > - hose->index, size); > > + WARN(1, "process \"%s\" tried to map%s 0x%08lx-0x%08lx on hose %d (size 0x%08lx)\n", > > + current->comm, sparse ? " sparse" : "", start, start + nr, > > + hose->index, size); > What's accomplished here? It looks like you joined two strings (which > were separated as to not overflow the 80-char limit) and spaced a > couple lines over. > > I don't see how this makes anything clearer. Hi Matt. This one is just a whitespace cleanup. Ignore it or nack it if you want. The patch was generated mostly by script to standardize the WARN uses. Long formats are generally preferred for grep. In this case, there's no particular value in the format coalescing because the output isn't going to be found with a grep. There were other patches that are actual defect fixes. cheers, Joe -- To unsubscribe from this list: send the line "unsubscribe linux-alpha" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
