From: Arnd Bergmann <arnd@arndb.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH 3/6] serial: mid8250: select CONFIG_RATIONAL
Date: Mon, 16 Nov 2015 18:05:09 +0100 [thread overview]
Message-ID: <28108741.gZodRCNg2d@wuerfel> (raw)
In-Reply-To: <1447692962.31665.145.camel@linux.intel.com>
On Monday 16 November 2015 18:56:02 Andy Shevchenko wrote:
> On Mon, 2015-11-16 at 16:48 +0100, Arnd Bergmann wrote:
> > The Intel MID support got split out from the PCI 8250 driver,
> > and that now causes a build error when no other driver selects
> > CONFIG_RATIONAL:
>
> Already published.
> https://lkml.org/lkml/2015/11/12/272
>
> It's not first time you send patches that already have been published.
>
> I think you use some testing automation which doesn't take into
> consideration what is sent in mailing lists.
Correct, it also ignores whatever patches other people have in private
git trees, in their mail clients or in their heads.
I try to send patches for things that break either on the first
day they are broken so mine comes first, or I wait a while to see
if a fix ends up in linux-next to give everyone else a chance to
get their patch into next so I can catch it on a rebase.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] serial: mid8250: select CONFIG_RATIONAL
Date: Mon, 16 Nov 2015 18:05:09 +0100 [thread overview]
Message-ID: <28108741.gZodRCNg2d@wuerfel> (raw)
In-Reply-To: <1447692962.31665.145.camel@linux.intel.com>
On Monday 16 November 2015 18:56:02 Andy Shevchenko wrote:
> On Mon, 2015-11-16 at 16:48 +0100, Arnd Bergmann wrote:
> > The Intel MID support got split out from the PCI 8250 driver,
> > and that now causes a build error when no other driver selects
> > CONFIG_RATIONAL:
>
> Already published.
> https://lkml.org/lkml/2015/11/12/272
>
> It's not first time you send patches that already have been published.
>
> I think you use some testing automation which doesn't take into
> consideration what is sent in mailing lists.
Correct, it also ignores whatever patches other people have in private
git trees, in their mail clients or in their heads.
I try to send patches for things that break either on the first
day they are broken so mine comes first, or I wait a while to see
if a fix ends up in linux-next to give everyone else a chance to
get their patch into next so I can catch it on a rebase.
Arnd
next prev parent reply other threads:[~2015-11-16 17:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 15:48 [PATCH 0/6] serial: fixes and cleanups Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` [PATCH 1/6] serial: export fsl8250_handle_irq Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` [PATCH 2/6] serial: fsl-lpuart: move SERIAL_EARLYCON dependency to console Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-17 0:29 ` Stefan Agner
2015-11-17 0:29 ` Stefan Agner
2015-11-16 15:48 ` [PATCH 3/6] serial: mid8250: select CONFIG_RATIONAL Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 16:56 ` Andy Shevchenko
2015-11-16 16:56 ` Andy Shevchenko
2015-11-16 17:05 ` Arnd Bergmann [this message]
2015-11-16 17:05 ` Arnd Bergmann
2015-11-16 15:48 ` [PATCH 4/6] serial: remove NWP serial support Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` [PATCH 5/6] serial: of: CONFIG_SERIAL_8250 is always set Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` [PATCH 6/6] serial: 8250: move of_serial code to 8250 directory Arnd Bergmann
2015-11-16 15:48 ` Arnd Bergmann
2015-11-16 15:48 ` 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=28108741.gZodRCNg2d@wuerfel \
--to=arnd@arndb.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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.