From: Artem Bityutskiy <dedekind@infradead.org>
To: Vinit Agnihotri <vinit.agnihotri@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: bug in UBI
Date: Wed, 04 Jul 2007 13:41:19 +0300 [thread overview]
Message-ID: <1183545679.3531.31.camel@sauron> (raw)
In-Reply-To: <9b52d64c0707040320h26d41c9bta5dab5bfce56dd45@mail.gmail.com>
On Wed, 2007-07-04 at 15:50 +0530, Vinit Agnihotri wrote:
> When attaching a UBI to a mtd device, UBI reports following mesage
> UBI: attached mtd0 to ubi1
Thank you for the catch!
However, if you want your patch to be committed and you to be the author
of the patch, send correctly made patch, with correct Signed-off-by.
Make sure I can use git-am to commit your patch. Google for more
information how to submit kernel patches.
Or I cam fix the print problem this myself and add you at Reported-by:.
I am fine with both.
Thanks, Artem.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-07-04 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 10:20 bug in UBI Vinit Agnihotri
2007-07-04 10:41 ` Artem Bityutskiy [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=1183545679.3531.31.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vinit.agnihotri@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox