From: Dan Carpenter <dan.carpenter@linaro.org>
To: Uri Arev <me@wantyapps.xyz>
Cc: Shresth Prasad <shresthprasad7@gmail.com>,
christophe.jaillet@wanadoo.fr, frank.li@vivo.com,
gregkh@linuxfoundation.org, hverkuil-cisco@xs4all.nl,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
luca.ceresoli@bootlin.com, prathubaronia2011@gmail.com,
robh@kernel.org, skhan@linuxfoundation.org,
u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH] staging: axis-fifo: align arguments to open parenthesis in axis-fifo.c
Date: Tue, 2 Apr 2024 10:15:12 +0300 [thread overview]
Message-ID: <fdc25599-f8a7-4d66-9535-494de8439da0@moroto.mountain> (raw)
In-Reply-To: <qnljnwccqvqzilxuoat2s6md2zwcuhfruzbpepxebk65k34t3g@cyl67lk5lsoe>
On Sun, Mar 31, 2024 at 09:33:55PM +0300, Uri Arev wrote:
> > Oh, that's too bad. Thanks for the heads up!
> No worries, I wouldn't mind it if your patch got accepted and not mine
> :p
> I just don't think they accept patches to axis-fifo anymore, especially
> not basic syntax and checkpatch patches which are not as important as
> actual bug-fixes.
No, we're always taking patches. You just had bad luck/timing where you
sent the patch 2 days before Greg went on vacation.
Greg is back now, but I imagine he has a long list of stuff to catch up
with. It's possible that he also accidentally dropped your patch
because of the vacation... I could imagine a situation where that
happened.
regards,
dan carpenter
next prev parent reply other threads:[~2024-04-02 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <z2ewk44rjutv24i6lqau3adrmlprj524ulqtqbncvfaj44dwcg@2dnnbm75abbp>
2024-03-31 2:19 ` [PATCH] staging: axis-fifo: align arguments to open parenthesis in axis-fifo.c Shresth Prasad
[not found] ` <qnljnwccqvqzilxuoat2s6md2zwcuhfruzbpepxebk65k34t3g@cyl67lk5lsoe>
2024-04-02 7:15 ` Dan Carpenter [this message]
2024-04-02 13:59 ` eretmochelys imbricata
2024-03-29 20:32 Shresth Prasad
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=fdc25599-f8a7-4d66-9535-494de8439da0@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=frank.li@vivo.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luca.ceresoli@bootlin.com \
--cc=me@wantyapps.xyz \
--cc=prathubaronia2011@gmail.com \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).