From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: "Timofei V. Bondarenko" <timm@ipi.ac.ru>
Cc: tglx@linutronix.de, linux-mtd@lists.infradead.org
Subject: Re: nand locking
Date: Wed, 27 Apr 2005 14:32:17 +0400 [thread overview]
Message-ID: <426F6A31.4010000@yandex.ru> (raw)
In-Reply-To: <426F691D.50905@ipi.ac.ru>
Timofei V. Bondarenko wrote:
> It awaits since 18 Apr - longer than a week... is it ok?
> Are there other ways to submit a patch? (a small bugfix to cmdlinepart).
> AFAIK, placing diffs into message text is not welcomed too.
Insert the patch to the mail body then.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-04-27 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 7:34 nand locking Timofei V. Bondarenko
2005-04-27 9:00 ` Thomas Gleixner
2005-04-27 9:09 ` Timofei V. Bondarenko
2005-04-27 10:45 ` Thomas Gleixner
2005-04-27 10:27 ` Timofei V. Bondarenko
2005-04-27 10:32 ` Artem B. Bityuckiy [this message]
2005-04-27 11:35 ` Thomas Gleixner
2005-04-27 11:19 ` Timofei V. Bondarenko
2005-04-27 18:27 ` Todd Poynor
2005-04-28 7:00 ` Timofei V. Bondarenko
2005-04-29 22:19 ` Todd Poynor
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=426F6A31.4010000@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=timm@ipi.ac.ru \
/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