mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Russell King <linux@arm.linux.org.uk>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/2] AB3100 regulator support v4
Date: Wed, 9 Sep 2009 13:17:18 +0200	[thread overview]
Message-ID: <63386a3d0909090417l742cfa88u9747558c3e04d08d@mail.gmail.com> (raw)
In-Reply-To: <20090909093500.GC4292@sortiz.org>

2009/9/9 Samuel Ortiz <sameo@linux.intel.com>:

> On Wed, Sep 09, 2009 at 12:07:05AM +0200, Linus Walleij wrote:
>> 009/9/3 Liam Girdwood <lrg@slimlogic.co.uk>:
>>
>> > Samuel, are you happy for this to go via mfd for simpler merging ?
>> > If so :-
>> >
>> > Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
>>
>> OK with you Sam?
>
> Yes, applied to my for-next branch. There were a couple checkpatch 80+
> character line length warnings, but I'm not that picky :)

Thanks a lot Sam, I think all these warnings are of the type where
dev_*(); messages get more than 80 characters long, and that has
been indicated by Linus (the other one) and some subsystem maintainers
to be undesireable to break across lines in order to avoid hassles
when grep:ing for error strings in the kernel tree.

Linus Walleij

      reply	other threads:[~2009-09-09 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 12:53 Linus Walleij
2009-09-03 13:36 ` Mark Brown
2009-09-03 14:15 ` Liam Girdwood
2009-09-08 22:07   ` Linus Walleij
2009-09-09  9:35     ` Samuel Ortiz
2009-09-09 11:17       ` Linus Walleij [this message]

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=63386a3d0909090417l742cfa88u9747558c3e04d08d@mail.gmail.com \
    --to=linus.ml.walleij@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lrg@slimlogic.co.uk \
    --cc=sameo@linux.intel.com \
    /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
all inboxes | Powered by JetHome®