From: Mugunthan V N <mugunthanvnm@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"tony@atomide.com" <tony@atomide.com>,
"artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"jp.francois@cynove.com" <jp.francois@cynove.com>,
"Balbi, Felipe" <balbi@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Benoit Cousson \(benoit.cousson@linaro.org\)"
<benoit.cousson@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe
Date: Tue, 2 Jul 2013 12:44:40 +0530 [thread overview]
Message-ID: <51D27DE0.3000905@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9E3B5D@DBDE04.ent.ti.com>
On 7/2/2013 9:44 AM, Gupta, Pekon wrote:
>>>> This does not apply to l2-mtd.git, could you please re-base?
>>>>
>>> [Pekon]: rebased to l2-mtd.git
>>> - updated [Patch 3/4] which conflicted with commit '26331c04' which
>> touched omap2.c.
>>> - Please ignore [Patch 4/4] as it’s a DT update, which adds on top of Benoit's
>> tree (which has NAND node commits too).
>> If you need one patch (DT patch) in the series to be merged in another
>> repository (DT maintainer tree) then separate out that patch as separate
>> series and mention the dependency or need ack from the driver maintainer
>> so that both maintainer can apply the whole series into his repository
>> instead of applying partially here and there.
>>
> Agree. Yes, I should have sent the DT patch separately.
> But I posted all changes as part of single series, as its easy for users to
> Test and Ack them.
> Similarly patches for GPMC (Tony's tree) and NAND (Artem's tree) are
> functionally coupled, So at times I have to send them as part of same series.
> However, I'll clearly mention that in my cover-letter for future patches.
> Thanks for feedback ..
>
>
In that case you can publish your testing branch to a public repo and point to
that repo in your cover letter so that someone who wants to test can test
from your repo which has all dependent patches.
Regards
Mugunthan V N
WARNING: multiple messages have this Message-ID (diff)
From: Mugunthan V N <mugunthanvnm@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"tony@atomide.com" <tony@atomide.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"jp.francois@cynove.com" <jp.francois@cynove.com>,
"Balbi, Felipe" <balbi@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Benoit Cousson (benoit.cousson@linaro.org)"
<benoit.cousson@linaro.org>
Subject: Re: [PATCH v3 1/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe
Date: Tue, 2 Jul 2013 12:44:40 +0530 [thread overview]
Message-ID: <51D27DE0.3000905@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9E3B5D@DBDE04.ent.ti.com>
On 7/2/2013 9:44 AM, Gupta, Pekon wrote:
>>>> This does not apply to l2-mtd.git, could you please re-base?
>>>>
>>> [Pekon]: rebased to l2-mtd.git
>>> - updated [Patch 3/4] which conflicted with commit '26331c04' which
>> touched omap2.c.
>>> - Please ignore [Patch 4/4] as it’s a DT update, which adds on top of Benoit's
>> tree (which has NAND node commits too).
>> If you need one patch (DT patch) in the series to be merged in another
>> repository (DT maintainer tree) then separate out that patch as separate
>> series and mention the dependency or need ack from the driver maintainer
>> so that both maintainer can apply the whole series into his repository
>> instead of applying partially here and there.
>>
> Agree. Yes, I should have sent the DT patch separately.
> But I posted all changes as part of single series, as its easy for users to
> Test and Ack them.
> Similarly patches for GPMC (Tony's tree) and NAND (Artem's tree) are
> functionally coupled, So at times I have to send them as part of same series.
> However, I'll clearly mention that in my cover-letter for future patches.
> Thanks for feedback ..
>
>
In that case you can publish your testing branch to a public repo and point to
that repo in your cover letter so that someone who wants to test can test
from your repo which has all dependent patches.
Regards
Mugunthan V N
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-02 7:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 17:58 [PATCH v3 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Pekon Gupta
2013-06-23 17:58 ` Pekon Gupta
2013-06-23 17:58 ` [PATCH v3 1/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe Pekon Gupta
2013-06-23 17:58 ` Pekon Gupta
2013-07-01 8:16 ` Artem Bityutskiy
2013-07-01 8:16 ` Artem Bityutskiy
2013-07-01 10:02 ` Gupta, Pekon
2013-07-01 10:02 ` Gupta, Pekon
2013-07-01 17:37 ` Mugunthan V N
2013-07-01 17:37 ` Mugunthan V N
2013-07-02 4:14 ` Gupta, Pekon
2013-07-02 4:14 ` Gupta, Pekon
2013-07-02 7:14 ` Mugunthan V N [this message]
2013-07-02 7:14 ` Mugunthan V N
2013-06-23 17:58 ` [PATCH v3 2/4] ARM: OMAP2+: cleaned-up DT support of various ECC schemes Pekon Gupta
2013-06-23 17:58 ` Pekon Gupta
2013-06-23 17:58 ` [PATCH v3 3/4] mtd:nand:omap2: updated support for BCH4 ECC scheme Pekon Gupta
2013-06-23 17:58 ` Pekon Gupta
2013-06-23 17:58 ` [PATCH v3 4/4] ARM: dts: AM33xx: updated default ECC scheme in nand-ecc-opt Pekon Gupta
2013-06-23 17:58 ` Pekon Gupta
2013-06-27 17:50 ` [PATCH v3 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Gupta, Pekon
2013-06-27 17:50 ` Gupta, Pekon
-- strict thread matches above, loose matches on Subject: below --
2013-06-22 21:03 Pekon Gupta
2013-06-22 21:03 ` [PATCH v3 1/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe Pekon Gupta
2013-06-22 21:03 ` Pekon Gupta
2013-06-22 21:47 ` Felipe Balbi
2013-06-22 21:47 ` Felipe Balbi
2013-06-23 18:06 ` Gupta, Pekon
2013-06-23 18:06 ` Gupta, Pekon
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=51D27DE0.3000905@ti.com \
--to=mugunthanvnm@ti.com \
--cc=arnd@arndb.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=balbi@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=jp.francois@cynove.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.com \
--cc=tony@atomide.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 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.