From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Martin Sperl <kernel@martin.sperl.org>,
linux-spi@vger.kernel.org
Subject: Re: [PATCH resend 1/5] spi: bcm2835: Add GPIOLIB dependency
Date: Mon, 04 May 2015 19:00:55 -0700 [thread overview]
Message-ID: <55482457.2020005@roeck-us.net> (raw)
In-Reply-To: <55480894.3080200@roeck-us.net>
On 05/04/2015 05:02 PM, Guenter Roeck wrote:
> On 05/04/2015 04:34 PM, Mark Brown wrote:
>> On Mon, May 04, 2015 at 03:30:45PM -0700, Guenter Roeck wrote:
>>> Fix:
>>>
>>> drivers/spi/spi-bcm2835.c: In function 'chip_match_name':
>>> drivers/spi/spi-bcm2835.c:356:21: error:
>>
>> This duplicates a patch someone else sent.
>>
>
> Hi Mark,
>
> not that it matters, but this is the patch in linux-next.
>
> I am aware that several other patches have been submitted to fix the
> problem (I think I have seen at least two); after all, I submitted the
> patch some three weeks ago, and many others are affected by it. I don't
> really care which one of the submitted patches is applied to mainline,
> as long as the problem is getting fixed.
>
> Repeating my comment from the patch,
>
> "Yes, I know, this patch is in -next. Please see this e-mail as gentle reminder
> to consider pushing it (or one of the other patches fixing the same problem)
> into mainline."
>
Follow-up: Since you accepted one of the other patches, please make sure
to remove my patch from your -next branch; otherwise we might end up
with dual "depends on GPIOLIB".
Thanks,
Guenter
next prev parent reply other threads:[~2015-05-05 2:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 22:30 [PATCH resend 0/5] Fix various build errors Guenter Roeck
2015-05-04 22:30 ` [PATCH resend 1/5] spi: bcm2835: Add GPIOLIB dependency Guenter Roeck
2015-05-04 23:34 ` Mark Brown
2015-05-05 0:02 ` Guenter Roeck
2015-05-05 2:00 ` Guenter Roeck [this message]
2015-05-05 11:16 ` Mark Brown
2015-05-05 11:32 ` Geert Uytterhoeven
2015-05-05 11:40 ` Mark Brown
2015-05-05 10:28 ` Mark Brown
2015-05-04 22:30 ` [PATCH resend 2/5] mips: Fix SMP builds Guenter Roeck
2015-05-04 22:30 ` [PATCH resend 3/5] xtensa: Provide dummy dma_alloc_attrs() and dma_free_attrs() Guenter Roeck
2015-05-04 22:35 ` Chris Zankel
2015-05-23 4:24 ` Guenter Roeck
2015-05-04 22:30 ` [PATCH resend 4/5] score: Fix exception handler label Guenter Roeck
2015-05-06 2:00 ` Lennox Wu
2015-05-23 4:24 ` Guenter Roeck
2015-05-25 14:56 ` Lennox Wu
2015-05-04 22:30 ` [PATCH resend 5/5] blackfin: Fix build error Guenter Roeck
2015-05-06 9:15 ` Steven Miao
2015-05-23 4:25 ` Guenter Roeck
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=55482457.2020005@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=kernel@martin.sperl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox