From: Saurav Girepunje <saurav.girepunje@gmail.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: santoshkumar.yadav@barco.com, peter.korsgaard@barco.com,
hdegoede@redhat.com, markgross@kernel.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, saurav.girepunje@hotmail.com
Subject: Re: [PATCH] platform: x86: Remove duplicated include in barco-p50-gpio.c
Date: Mon, 27 Jun 2022 23:05:01 +0530 [thread overview]
Message-ID: <f08574e9-3e1e-0bc4-c95c-83fb955d2869@gmail.com> (raw)
In-Reply-To: <87y1xizj06.fsf@dell.be.48ers.dk>
On 27/06/22 12:32 pm, Peter Korsgaard wrote:
>>>>>> "Saurav" == Saurav Girepunje <saurav.girepunje@gmail.com> writes:
>
> > On 27/06/22 12:41 am, Peter Korsgaard wrote:
> >>>>>>> "Saurav" == Saurav Girepunje <saurav.girepunje@gmail.com> writes:
> >>
> >> > Remove the duplicate include of linux/io.h in barco-p50-gpio.c
> >> > file.
> >>
> >> > Signed-off-by: Saurav Girepunje <saurav.girepunje@gmail.com>
> >>
> >> What tree is this against? The io.h include in the line just above
> >> delay.h was already removed by:
> >>
>
> > I am using git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git .
>
> staging? That seems an odd tree to make platform/x86 changes
> from. Just using the mainline tree would be a better choice.
Ok, Sure
>
> > if it fix on another tree . Please ignore this patch.
>
> git describe --contains 011881b80ebe773914b59905bce0f5e0ef93e7ba
> v5.19-rc2~1^2~5
>
> So it is in 5.19-rc2, released 2 weeks ago.
>
Yes
prev parent reply other threads:[~2022-06-27 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 17:15 Saurav Girepunje
2022-06-26 19:11 ` Peter Korsgaard
2022-06-27 3:39 ` Saurav Girepunje
2022-06-27 7:02 ` Peter Korsgaard
2022-06-27 17:35 ` Saurav Girepunje [this message]
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=f08574e9-3e1e-0bc4-c95c-83fb955d2869@gmail.com \
--to=saurav.girepunje@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=peter@korsgaard.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=santoshkumar.yadav@barco.com \
--cc=saurav.girepunje@hotmail.com \
/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
all inboxes | Powered by JetHome®