Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932183AbbDMRR4 (ORCPT ); Mon, 13 Apr 2015 13:17:56 -0400 Received: from mail-pd0-f175.google.com ([209.85.192.175]:35499 "EHLO mail-pd0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754083AbbDMRRw (ORCPT ); Mon, 13 Apr 2015 13:17:52 -0400 Date: Mon, 13 Apr 2015 10:17:43 -0700 From: Brian Norris To: linux-mtd@lists.infradead.org Cc: Andrea Scian , Boris Brezillon , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, dedekind1@gmail.com, Richard Weinberger Subject: linux-mtd digest emails (was Re: [PATCH 4/4] UBI: Implement bitrot checking) Message-ID: <20150413171743.GO32500@ld-irv-0074> References: <552AA390.3070700@nod.at> <552AD8A6.6000406@dave-tech.it> <552ADD27.6080703@nod.at> <552AE48C.8070500@dave-tech.it> <552AE6C3.8040605@nod.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <552AE6C3.8040605@nod.at> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 941 Lines: 28 Hi everyone, linux-mtd administrative note: Please don't start conversations based on mailing list "digest" emails. It's not helpful for others (e.g., it likely breaks threading). Also, the mailing list filters these types of messages out, presumably based on the email subject, so many subscribers probably did not see your email. So, a recent thread was under the subject: Re: [PATCH 4/4] UBI: Implement bitrot checking (linux-mtd Digest, Vol 145, Issue 24) But it should be using: Re: [PATCH 4/4] UBI: Implement bitrot checking I've released a few messages for now, but I can't guarantee that such messages will get through in the future (and certainly not promptly). Thanks, Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/