From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] ARM:AM33XX: Add support for TI AM335X EVM
Date: Wed, 12 Oct 2011 23:19:12 +0200 [thread overview]
Message-ID: <4E960450.4060004@compulab.co.il> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930257A576D2@dbde02.ent.ti.com>
On 10/12/11 12:18, Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Igor Grinberg
>> Sent: Wednesday, October 12, 2011 1:24 PM
>> To: Kumar Nath, Chandan
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] [PATCH 5/5] ARM:AM33XX: Add support for
>> TI AM335X EVM
>>
>> Hi Chandan,
>>
>> On 10/11/11 15:51, Chandan Nath wrote:
>>> This patch adds basic support for booting the board.
>>> This patch adds support for the UART necessary to
>>> get to the u-boot prompt.
>>>
>>> Signed-off-by: Chandan Nath <chandan.nath@ti.com>
>>> ---
>>> Support for additional peripherals depends on this patchset.
>>> Will be posting them soon.
>>
>> Please, don't forget to specify the dependencies when you post
>> the depending patch sets.
>
> Igor,
> The comment means that there are more patches in the pipeline
> that depend on "this" patchset. This patchset doesn't have any
> dependency.
I know it does not. I think you've misunderstood me :)
(or my English is not good enough, which I think is a real problem).
By saying "depending patch sets", I meant the future patchsets that
will depend on the current one.
Technically, it is more important to specify that a patchset depends
on something than there will be patches that depend on the current one. :)
--
Regards,
Igor.
next prev parent reply other threads:[~2011-10-12 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 13:51 [U-Boot] [PATCH 0/5] ARM:AM33XX: Basic support for AM33xx platform Chandan Nath
2011-10-11 13:51 ` [U-Boot] [PATCH 1/5] ARM:AM33XX: Added support for AM33xx Chandan Nath
2011-10-11 16:06 ` Tom Rini
2011-10-12 10:29 ` Kumar
2011-10-12 14:07 ` Tom Rini
2011-10-11 13:51 ` [U-Boot] [PATCH 2/5] ARM:AM33XX: Add clock definitions Chandan Nath
2011-10-11 13:51 ` [U-Boot] [PATCH 3/5] ARM:AM33XX: Add emif/ddr support Chandan Nath
2011-10-11 13:51 ` [U-Boot] [PATCH 4/5] ARM:AM33XX: Added timer support Chandan Nath
2011-10-11 16:04 ` Tom Rini
2011-10-12 10:25 ` Kumar
2011-10-11 13:51 ` [U-Boot] [PATCH 5/5] ARM:AM33XX: Add support for TI AM335X EVM Chandan Nath
2011-10-11 16:09 ` Tom Rini
2011-10-12 10:30 ` Kumar
2011-10-12 7:53 ` Igor Grinberg
2011-10-12 10:18 ` Premi, Sanjeev
2011-10-12 21:19 ` Igor Grinberg [this message]
2011-10-12 11:08 ` Kumar
2011-10-12 8:04 ` Igor Grinberg
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=4E960450.4060004@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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