All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 0/1] GPIO support for Microblaze
Date: Mon, 29 Apr 2013 10:21:57 +0200	[thread overview]
Message-ID: <517E2DA5.5010307@monstr.eu> (raw)
In-Reply-To: <CAPnjgZ2iDL2vcAqSHg4CGvJS6NtLEZ_+zBSBy=MeumT5oUa1Yw@mail.gmail.com>

On 04/27/2013 05:35 PM, Simon Glass wrote:
> Hi Michal,
> 
> On Wed, Apr 24, 2013 at 1:30 AM, Michal Simek <monstr@monstr.eu> wrote:
>> Hi Simon,
>>
>> here is also one small problem if you want to use patman just for one patch
>> then cover letter contains 0/1 but patch itself doesn't contain 1/1.
>>
>> I think will be good to just add 1/1 to patch too.
>>
>> Generated by:
>> ./tools/patman/patman -c 1
> 
> Possibly, although here patman is just using 'git format-patch' to
> create the initial patch file.

It is just to call "git format-patch -n" instead of git format-patch
all the time. For more that one patch is -n used all the time.

> There is a 'Series-notes:' tag for adding notes to the cover letter. I
> wonder if we should add a way to add text below the cut in a patch?

Isn't it already done - if you just add text below "---"?

> Then in the case where you only have one patch you might not need a
> cover letter.

I would prefer to support both option. If you have one patch you can
add notes below "---" or just create cover letter.
Developer should choose which way is better for his case.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130429/e5a9ac97/attachment.pgp>

      reply	other threads:[~2013-04-29  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  8:27 [U-Boot] [RFC PATCH 0/1] GPIO support for Microblaze Michal Simek
2013-04-24  8:27 ` [U-Boot] [RFC PATCH] gpio: Add support for microblaze xilinx GPIO Michal Simek
2013-04-27 15:45   ` Simon Glass
2013-04-29  8:56     ` Michal Simek
2013-04-24  8:30 ` [U-Boot] [RFC PATCH 0/1] GPIO support for Microblaze Michal Simek
2013-04-27 15:35   ` Simon Glass
2013-04-29  8:21     ` Michal Simek [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=517E2DA5.5010307@monstr.eu \
    --to=monstr@monstr.eu \
    --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 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.