From: Artem Bityutskiy <dedekind1@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 14 (mtd)
Date: Tue, 15 Jan 2013 12:21:32 +0200 [thread overview]
Message-ID: <1358245292.2731.120.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <874nija8ry.fsf@free.fr>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Mon, 2013-01-14 at 20:01 +0100, Robert Jarzmik wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
> > ERROR: "byte_rev_table" [drivers/mtd/devices/docg3.ko] undefined!
>
> Thanks for the report. I have a trivial patch attached. Should it go through
> Artem's tree or do you want to take it directly ?
David just picked this patch to the MTD tree.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
linux-mtd@lists.infradead.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 14 (mtd)
Date: Tue, 15 Jan 2013 12:21:32 +0200 [thread overview]
Message-ID: <1358245292.2731.120.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <874nija8ry.fsf@free.fr>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Mon, 2013-01-14 at 20:01 +0100, Robert Jarzmik wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
> > ERROR: "byte_rev_table" [drivers/mtd/devices/docg3.ko] undefined!
>
> Thanks for the report. I have a trivial patch attached. Should it go through
> Artem's tree or do you want to take it directly ?
David just picked this patch to the MTD tree.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-15 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 4:46 linux-next: Tree for Jan 14 Stephen Rothwell
2013-01-14 4:46 ` Stephen Rothwell
2013-01-14 16:25 ` linux-next: Tree for Jan 14 (mtd) Randy Dunlap
2013-01-14 16:25 ` Randy Dunlap
2013-01-14 19:01 ` Robert Jarzmik
2013-01-14 19:13 ` Randy Dunlap
2013-01-15 10:21 ` Artem Bityutskiy [this message]
2013-01-15 10:21 ` Artem Bityutskiy
2013-01-14 16:40 ` [ath9k-devel] linux-next: Tree for Jan 14 (wireless/ath9k) Randy Dunlap
2013-01-14 16:40 ` Randy Dunlap
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=1358245292.2731.120.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robert.jarzmik@free.fr \
--cc=sfr@canb.auug.org.au \
/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.