From: Soumya Negi <soumya.negi97@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Jonathan Kim <jonathankim@gctsemi.com>,
Dean ahn <deanahn@gctsemi.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tty: gdm724x: Match alignment with open parenthesis
Date: Thu, 19 Oct 2023 19:14:07 -0700 [thread overview]
Message-ID: <20231020021407.GE3017@Negi> (raw)
In-Reply-To: <52732a88-7f40-4ce4-b75b-dded9827c1f0@kadam.mountain>
On Sat, Oct 14, 2023 at 10:38:22AM +0300, Dan Carpenter wrote:
> On Fri, Oct 13, 2023 at 02:13:26PM -0700, Soumya Negi wrote:
> > On Fri, Oct 13, 2023 at 11:57:40AM +0300, Dan Carpenter wrote:
> > > On Fri, Oct 13, 2023 at 01:26:34AM -0700, Soumya Negi wrote:
> > > > Fix CHECK: Alignment should match open parenthesis
> > > > Issue found by checkpatch.pl
> > > >
> > > > Signed-off-by: Soumya Negi <soumya.negi97@gmail.com>
> > > > ---
> > > > drivers/staging/gdm724x/gdm_tty.c | 4 ++--
> > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/staging/gdm724x/gdm_tty.c b/drivers/staging/gdm724x/gdm_tty.c
> > > > index 32b2e817ff04..4e5cac76db58 100644
> > > > --- a/drivers/staging/gdm724x/gdm_tty.c
> > > > +++ b/drivers/staging/gdm724x/gdm_tty.c
> > > > @@ -271,8 +271,8 @@ int register_lte_tty_driver(void)
> > > > int ret;
> > > >
> > > > for (i = 0; i < TTY_MAX_COUNT; i++) {
> > > > - tty_driver = tty_alloc_driver(GDM_TTY_MINOR,
> > > > - TTY_DRIVER_REAL_RAW | TTY_DRIVER_DYNAMIC_DEV);
> > > > + tty_driver = tty_alloc_driver(GDM_TTY_MINOR, TTY_DRIVER_REAL_RAW |
> > > > + TTY_DRIVER_DYNAMIC_DEV);
> > >
> > > I prefered the original code. It was more readable.
> > >
> > > regards,
> > > dan carpenter
> > Hi Dan,
> >
> > Noted. I'm curious what happens when some of the patches in a patchset
> > are acceptable and some are not. Is everything disregarded by
> > maintainers or are the good patches cherry-picked from the set?
>
> Most of the time, you should just resend the series. Sometimes a
> maintainer will take the first few patches and then when they hit one
> that can't be merged they'll stop. So you should try to organize your
> patchsets from fixes first, then cleanups and then least controversial
> to most controversial. Except people might be annoyed if it looks like
> you're hiding a really controversial one at the end of a long series.
>
> regards,
> dan carpenter
Thank you!
- Soumya
next prev parent reply other threads:[~2023-10-20 2:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 8:26 [PATCH 0/2] tty: gdm724x: Fix coding style in gdm_tty.c Soumya Negi
2023-10-13 8:26 ` [PATCH 1/2] tty: gdm724x: Match alignment with open parenthesis Soumya Negi
2023-10-13 8:57 ` Dan Carpenter
2023-10-13 21:13 ` Soumya Negi
2023-10-14 7:38 ` Dan Carpenter
2023-10-20 2:14 ` Soumya Negi [this message]
2023-10-13 8:26 ` [PATCH 2/2] tty: gdm724x: Add blank line after declaration Soumya Negi
2023-10-15 5:37 ` Greg Kroah-Hartman
2023-10-15 6:07 ` Soumya Negi
2023-10-15 12:50 ` Greg Kroah-Hartman
2023-10-15 19:19 ` Soumya Negi
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=20231020021407.GE3017@Negi \
--to=soumya.negi97@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=deanahn@gctsemi.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathankim@gctsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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.