From: Bastian Hecht <hechtb@googlemail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-mtd@lists.infradead.org,
Laurent Pichart <laurent.pinchart@ideasonboard.com>,
Brian Norris <computersforpeace@gmail.com>,
Bastian Hecht <hechtb@googlemail.com>
Subject: Re: [PATCH v3 02/10] ARM: sh-mobile: mackerel: Add error IRQ resource
Date: Thu, 3 May 2012 11:29:26 +0200 [thread overview]
Message-ID: <CABYn4szWZP4zZcz1MJ1xk5oCxiWh0nyJczcHGUqw4wE5MfJunA@mail.gmail.com> (raw)
In-Reply-To: <1336024908.2056.3.camel@koala>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
Am 03.05.2012 08:01 schrieb "Artem Bityutskiy" <dedekind1@gmail.com>:
>
> On Thu, 2012-05-03 at 09:00 +0300, Artem Bityutskiy wrote:
> > On Wed, 2012-05-02 at 22:49 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, May 02, 2012, Bastian Hecht wrote:
> > > > Supply the platform data for the FLSTEI error IRQ.
> > > >
> > > > Signed-off-by: Bastian Hecht <hechtb@gmail.com>
> > >
> > > I'm going to take this patch into the renesas.git tree and push it
> > > upstream throuch arm-soc, if that's not a problem.
> >
> > It is already in the MTD tree with the rest of the 10 patches...
>
> Ops, sorry, this is not true. Then Bastian should separate it out and
> not send it to the MTD tree.
Alright I'll do. I need to fix the compiler warnings of the mtd patches
anyway. So the board code is independant and can be pushed already by
Rafael, right? How is it supposed to work in general? I think the sh-mobile
list wants to be informed when I change something in the flctl code. Would
the right approach be to send 2 patchsets - posted on both MLs so that
Artem can take the mtd portions and Rafael the mackerel ones?
Best regards,
Bastian Hecht
> --
> Best Regards,
> Artem Bityutskiy
[-- Attachment #2: Type: text/html, Size: 1549 bytes --]
next prev parent reply other threads:[~2012-05-03 9:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 9:41 [PATCH v3 0/10] sh_flctl hardware ECC mode cleanup Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 01/10] mtd: sh_flctl: Add missing iounmap() Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 02/10] ARM: sh-mobile: mackerel: Add error IRQ resource Bastian Hecht
2012-05-02 20:49 ` Rafael J. Wysocki
2012-05-02 21:03 ` Magnus Damm
2012-05-03 6:00 ` Artem Bityutskiy
2012-05-03 6:01 ` Artem Bityutskiy
2012-05-03 9:29 ` Bastian Hecht [this message]
2012-05-03 10:05 ` Artem Bityutskiy
2012-05-03 13:31 ` Rafael J. Wysocki
2012-05-02 9:41 ` [PATCH v3 03/10] mtd: sh_flctl: Add support for error IRQ Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 04/10] mtd: sh_flctl: Use different OOB layout Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 05/10] mtd: sh_flctl: Fix hardware ECC behaviour Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 06/10] mtd: sh_flctl: Simplify the hardware ecc page read/write Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 07/10] mtd: sh_flctl: Group sector accesses into a single transfer Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 08/10] mtd: sh_flctl: Restructure the hardware ECC handling Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 09/10] mtd: sh_flctl: Use user oob data in hardware ECC mode Bastian Hecht
2012-05-02 9:41 ` [PATCH v3 10/10] ARM: sh-mobile: mackerel: Use hardware error correction Bastian Hecht
2012-05-02 10:38 ` [PATCH v3 0/10] sh_flctl hardware ECC mode cleanup Artem Bityutskiy
2012-05-02 11:51 ` Bastian Hecht
2012-05-02 12:02 ` Artem Bityutskiy
2012-05-02 13:41 ` Bastian Hecht
2012-05-02 13:55 ` Artem Bityutskiy
2012-05-02 14:00 ` Bastian Hecht
2012-05-02 14:08 ` Artem Bityutskiy
2012-05-02 14:40 ` Bastian Hecht
2012-05-02 14:46 ` Bastian Hecht
2012-05-02 14:51 ` Artem Bityutskiy
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=CABYn4szWZP4zZcz1MJ1xk5oCxiWh0nyJczcHGUqw4wE5MfJunA@mail.gmail.com \
--to=hechtb@googlemail.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).