From: Artem Bityutskiy <dedekind1@gmail.com>
To: Christian Daudt <csd@broadcom.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Will Deacon <will.deacon@arm.com>,
cdaudt@gmail.com, "arm@kernel.org" <arm@kernel.org>,
linux-mtd@lists.infradead.org,
"JD \(Jiandong\) Zheng" <jdzheng@broadcom.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] ARM: Remove bcmring NAND driver
Date: Mon, 24 Sep 2012 18:06:27 +0300 [thread overview]
Message-ID: <1348499187.4880.66.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1348263626-3087-2-git-send-email-csd@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Fri, 2012-09-21 at 14:40 -0700, Christian Daudt wrote:
> This driver is being removed as part of the cleanup of the bcmring
> SoC from mainline as it is no longer maintained.
>
> Signed-off-by: Christian Daudt <csd@broadcom.com>
> Reviewed-by: Jiandong Zheng <jdzheng@broadcom.com>
> Acked-by: Will Deacon <will.deacon@arm.com>
Pushed this patch to l2-mtd.git. But if you decide to merge it via
Arnd's tree (probably better idea) - let me know, I'll drop it.
--
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: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] ARM: Remove bcmring NAND driver
Date: Mon, 24 Sep 2012 18:06:27 +0300 [thread overview]
Message-ID: <1348499187.4880.66.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1348263626-3087-2-git-send-email-csd@broadcom.com>
On Fri, 2012-09-21 at 14:40 -0700, Christian Daudt wrote:
> This driver is being removed as part of the cleanup of the bcmring
> SoC from mainline as it is no longer maintained.
>
> Signed-off-by: Christian Daudt <csd@broadcom.com>
> Reviewed-by: Jiandong Zheng <jdzheng@broadcom.com>
> Acked-by: Will Deacon <will.deacon@arm.com>
Pushed this patch to l2-mtd.git. But if you decide to merge it via
Arnd's tree (probably better idea) - let me know, I'll drop it.
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120924/8db93cc8/attachment-0001.sig>
next prev parent reply other threads:[~2012-09-24 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 21:40 [PATCH v3 0/2] ARM: Removal of bcmring Christian Daudt
2012-09-21 21:40 ` Christian Daudt
2012-09-21 21:40 ` [PATCH v3 1/2] ARM: Remove bcmring NAND driver Christian Daudt
2012-09-21 21:40 ` Christian Daudt
2012-09-24 15:06 ` Artem Bityutskiy [this message]
2012-09-24 15:06 ` Artem Bityutskiy
2012-09-24 15:21 ` Olof Johansson
2012-09-24 15:21 ` Olof Johansson
2012-09-21 21:40 ` [PATCH v3 2/2] ARM: Remove mach-bcmring Christian Daudt
2012-09-21 21:40 ` Christian Daudt
2012-09-24 8:37 ` Will Deacon
2012-09-24 8:37 ` Will Deacon
2012-09-28 19:46 ` Arnd Bergmann
2012-09-28 19:46 ` Arnd Bergmann
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=1348499187.4880.66.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=cdaudt@gmail.com \
--cc=csd@broadcom.com \
--cc=jdzheng@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=olof@lixom.net \
--cc=will.deacon@arm.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 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.