From: Thomas Gleixner <tglx@linutronix.de>
To: sshahrom@micron.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] NAND: Adding Micron MFR Id
Date: Wed, 21 Mar 2007 16:10:38 +0100 [thread overview]
Message-ID: <1174489838.10840.94.camel@localhost.localdomain> (raw)
In-Reply-To: <809D758398CC1F49AA8E493528AD4A27014DF5FB@ntxsjombx02.micron.com>
On Mon, 2007-03-19 at 09:30 -0700, sshahrom@micron.com wrote:
> Hello,
> Adding Micron manufacturing ID.
>
> Signed-off-by: Shahrom Sharif <sshahrom@micron.com>
patching file drivers/mtd/nand/nand_ids.c
Hunk #1 FAILED at 137.
1 out of 1 hunk FAILED -- saving rejects to file drivers/mtd/nand/nand_ids.c.rej
patching file include/linux/mtd/nand.h
Hunk #1 FAILED at 431.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/mtd/nand.h.rej
Your patch is whitespace damaged, please fix your mail client or your editor.
tglx
next prev parent reply other threads:[~2007-03-21 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 16:30 [PATCH] [MTD] NAND: Adding Micron MFR Id sshahrom
2007-03-21 15:10 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 1:48 [PATCH] [MTD] NAND: Adding Micron MFR ID sshahrom
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=1174489838.10840.94.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=sshahrom@micron.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