All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: hw_breakpoint: Fix newlines in WARNings
Date: Wed, 09 Mar 2011 21:58:59 +0000	[thread overview]
Message-ID: <1299707939.4971.1.camel@jazzbox> (raw)
In-Reply-To: <4D77D6CB.402@codeaurora.org>

On Wed, 2011-03-09 at 19:36 +0000, Stephen Boyd wrote:
> Will,

Hi Stephen,
> 
> On 02/25/2011 08:06 PM, Stephen Boyd wrote:
> > Will Deacon wrote:
> >>> I'd prefer the message text not to be line wrapped, even if it
> >>> violates the general line length rule, because that makes it easier to
> >>> grep for the message in the source code.
> >> Ok, that's understandable. Moving the text onto its own line will limit
> >> the damage to the line length too. Stephen - are you happy to make these
> >> changes as part of your previous patch?
> >
> 
> Do you want to take this? I'm going to submit it to the patch tracker
> tomorrow otherwise.

Please submit it to the patch system with my ack:

Acked-by: Will Deacon <will.deacon@arm.com>

Thanks,

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: hw_breakpoint: Fix newlines in WARNings
Date: Wed, 09 Mar 2011 21:58:59 +0000	[thread overview]
Message-ID: <1299707939.4971.1.camel@jazzbox> (raw)
In-Reply-To: <4D77D6CB.402@codeaurora.org>

On Wed, 2011-03-09 at 19:36 +0000, Stephen Boyd wrote:
> Will,

Hi Stephen,
> 
> On 02/25/2011 08:06 PM, Stephen Boyd wrote:
> > Will Deacon wrote:
> >>> I'd prefer the message text not to be line wrapped, even if it
> >>> violates the general line length rule, because that makes it easier to
> >>> grep for the message in the source code.
> >> Ok, that's understandable. Moving the text onto its own line will limit
> >> the damage to the line length too. Stephen - are you happy to make these
> >> changes as part of your previous patch?
> >
> 
> Do you want to take this? I'm going to submit it to the patch tracker
> tomorrow otherwise.

Please submit it to the patch system with my ack:

Acked-by: Will Deacon <will.deacon@arm.com>

Thanks,

Will


  reply	other threads:[~2011-03-09 21:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 18:55 [TRIVIAL/PATCH] ARM: hw_breakpoint: Fix newlines in WARN messages Stephen Boyd
2011-02-24 18:55 ` Stephen Boyd
2011-02-25  6:38 ` Lothar Waßmann
2011-02-25  6:38   ` Lothar Waßmann
2011-02-25 11:31   ` Will Deacon
2011-02-25 11:31     ` Will Deacon
2011-02-26  4:06     ` [PATCH] ARM: hw_breakpoint: Fix newlines in WARNings Stephen Boyd
2011-02-26  4:06       ` Stephen Boyd
2011-03-09 19:36       ` Stephen Boyd
2011-03-09 19:36         ` Stephen Boyd
2011-03-09 21:58         ` Will Deacon [this message]
2011-03-09 21:58           ` Will Deacon

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=1299707939.4971.1.camel@jazzbox \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.