From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/6] ARM: davinci: Changed pr_warning() to pr_warn()
Date: Sat, 27 Oct 2012 14:22:57 +0530 [thread overview]
Message-ID: <508BA0E9.2050406@ti.com> (raw)
In-Reply-To: <13514BD7FAEBA745BBD7D8A672905C14311F0E03@DFLE08.ent.ti.com>
On 10/27/2012 6:29 AM, Tivy, Robert wrote:
> Thanks for your comments, Sergei. Please see below...
>
>> -----Original Message-----
>> From: Sergei Shtylyov [mailto:sshtylyov at mvista.com]
>> Sent: Friday, October 26, 2012 2:46 AM
>> To: Tivy, Robert
>> Cc: davinci-linux-open-source at linux.davincidsp.com; linux-arm-
>> kernel at lists.infradead.org; Ring, Chris; Grosen, Mark; Nori, Sekhar
>> Subject: Re: [PATCH v2 1/6] ARM: davinci: Changed pr_warning() to
>> pr_warn()
>>
>> Hello.
>>
>> It's not a good idea to send multiple patches with the same
>> subject.
>> Actually, in this case it's worth merging all 4 patches into one.
>
> My first patch submission had them all as one patch, but Sekhar asked that they be split into 4 separate patches to make the merge easier.
>
> I can make each one have a different subject, though.
Yes, it was I who asked for the patch to be separated out. My main
motivation was to keep board and soc file changes from mixing together.
The subject line for each patch should be different though.
>
>>
>> On 26-10-2012 0:35, Robert Tivy wrote:
>>
>>> Also, while modifying those pr_warning() calls I changed hardcoded
>>> function names to use '"%s:", __func__' instead
>>
>>> Signed-off-by: Robert Tivy <rtivy@ti.com>
>>> ---
>>> Clean up files that will be otherwise modified in subsequent patch.
>>
>>> Applies to v3.5 tag (commit 28a33cbc24e4256c143dce96c7d93bf423229f92)
>> of
>>> Linus' mainline kernel at git.kernel.org.
>>
>> 3.5 is too old. Why not to 3.6 or even 3.7-rc2?
>
> I will attempt to recreate this patch series on 3.7-rc2, although I will need to change it to use the newer "rproc" APIs and data structures.
All the more reason to rebase to v3.7-rc2!
Thanks,
Sekhar
next prev parent reply other threads:[~2012-10-27 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1351197357-23528-1-git-send-email-rtivy@ti.com>
2012-10-26 9:46 ` [PATCH v2 1/6] ARM: davinci: Changed pr_warning() to pr_warn() Sergei Shtylyov
2012-10-27 0:59 ` Tivy, Robert
2012-10-27 8:52 ` Sekhar Nori [this message]
[not found] ` <1351197357-23528-5-git-send-email-rtivy@ti.com>
2012-11-01 13:52 ` [PATCH v2 5/6] ARM: davinci: remoteproc board support for OMAP-L138 DSP Ben Gardiner
2012-11-06 5:02 ` Prabhakar Lad
2012-11-06 19:33 ` Tivy, Robert
2012-11-07 5:20 ` Prabhakar Lad
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=508BA0E9.2050406@ti.com \
--to=nsekhar@ti.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.