From: Mail Delivery System <Mailer-Daemon@infradead.org>
To: linux-mtd-bounces@lists.infradead.org
Subject: Mail delivery failed: returning message to sender
Date: Mon, 16 Aug 2004 10:21:16 -0400 [thread overview]
Message-ID: <E1BwiMO-0007EC-Uw@canuck.infradead.org> (raw)
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
lukefimmerzane@hotmail.com
SMTP error from remote mailer after RCPT TO:<lukefimmerzane@hotmail.com>:
host mx1.hotmail.com [65.54.252.99]: 550 Requested action not taken:
mailbox unavailable
------ This is a copy of the message, including all the headers. ------
Return-path: <linux-mtd-bounces@lists.infradead.org>
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiLa-0007B5-TB; Mon, 16 Aug 2004 10:20:27 -0400
From: linux-mtd-request@lists.infradead.org
Subject: linux-mtd Digest, Vol 17, Issue 17
To: linux-mtd@lists.infradead.org
Reply-To: linux-mtd@lists.infradead.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
Message-ID: <E1BwiLa-0007B5-TB@canuck.infradead.org>
Date: Mon, 16 Aug 2004 10:20:27 -0400
Send linux-mtd mailing list submissions to
linux-mtd@lists.infradead.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.infradead.org/mailman/listinfo/linux-mtd
or, via email, send a message with subject or body 'help' to
linux-mtd-request@lists.infradead.org
You can reach the person managing the list at
linux-mtd-owner@lists.infradead.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of linux-mtd digest..."
Today's Topics:
1. Support of stupid devices (Ian Molton)
2. Re: Support of stupid devices (Thomas Gleixner)
3. Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and
cfi_probe (Josh Boyer)
4. Mail delivery failed: returning message to sender
(Mail Delivery System)
5. failure notice (MAILER-DAEMON@conectiva.com.br)
6. failure notice (MAILER-DAEMON@conectiva.com.br)
7. Mail delivery failed: returning message to sender
(Mail Delivery System)
----------------------------------------------------------------------
Message: 1
Date: Mon, 16 Aug 2004 01:39:33 +0100
From: Ian Molton <spyro@f2s.com>
Subject: Support of stupid devices
To: linux-mtd@lists.infradead.org
Message-ID: <20040816013933.163a101d.spyro@f2s.com>
Content-Type: text/plain; charset=US-ASCII
Hi.
Im porting linux to the toshiba e7xx and 8xx PDAs which contain a nand flash controller.
Im not certain, but it appears the controllerhas an odd quirk meaning byte-reads of the data register dont work as the linux mtd code expects.
AFAICT if I read a word (after issuing a chipid command) I get:
0xYYZZ75ec -- this is good - Samsung, 32MB device.
if I do two byte reads I get 0xec 0xec.
a halfword access gets me 0xYYZZ.
a misaligned (by one byte) word access gives me 0xecYYZZ75, but this fails to work for byte accesses. halfword misaligned accesses are just weird.
so basically, the only way to read the chipid is to do:
a word access to the data reg and then shift the data out
or
a word access (and mask off the high 3 bytes followed by a misaligned word access and mask off the upper 3 bytes.
clearly the former solution is the better one, but this doesnt fit in the nand driver model very well (read_byte() et.al.)
the chip is a TC6393XB (system on chip) and the flash is a samsung K9F5608UOC YCBO
------------------------------
Message: 2
Date: Mon, 16 Aug 2004 15:11:17 +0200
From: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Support of stupid devices
To: Ian Molton <spyro@f2s.com>
Cc: linux-mtd@lists.infradead.org
Message-ID: <1092661877.4354.10.camel@lap02.tec.linutronix.de>
Content-Type: text/plain
On Mon, 2004-08-16 at 02:39, Ian Molton wrote:
> Hi.
>
> Im porting linux to the toshiba e7xx and 8xx PDAs
> which contain a nand flash controller.
> Im not certain, but it appears the controllerhas an
> odd quirk meaning byte-reads of the data register
> dont work as the linux mtd code expects.
>
> AFAICT if I read a word (after issuing a chipid command) I get:
>
> 0xYYZZ75ec -- this is good - Samsung, 32MB device.
>
> if I do two byte reads I get 0xec 0xec.
>
> a halfword access gets me 0xYYZZ.
> a misaligned (by one byte) word access gives me 0xecYYZZ75,
Sounds really stupid :)
> but this fails to work for byte accesses. halfword misaligned
> accesses are just weird.
> so basically, the only way to read the chipid is to do:
> a word access to the data reg and then shift the data out
> or
> a word access (and mask off the high 3 bytes followed by a
> misaligned word access and mask off the upper 3 bytes.
> clearly the former solution is the better one, but this
> doesnt fit in the nand driver model very well
> (read_byte() et.al.)
You can provide your own read_byte() et. al. functions which do all the
magic. Look into the other Toshiba nand driver implementations. They do
the same. I don't have the header files which implement the real access
but Alice should be a source of help.
> the chip is a TC6393XB (system on chip) and the flash
> is a samsung K9F5608UOC YCBO
tglx
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
------------------------------
Message: 3
Date: Mon, 16 Aug 2004 09:13:19 -0500
From: Josh Boyer <jdub@us.ibm.com>
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and
cfi_probe
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Message-ID: <1092665599.2912.120.camel@weaponx.rchland.ibm.com>
Content-Type: text/plain
On Thu, 2004-08-12 at 02:13, Eric W. Biederman wrote:
> So far I have been busy with other things so I have been taking the slow route
> to refactoring. I have just reported the cfi_fixup function from cfi_util
> and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
> under control.
>
> It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
> merged.
Sorry for the delay. Maybe I can convince Joern to get them merged.
Most of the stuff can probably be done in a fixup function now that they
take a struct mtd_info *.
>
> For the deeper pieces of command set common code moving their helper functions
> into cfi_util is probably a good place to start.
>
> I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...
We can always hope :).
josh
------------------------------
Message: 4
Date: Mon, 16 Aug 2004 10:14:32 -0400
From: Mail Delivery System <Mailer-Daemon@infradead.org>
Subject: Mail delivery failed: returning message to sender
To: linux-mtd-bounces@lists.infradead.org
Message-ID: <E1BwiFs-0006gs-TJ@canuck.infradead.org>
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
joern@wohnheim.fh-wedel.de
retry time not reached for any host after a long failure period
------ This is a copy of the message, including all the headers. ------
Return-path: <linux-mtd-bounces@lists.infradead.org>
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiFQ-0006YI-H8; Mon, 16 Aug 2004 10:14:04 -0400
Received: from e32.co.us.ibm.com ([32.97.110.130])
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiF0-0006YB-1m
for linux-mtd@lists.infradead.org; Mon, 16 Aug 2004 10:13:41 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com
[9.17.193.32])
by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id i7GEDKmL743234;
Mon, 16 Aug 2004 10:13:20 -0400
Received: from [9.10.78.208] (d03av02.boulder.ibm.com [9.17.195.168])
by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
i7GEDIB0207952; Mon, 16 Aug 2004 08:13:19 -0600
From: Josh Boyer <jdub@us.ibm.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
In-Reply-To: <m31xic6d79.fsf@maxwell.lnxi.com>
References: <m3vfgsmwfs.fsf@maxwell.lnxi.com>
<1089699909.8822.9.camel@imladris.demon.co.uk>
<m3658sj5ex.fsf@maxwell.lnxi.com>
<1089735455.29112.14.camel@weaponx.rchland.ibm.com>
<m31xic6d79.fsf@maxwell.lnxi.com>
Content-Type: text/plain
Message-Id: <1092665599.2912.120.camel@weaponx.rchland.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7)
Date: Mon, 16 Aug 2004 09:13:19 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
On Thu, 2004-08-12 at 02:13, Eric W. Biederman wrote:
> So far I have been busy with other things so I have been taking the slow route
> to refactoring. I have just reported the cfi_fixup function from cfi_util
> and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
> under control.
>
> It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
> merged.
Sorry for the delay. Maybe I can convince Joern to get them merged.
Most of the stuff can probably be done in a fixup function now that they
take a struct mtd_info *.
>
> For the deeper pieces of command set common code moving their helper functions
> into cfi_util is probably a good place to start.
>
> I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...
We can always hope :).
josh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
------------------------------
Message: 5
Date: 16 Aug 2004 15:12:03 -0000
From: MAILER-DAEMON@conectiva.com.br
Subject: failure notice
To: linux-mtd-bounces@lists.infradead.org
Message-ID: <20040816141423.0D13947448@perninha.conectiva.com.br>
Hi. This is the qmail-send program at conectiva.com.br.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<beckmann@burns.conectiva>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is a copy of the message.
Return-Path: <linux-mtd-bounces@lists.infradead.org>
Received: (qmail 18818 invoked by uid 0); 16 Aug 2004 15:12:03 -0000
Received: from perninha.conectiva.com.br (200.140.247.100)
by burns.conectiva with SMTP; 16 Aug 2004 15:12:03 -0000
Received: by perninha.conectiva.com.br (Postfix)
id E549947448; Mon, 16 Aug 2004 11:14:22 -0300 (BRT)
Delivered-To: beckmann@conectiva.com.br
Received: by perninha.conectiva.com.br (Postfix, from userid 568)
id DD0784745F; Mon, 16 Aug 2004 11:14:22 -0300 (BRT)
Received: from canuck.infradead.org (canuck.infradead.org [205.233.218.70])
by perninha.conectiva.com.br (Postfix) with ESMTP id D346947448
for <beckmann@conectiva.com.br>; Mon, 16 Aug 2004 11:14:20 -0300 (BRT)
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiFQ-0006YI-Qn; Mon, 16 Aug 2004 10:14:04 -0400
Received: from e32.co.us.ibm.com ([32.97.110.130])
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiF0-0006YB-1m
for linux-mtd@lists.infradead.org; Mon, 16 Aug 2004 10:13:41 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com
[9.17.193.32])
by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id i7GEDKmL743234;
Mon, 16 Aug 2004 10:13:20 -0400
Received: from [9.10.78.208] (d03av02.boulder.ibm.com [9.17.195.168])
by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
i7GEDIB0207952; Mon, 16 Aug 2004 08:13:19 -0600
From: Josh Boyer <jdub@us.ibm.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
In-Reply-To: <m31xic6d79.fsf@maxwell.lnxi.com>
References: <m3vfgsmwfs.fsf@maxwell.lnxi.com>
<1089699909.8822.9.camel@imladris.demon.co.uk>
<m3658sj5ex.fsf@maxwell.lnxi.com>
<1089735455.29112.14.camel@weaponx.rchland.ibm.com>
<m31xic6d79.fsf@maxwell.lnxi.com>
Content-Type: text/plain
Message-Id: <1092665599.2912.120.camel@weaponx.rchland.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7)
Date: Mon, 16 Aug 2004 09:13:19 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
X-Bogosity: No, tests=bogofilter, spamicity=0.262721, version=0.16.3
On Thu, 2004-08-12 at 02:13, Eric W. Biederman wrote:
> So far I have been busy with other things so I have been taking the slow route
> to refactoring. I have just reported the cfi_fixup function from cfi_util
> and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
> under control.
>
> It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
> merged.
Sorry for the delay. Maybe I can convince Joern to get them merged.
Most of the stuff can probably be done in a fixup function now that they
take a struct mtd_info *.
>
> For the deeper pieces of command set common code moving their helper functions
> into cfi_util is probably a good place to start.
>
> I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...
We can always hope :).
josh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
------------------------------
Message: 6
Date: 16 Aug 2004 15:11:58 -0000
From: MAILER-DAEMON@conectiva.com.br
Subject: failure notice
To: linux-mtd-bounces@lists.infradead.org
Message-ID: <20040816141418.1D1A5473D8@perninha.conectiva.com.br>
Hi. This is the qmail-send program at conectiva.com.br.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<fuganti@burns.conectiva>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is a copy of the message.
Return-Path: <linux-mtd-bounces@lists.infradead.org>
Received: (qmail 18808 invoked by uid 0); 16 Aug 2004 15:11:58 -0000
Received: from perninha.conectiva.com.br (200.140.247.100)
by burns.conectiva with SMTP; 16 Aug 2004 15:11:58 -0000
Received: by perninha.conectiva.com.br (Postfix)
id E3EB5473D8; Mon, 16 Aug 2004 11:14:17 -0300 (BRT)
Delivered-To: fuganti@conectiva.com.br
Received: by perninha.conectiva.com.br (Postfix, from userid 568)
id D0FF0473E4; Mon, 16 Aug 2004 11:14:17 -0300 (BRT)
Received: from canuck.infradead.org (canuck.infradead.org [205.233.218.70])
by perninha.conectiva.com.br (Postfix) with ESMTP id 71F4B473F1
for <fuganti@conectiva.com.br>; Mon, 16 Aug 2004 11:14:14 -0300 (BRT)
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiFP-0006YI-G4; Mon, 16 Aug 2004 10:14:03 -0400
Received: from e32.co.us.ibm.com ([32.97.110.130])
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiF0-0006YB-1m
for linux-mtd@lists.infradead.org; Mon, 16 Aug 2004 10:13:41 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com
[9.17.193.32])
by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id i7GEDKmL743234;
Mon, 16 Aug 2004 10:13:20 -0400
Received: from [9.10.78.208] (d03av02.boulder.ibm.com [9.17.195.168])
by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
i7GEDIB0207952; Mon, 16 Aug 2004 08:13:19 -0600
From: Josh Boyer <jdub@us.ibm.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
In-Reply-To: <m31xic6d79.fsf@maxwell.lnxi.com>
References: <m3vfgsmwfs.fsf@maxwell.lnxi.com>
<1089699909.8822.9.camel@imladris.demon.co.uk>
<m3658sj5ex.fsf@maxwell.lnxi.com>
<1089735455.29112.14.camel@weaponx.rchland.ibm.com>
<m31xic6d79.fsf@maxwell.lnxi.com>
Content-Type: text/plain
Message-Id: <1092665599.2912.120.camel@weaponx.rchland.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7)
Date: Mon, 16 Aug 2004 09:13:19 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
X-Bogosity: No, tests=bogofilter, spamicity=0.262721, version=0.16.3
On Thu, 2004-08-12 at 02:13, Eric W. Biederman wrote:
> So far I have been busy with other things so I have been taking the slow route
> to refactoring. I have just reported the cfi_fixup function from cfi_util
> and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
> under control.
>
> It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
> merged.
Sorry for the delay. Maybe I can convince Joern to get them merged.
Most of the stuff can probably be done in a fixup function now that they
take a struct mtd_info *.
>
> For the deeper pieces of command set common code moving their helper functions
> into cfi_util is probably a good place to start.
>
> I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...
We can always hope :).
josh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
------------------------------
Message: 7
Date: Mon, 16 Aug 2004 10:16:09 -0400
From: Mail Delivery System <Mailer-Daemon@infradead.org>
Subject: Mail delivery failed: returning message to sender
To: linux-mtd-bounces@lists.infradead.org
Message-ID: <E1BwiHR-0006tb-21@canuck.infradead.org>
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
joern@wohnheim.fh-wedel.de
retry time not reached for any host after a long failure period
------ This is a copy of the message, including all the headers. ------
Return-path: <linux-mtd-bounces@lists.infradead.org>
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiGo-0006hX-JJ; Mon, 16 Aug 2004 10:15:30 -0400
Received: from exim by canuck.infradead.org with local (Exim 4.33 #1 (Red Hat
Linux)) id 1BwiFs-0006gs-TJ
for linux-mtd-bounces@lists.infradead.org;
Mon, 16 Aug 2004 10:14:33 -0400
X-Failed-Recipients: joern@wohnheim.fh-wedel.de
Auto-Submitted: auto-generated
From: Mail Delivery System <Mailer-Daemon@infradead.org>
To: linux-mtd-bounces@lists.infradead.org
Message-Id: <E1BwiFs-0006gs-TJ@canuck.infradead.org>
Date: Mon, 16 Aug 2004 10:14:32 -0400
Subject: Mail delivery failed: returning message to sender
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
joern@wohnheim.fh-wedel.de
retry time not reached for any host after a long failure period
------ This is a copy of the message, including all the headers. ------
Return-path: <linux-mtd-bounces@lists.infradead.org>
Received: from localhost ([127.0.0.1] helo=canuck.infradead.org)
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiFQ-0006YI-H8; Mon, 16 Aug 2004 10:14:04 -0400
Received: from e32.co.us.ibm.com ([32.97.110.130])
by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux))
id 1BwiF0-0006YB-1m
for linux-mtd@lists.infradead.org; Mon, 16 Aug 2004 10:13:41 -0400
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com
[9.17.193.32])
by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id i7GEDKmL743234;
Mon, 16 Aug 2004 10:13:20 -0400
Received: from [9.10.78.208] (d03av02.boulder.ibm.com [9.17.195.168])
by westrelay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
i7GEDIB0207952; Mon, 16 Aug 2004 08:13:19 -0600
From: Josh Boyer <jdub@us.ibm.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
In-Reply-To: <m31xic6d79.fsf@maxwell.lnxi.com>
References: <m3vfgsmwfs.fsf@maxwell.lnxi.com>
<1089699909.8822.9.camel@imladris.demon.co.uk>
<m3658sj5ex.fsf@maxwell.lnxi.com>
<1089735455.29112.14.camel@weaponx.rchland.ibm.com>
<m31xic6d79.fsf@maxwell.lnxi.com>
Content-Type: text/plain
Message-Id: <1092665599.2912.120.camel@weaponx.rchland.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7)
Date: Mon, 16 Aug 2004 09:13:19 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
X-BeenThere: linux-mtd@lists.infradead.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Linux MTD discussion mailing list <linux-mtd.lists.infradead.org>
List-Unsubscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=unsubscribe>
List-Archive: <http://lists.infradead.org/pipermail/linux-mtd>
List-Post: <mailto:linux-mtd@lists.infradead.org>
List-Help: <mailto:linux-mtd-request@lists.infradead.org?subject=help>
List-Subscribe: <http://lists.infradead.org/mailman/listinfo/linux-mtd>,
<mailto:linux-mtd-request@lists.infradead.org?subject=subscribe>
Sender: linux-mtd-bounces@lists.infradead.org
Errors-To: linux-mtd-bounces@lists.infradead.org
On Thu, 2004-08-12 at 02:13, Eric W. Biederman wrote:
> So far I have been busy with other things so I have been taking the slow route
> to refactoring. I have just reported the cfi_fixup function from cfi_util
> and have gotten nearly all of the variation in cfi_cmdset_0001 and cfi_cmdset_0002
> under control.
>
> It is probably enough infrastructure so that cfi_cmdset_0001 and 0020 could be
> merged.
Sorry for the delay. Maybe I can convince Joern to get them merged.
Most of the stuff can probably be done in a fixup function now that they
take a struct mtd_info *.
>
> For the deeper pieces of command set common code moving their helper functions
> into cfi_util is probably a good place to start.
>
> I'm hoping I have accomplished enough I don't need to touch the code again for quite a while but...
We can always hope :).
josh
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
------------------------------
______________________________________________________
Linux MTD discussion mailing list digest
http://lists.infradead.org/mailman/listinfo/linux-mtd/
End of linux-mtd Digest, Vol 17, Issue 17
*****************************************
next reply other threads:[~2004-08-16 14:21 UTC|newest]
Thread overview: 297+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 14:21 Mail Delivery System [this message]
[not found] <20230919130822.8B68EBEEA34BA704@vger.kernel.org>
2023-09-19 11:40 ` Mail delivery failed: returning message to sender Mail Delivery System
[not found] <20230911010529.86EA1B7408F3EC04@vger.kernel.org>
2023-09-11 8:05 ` Mail Delivery System
[not found] <20230817100924.49044D6518A44C49@vger.kernel.org>
2023-08-17 9:09 ` Mail Delivery System
[not found] <20230816120734.EC69A8DEF6067EB6@kernel.org>
2023-08-16 11:07 ` Mail Delivery System
[not found] <20230816120650.BE2BBAFE768CB5F4@lists.linux.dev>
2023-08-16 11:06 ` Mail Delivery System
[not found] <20230816120551.D77682163964749B@lists.linux.dev>
2023-08-16 11:05 ` Mail Delivery System
[not found] <20230816120550.67970145FA271048@lists.linux.dev>
2023-08-16 11:05 ` Mail Delivery System
[not found] <20230816120531.057CDA36916887DA@lists.linux.dev>
2023-08-16 11:05 ` Mail Delivery System
[not found] <20230816120528.99581B15228A21F9@lists.linux.dev>
2023-08-16 11:05 ` Mail Delivery System
[not found] <20230816120406.444E5852DC7BE3EF@lists.linux.dev>
2023-08-16 11:04 ` Mail Delivery System
[not found] <20230816120404.72EB41734ED057E8@lists.linux.dev>
2023-08-16 11:04 ` Mail Delivery System
[not found] <20230816115124.E887BBA760932448@lists.linux.dev>
2023-08-16 10:51 ` Mail Delivery System
[not found] <20230816113737.044F6D5996B8EF88@lists.linux.dev>
2023-08-16 10:37 ` Mail Delivery System
[not found] <20230816113304.228C7B2568AFF488@lists.linux.dev>
2023-08-16 10:33 ` Mail Delivery System
[not found] <20230816113242.DA07B8DB3BA1A07D@lists.linux.dev>
2023-08-16 10:32 ` Mail Delivery System
[not found] <20230816100304.F9930AA917EDA9DA@lists.linux.dev>
2023-08-16 9:03 ` Mail Delivery System
[not found] <20230816100303.E4027DC3296C6D15@lists.linux.dev>
2023-08-16 9:03 ` Mail Delivery System
[not found] <20230816100258.B626FAF3CD9EBBD6@lists.linux.dev>
2023-08-16 9:03 ` Mail Delivery System
[not found] <20230816100254.6BDE7A944CA9BB78@kernel.org>
2023-08-16 9:02 ` Mail Delivery System
[not found] <20230814111940.870716D17901B27D@kernel.org>
2023-08-14 10:19 ` Mail Delivery System
[not found] <20230814104639.54BEF81890F70DC4@lists.linux.dev>
2023-08-14 9:46 ` Mail Delivery System
[not found] <20230814104255.C2BBCDDA9B815FB6@lists.linux.dev>
2023-08-14 9:42 ` Mail Delivery System
[not found] <20230814103628.32A9B9B6C52A1DE3@lists.linux.dev>
2023-08-14 9:36 ` Mail Delivery System
[not found] <20230814102751.31AD0FD42294B28C@lists.linux.dev>
2023-08-14 9:27 ` Mail Delivery System
[not found] <20230814102730.62A81ABA2617AADC@lists.linux.dev>
2023-08-14 9:27 ` Mail Delivery System
[not found] <20230814102704.8CF24EB60A0CCCC4@lists.linux.dev>
2023-08-14 9:27 ` Mail Delivery System
[not found] <20230814102704.252CCD7AE5C5FBA6@lists.linux.dev>
2023-08-14 9:27 ` Mail Delivery System
[not found] <20230814102700.7F5D13F4B03D7D17@lists.linux.dev>
2023-08-14 9:27 ` Mail Delivery System
[not found] <20230814102412.45D084CD67ABFEB1@lists.linux.dev>
2023-08-14 9:24 ` Mail Delivery System
[not found] <20230814101407.E583F8A1584FBF9E@lists.linux.dev>
2023-08-14 9:14 ` Mail Delivery System
[not found] <20230814093908.58A41D84261385F6@lists.linux.dev>
2023-08-14 8:39 ` Mail Delivery System
[not found] <20230814093047.3B521F5FA66C0D10@lists.linux.dev>
2023-08-14 8:30 ` Mail Delivery System
[not found] <20230814091553.68398532BA78381E@lists.linux.dev>
2023-08-14 8:15 ` Mail Delivery System
[not found] <20230814002142.B09C7749E66E56C3@kernel.org>
2023-08-13 23:21 ` Mail Delivery System
[not found] <20230813233345.1D20AEA1D24982E9@kernel.org>
2023-08-13 22:33 ` Mail Delivery System
[not found] <20230705094258.A0537187FDAFEDF3@kernel.org>
2023-07-05 9:43 ` Mail Delivery System
[not found] <20230506214302.B57697534CB0D3D0@vger.kernel.org>
2023-05-06 21:43 ` Mail Delivery System
[not found] <20230424173748.4C0F6EA6C3A3A716@kernel.org>
2023-04-24 15:37 ` Mail Delivery System
[not found] <20230424075707.E7190108E70A3C1F@kernel.org>
2023-04-24 5:57 ` Mail Delivery System
[not found] <48c97496-983b-4227-9566-2223268b51bf@lists.linux.dev>
2022-10-05 5:48 ` Mail Delivery System
[not found] <eb0c8064-a9a0-403d-904f-e1a2ae2e68e9@lists.ozlabs.org>
2022-09-07 12:49 ` Mail Delivery System
[not found] <625918748262f@lists.linux.dev>
2022-04-20 8:14 ` Mail Delivery System
-- strict thread matches above, loose matches on Subject: below --
2020-07-18 1:26 Mail Delivery System
2020-05-15 16:10 Mail Delivery System
2015-06-14 6:52 Mail Delivery System
2015-03-25 9:22 Mail Delivery System
2015-03-25 0:38 Mail Delivery System
2015-02-05 7:54 Mail Delivery System
2014-12-11 17:07 Mail Delivery System
2014-12-08 12:51 Mail Delivery System
2014-10-07 5:59 Mail Delivery System
2014-08-06 4:32 Mail Delivery System
2014-08-05 7:09 Mail Delivery System
2014-07-22 14:04 Mail Delivery System
2014-07-22 9:24 Mail Delivery System
2014-07-21 17:29 Mail Delivery System
2014-07-20 18:35 Mail Delivery System
2014-02-21 12:35 Mail Delivery System
2014-02-21 6:39 Mail Delivery System
2014-02-21 5:50 Mail Delivery System
2014-02-21 0:06 Mail Delivery System
2014-02-20 7:49 Mail Delivery System
2013-05-22 22:40 Mail Delivery System
2013-03-25 6:04 Mail Delivery System
2013-03-25 1:46 Mail Delivery System
2012-10-30 19:26 Mail Delivery System
2012-10-30 9:13 Mail Delivery System
2012-10-30 4:20 Mail Delivery System
2012-10-24 14:03 Mail Delivery System
2012-10-17 12:02 Mail Delivery System
2012-09-15 0:34 Mail Delivery System
2012-09-15 0:34 Mail Delivery System
2012-09-15 0:34 Mail Delivery System
2012-09-15 0:34 Mail Delivery System
2012-09-15 0:34 Mail Delivery System
2012-09-11 17:46 Mailer Delivery System
2012-09-11 17:44 Mail Delivery System
2012-09-11 17:44 Mailer Delivery System
2012-09-11 17:44 Mailer Delivery System
2012-09-11 17:44 Mailer Delivery System
2012-09-11 17:44 Mailer Delivery System
2012-09-11 14:40 Mail Delivery System
2012-08-27 15:57 Mail Delivery System
2012-08-27 1:57 Mail Delivery System
2012-08-27 0:50 Mail Delivery System
2012-08-27 0:13 Mail Delivery System
2012-08-14 1:01 Mail Delivery System
2012-08-14 0:47 Mail Delivery System
2012-05-12 3:27 Mail Delivery System
2012-04-03 9:03 Mail Delivery System
2012-03-30 1:05 Mail Delivery System
2012-03-26 7:38 Mail Delivery System
2012-03-18 8:02 Mail Delivery System
2012-03-07 2:31 Mail Delivery System
2012-02-29 18:03 Mail Delivery System
2012-02-28 11:42 Mail Delivery System
2012-02-27 11:28 Mail Delivery System
2012-02-23 20:26 Mail Delivery System
2012-02-22 4:07 Mail Delivery System
2012-02-21 6:20 Mail Delivery System
2012-02-21 6:11 Mail Delivery System
2012-02-21 5:57 Mail Delivery System
2012-02-07 12:43 Mail Delivery System
2012-01-19 15:48 Mail Delivery System
2012-01-08 7:25 Mail Delivery System
2012-01-04 10:44 Mail Delivery System
2012-01-03 0:12 Mail Delivery System
2011-12-30 1:08 Mail Delivery System
2011-12-29 16:08 Mail Delivery System
2011-12-21 10:46 Mail Delivery System
2011-12-21 1:21 Mail Delivery System
2011-12-21 1:21 Mail Delivery System
2011-12-21 1:21 Mail Delivery System
2011-12-21 1:20 Mail Delivery System
2011-12-21 1:20 Mail Delivery System
2011-12-10 8:30 Mail Delivery System
2011-12-09 23:24 Mail Delivery System
2011-12-07 4:44 Mail Delivery System
2011-12-07 1:43 Mail Delivery System
2011-12-06 11:06 Mail Delivery System
2011-12-06 1:03 Mail Delivery System
2011-12-03 6:13 Mail Delivery System
2011-11-26 9:11 Mail Delivery System
2011-11-26 8:11 Mail Delivery System
2011-11-26 7:40 Mail Delivery System
2011-11-26 4:16 Mail Delivery System
2011-11-25 19:15 Mail Delivery System
2011-11-24 5:08 Mail Delivery System
2011-11-23 20:52 Mail Delivery System
2011-11-23 4:37 Mail Delivery System
2011-11-20 11:54 Mail Delivery System
2011-11-15 20:12 Mail Delivery System
2011-11-15 18:44 Mail Delivery System
2011-11-15 11:51 Mail Delivery System
2011-11-15 9:29 Mail Delivery System
2011-11-15 5:50 Mail Delivery System
2011-11-15 0:54 Mail Delivery System
2011-11-05 15:37 Mail Delivery System
2011-11-03 2:14 Mail Delivery System
2011-11-01 13:29 Mail Delivery System
2011-11-01 13:08 Mail Delivery System
2011-10-25 6:39 Mail Delivery System
2011-10-24 21:30 Mail Delivery System
2008-10-03 0:54 Mail Delivery System
2008-02-15 5:40 Mail Delivery System
2008-02-15 2:23 Mail Delivery System
2008-02-15 1:40 Mail Delivery System
2007-05-29 21:10 Mail Delivery System
2007-03-19 15:18 Mail Delivery System
2007-03-18 12:04 Mail Delivery System
2007-03-16 6:11 Mail Delivery System
2007-03-15 13:09 Mail Delivery System
2007-03-15 12:35 Mail Delivery System
2007-03-14 4:07 Mail Delivery System
2007-03-13 20:06 Mail Delivery System
2007-03-13 2:24 Mail Delivery System
2007-03-11 10:26 Mail Delivery System
2007-03-10 20:06 Mail Delivery System
2007-03-07 17:45 Mail Delivery System
2007-03-03 1:05 Mail Delivery System
2007-03-01 14:27 Mail Delivery System
2007-02-27 5:10 Mail Delivery System
2007-02-27 1:07 Mail Delivery System
2007-02-24 12:53 Mail Delivery System
2007-02-23 11:08 Mail Delivery System
2007-02-21 16:29 Mail Delivery System
2007-02-21 14:46 Mail Delivery System
2007-02-20 14:58 Mail Delivery System
2007-02-20 14:33 Mail Delivery System
2007-02-20 5:28 Mail Delivery System
2007-02-17 11:19 Mail Delivery System
2007-02-16 19:31 Mail Delivery System
2007-02-14 22:31 Mail Delivery System
2007-02-14 14:29 Mail Delivery System
2007-02-13 7:35 Mail Delivery System
2007-02-12 5:27 Mail Delivery System
2007-02-08 22:54 Mail Delivery System
2007-02-08 16:06 Mail Delivery System
2007-02-04 16:40 Mail Delivery System
2007-01-31 13:43 Mail Delivery System
2007-01-31 1:24 Mail Delivery System
2007-01-27 5:43 Mail Delivery System
2007-01-27 4:48 Mail Delivery System
2007-01-25 21:50 Mail Delivery System
2007-01-21 7:12 Mail Delivery System
2007-01-19 11:06 Mail Delivery System
2007-01-13 14:05 Mail Delivery System
2007-01-11 2:52 Mail Delivery System
2007-01-10 5:43 Mail Delivery System
2007-01-07 17:57 Mail Delivery System
2007-01-06 1:52 Mail Delivery System
2007-01-04 16:36 Mail Delivery System
2007-01-03 17:58 Mail Delivery System
2006-12-12 11:24 Mail Delivery System
2006-12-03 16:24 Mail Delivery System
2006-11-22 1:50 Mail Delivery System
2006-11-20 3:36 Mail Delivery System
2006-11-19 11:08 Mail Delivery System
2006-11-16 16:40 Mail Delivery System
2006-11-16 9:07 Mail Delivery System
2006-11-14 19:58 Mail Delivery System
2006-11-07 18:08 Mail Delivery System
2006-10-28 0:48 Mail Delivery System
2006-10-25 1:36 Mail Delivery System
2006-10-05 16:58 Mail Delivery System
2006-06-24 5:23 Mail Delivery System
2006-03-25 11:14 Mail Delivery System
2006-03-24 8:53 Mail Delivery System
2006-03-21 10:11 Mail Delivery System
2006-01-14 3:27 Mail Delivery System
2005-11-30 8:21 Mail Delivery System
2005-10-19 16:57 Mail Delivery System
2005-07-16 9:52 Mail Delivery System
2004-09-13 19:39 Mail Delivery System
2004-09-11 4:12 Mail Delivery System
2004-08-16 14:20 Mail Delivery System
2004-08-16 14:18 Mail Delivery System
2004-08-16 14:16 Mail Delivery System
2004-08-16 14:14 Mail Delivery System
2004-08-12 10:14 Mail Delivery System
2004-08-11 7:44 Mail Delivery System
2004-08-07 0:58 Mail Delivery System
2004-08-06 23:36 Mail Delivery System
2004-08-04 9:17 Mail Delivery System
2004-08-03 8:58 Mail Delivery System
2004-07-31 20:32 Mail Delivery System
2004-07-30 15:14 Mail Delivery System
2004-07-29 6:35 Mail Delivery System
2004-07-27 15:55 Mail Delivery System
2004-07-27 8:01 Mail Delivery System
2004-07-26 13:58 Mail Delivery System
2004-07-24 2:17 Mail Delivery System
2004-07-23 4:31 Mail Delivery System
2004-07-15 1:23 Mail Delivery System
2004-07-13 5:17 Mail Delivery System
2004-07-11 8:46 Mail Delivery System
2004-07-09 17:41 Mail Delivery System
2004-07-03 11:14 Mail Delivery System
2004-07-01 18:00 Mail Delivery System
2004-07-01 11:59 Mail Delivery System
2004-06-29 13:53 Mail Delivery System
2004-06-27 5:08 Mail Delivery System
2004-06-16 20:16 Mail Delivery System
2004-06-14 4:33 Mail Delivery System
2004-06-12 17:13 Mail Delivery System
2004-06-11 2:52 Mail Delivery System
2004-06-10 10:58 Mail Delivery System
2004-06-09 11:38 Mail Delivery System
2004-06-07 6:05 Mail Delivery System
2004-06-02 2:44 Mail Delivery System
2004-05-20 17:22 Mail Delivery System
2004-05-19 0:26 Mail Delivery System
2004-05-14 3:12 Mail Delivery System
2004-05-11 17:45 Mail Delivery System
2004-05-10 7:49 Mail Delivery System
2004-05-10 1:37 Mail Delivery System
2004-05-07 2:22 Mail Delivery System
2004-05-07 1:25 Mail Delivery System
2004-04-30 9:59 Mail Delivery System
2004-04-30 2:11 Mail Delivery System
2004-04-18 8:49 Mail Delivery System
2004-04-18 6:17 Mail Delivery System
2004-04-15 11:02 Mail Delivery System
2004-04-12 9:53 Mail Delivery System
2004-04-07 9:32 Mail Delivery System
2004-04-05 10:17 Mail Delivery System
2004-04-05 2:28 Mail Delivery System
2004-04-04 11:52 Mail Delivery System
2004-04-02 1:19 Mail Delivery System
2004-04-02 0:28 Mail Delivery System
2004-04-01 7:10 Mail Delivery System
2004-03-25 16:44 Mail Delivery System
2004-03-24 22:54 Mail Delivery System
2004-03-17 18:01 Mail Delivery System
2004-03-17 7:22 Mail Delivery System
2004-03-16 20:50 Mail Delivery System
2004-03-14 11:40 Mail Delivery System
2004-03-13 3:05 Mail Delivery System
2004-01-28 0:38 Mail Delivery System
2004-01-27 15:36 Mail Delivery System
2004-01-27 3:18 Mail Delivery System
2004-01-26 23:18 Mail Delivery System
2004-01-26 22:57 Mail Delivery System
2003-09-26 21:19 noreply
2003-09-26 19:00 noreply
2003-09-26 18:38 noreply
2003-09-26 18:25 noreply
2003-09-21 0:02 noreply
2003-07-05 23:56 Mail Delivery System
2003-07-05 21:22 Mail Delivery System
2003-06-27 12:05 Mail Delivery System
2003-06-17 8:18 Mail Delivery System
[not found] <20030521012148.P10585@flint.arm.linux.org.uk>
2003-05-21 0:55 ` David S. Miller
2003-05-21 2:22 ` kuznet
2003-05-21 2:31 ` David S. Miller
2003-05-21 9:07 ` Russell King
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=E1BwiMO-0007EC-Uw@canuck.infradead.org \
--to=mailer-daemon@infradead.org \
--cc=linux-mtd-bounces@lists.infradead.org \
/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.